AOD parallel jobs
Nobody has claimed this yet.
- Dominant language
- Fortran
- Stars
- 8
- Forks
- 3
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 6
Description
The AOD job processing logic in the GEOSdas.csm file needs to be cleaned up.
In the 3DVar case, AOD can be run in parallel with GSI if enough CPUs are available for both. Otherwise, AOD should be submitted as a separate job, and GCM processing should be held up until AOD completes. This logic is pretty much already in the code.
In the ensemble case, AOD needs to be run prior to GSI processing. There is no need to run it as a separate job. It just needs to be run and completed prior to starting the GSI. It cannot be run in parallel with the GSI.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the AOD job-processing logic in GEOSdas.csm first. Trace the 3DVar path for available CPUs and separate-job submission, then compare it with the ensemble path. Done means AOD runs in parallel with GSI only when resources allow in 3DVar, while ensemble AOD completes before GSI and GCM waits when required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fortran
- Domain
- hpc
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100