New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE REQUEST] Force GEOS-Chem Classic restart file to match simulation date #667
Comments
These updates are now in the |
@msulprizio Could you clarify for me what happens in 13.0.0 if the initial restart file's date doesn't match the simulation date? Are some species initialized to the background concentrations? This only affects GC-Classic right? One other question: As of 13.0.1 does the initial restart file's date need to match the simulation's start date? |
Hi @LiamBindle. In 13.0.0, the species concentrations from the GEOS-Chem restart entries ( As of 13.0.1, the default time cycle flag used for species concentrations from the GEOS-Chem restart was changed to With all of that said, the above descriptions apply to GEOS-Chem Classic only. For GCHP, the restart file reads are handled by MAPL. In GCHP (specifically in Chem_GridCompMod.F90), it looks like MAPL checks if the restart file exists and if it does not then it uses background species concentration values. That behavior hasn't changed in GCHP. @lizziel feel free to add on if I'm forgetting anything here. |
Thanks @msulprizio! |
The time cycle flags for the species concentration fields (
SPC_
) from the restart files were previously either (EY
orCYS
). In the case ofEY
, HEMCO would only read the restart file if the date in the restart file matched the simulation date, but would not crash if the correct date was not found. If GEOS-Chem then couldn't find the field from HEMCO, it would set initial species concentrations to the default background values specified in the species database. In the case ofCYS
, HEMCO would use the restart file for the closest available date. If it couldn't find a restart file then HEMCO would skip that field and GEOS-Chem would default to the background concentrations. In both cases, the user might not be aware of this behavior unless they inspected the GEOS-Chem log file.To avoid using restart files for the wrong date and/or defaulting to background species concentrations without the user's knowledge, we want to use the
EFY
flag for the SPC_ fields. This tells HEMCO to read the initial species concentrations from the restart file only if the date in the file matches the simulation date. If a restart file is not found, then the simulation will crash. Users can then take it upon themselves to modify the time cycle flag, but they will at least do so knowing how the initial concentrations will be handled by HEMCO.For some simulations, the sample restart file provided does not include all species in that simulation, so the
EFY
flag will always cause those simulations to crash out-of-the-box. To avoid this, we set the time cycle flag for theSPC_
entries toEY
so that HEMCO doesn't crash and GEOS-Chem will default to the background concentrations for any missing species. When users create a run directory for these simulations withcreateRunDir.sh
, a warning will print to the screen informing users that some species may be missing and to check their GEOS-Chem log file for details on how initial species concentrations are handled. The simulations that this impacts are: complexSOA_SVPOA, aciduptake, marinePOA, APM, tagCH4, tagO3, and POPs.The text was updated successfully, but these errors were encountered: