-
Notifications
You must be signed in to change notification settings - Fork 157
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] Allow model to run with nested boundary conditions if you add a new species #268
Comments
Absolutely, we can add this as a functionality in GEOS-Chem 12.8.1. This capability already exists for restart files, so it would make sense to extend it to boundary conditions as well. We want users to be aware when species are skipped and background concentrations are used, so we always advise checking the log file to ensure species are being initialized with the expected concentrations. When species aren't found in the restart file (and soon-to-be BC files), a warning is listed in the log file saying it wasn't found and the background concentration (usually 1e-20 v/v) is used. |
…n BCs aren't found for a species To allow for nested grid simulations to proceed if a species isn't found in the boundary conditions file, we now apply the background species concentrations when the species cannot be found. The min, max, or background value applied for each species as boundary conditions will be printed to the log file. It is recommended that users check the log file to verify that the proper BCs are being read and applied. See also #268. Signed-off-by: Melissa Sulprizio <mpayer@seas.harvard.edu>
This issue is now fixed in commit 2c7ac9a and will be included in GEOS-Chem 12.8.1. |
…rations when BCs aren't found for a species This update was originally added in commit 2c7ac9a to Get_Boundary_Conditions routine in hcoi_gc_main_mod.F90, but was not translated over to the module hco_utilities_gc_mod.F90 that was introduced during HEMCO restructuring. The orinal commit message is included below: To allow for nested grid simulations to proceed if a species isn't found in the boundary conditions file, we now apply the background species concentrations when the species cannot be found. The min, max, or background value applied for each species as boundary conditions will be printed to the log file. It is recommended that users check the log file to verify that the proper BCs are being read and applied. See also #268. Signed-off-by: Melissa Sulprizio <mpayer@seas.harvard.edu>
…r CH4 inversions (1) Update Get_Boundary_Conditions to apply background concentrations when BCs aren't found for a species To allow for nested grid simulations to proceed if a species isn't found in the boundary conditions file, we now apply the background species concentrations when the species cannot be found. The min, max, or background value applied for each species as boundary conditions will be printed to the log file. It is recommended that users check the log file to verify that the proper BCs are being read and applied. See also geoschem#268. (2) Add EFY time cycle flag to HEMCO The EFY time cycle flag has been added to hco_config_mod.F90. This option will be used for meteorology fields to ensure the exact date is used (E), the data is found (F), and the simulation year is used (Y). (3) Do not read FLASH_DENS and CONV_DEPTH fields in FlexGrid when lightning NOx extensionin HEMCO is off A shadow variable Input_Opt%DoLightNOx has been added and will be set to true or false depending on if the lightning NOx extension is turned on in HEMCO_Config.rc. When that option is off, the reading of FLASH_DENS and CONV_DEPTH in flexgrid_read_mod.F90 will be skipped (keeping those fields as all zeroes). This will avoid the requirement of having users download those data for simulations that do not require it. For more details, see geoschem#279. Signed-off-by: Melissa Sulprizio <mpayer@seas.harvard.edu>
This merge brings PR #2213 (Change NEI 2D emissions to xy dimension, by @nicholasbalasus) into the GEOS-Chem "no-diff-to-benchmark" development stream. This PR implements a workaround to an issue caused by the merge of HEMCO PR #235 (Bug fix for vertical regridding). This must be merged simultaneously with HEMCO PR #268. Signed-off-by: Bob Yantosca <yantosca@seas.harvard.edu>
Hi support team!
Currently the model will run with a restart file even if you add a new tracer. However it will not do the same for boundary conditions. This makes it difficult to run nested sensitivity tests since you have to rerun the boundary conditions with the new species. Could we add this functionality to the model?
The text was updated successfully, but these errors were encountered: