Optional mass accumulation table in 1-month benchmark #216
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… option The mass accumulation table compares the difference in mass change for each species across two different runs, ref and dev. The mass change per species is computed as the difference between start and end based on values in the restart files (end restart mass minus start restart mass). Concentrations are converted to mass in the same way as done for the benchmark mass tables. This table can be used with the operations budget table to look at changes in mass across a run, and to validate the operations budget diagnostics. Its values correspond to the ACCUMULATION entries in the operations budget table and is an alternative (and cheaper) way to get those values. The table is currently only produced for full column and is limited to the 1-month benchmark. Signed-off-by: Lizzie Lundgren <elundgren@seas.harvard.edu> initial commit Signed-off-by: Lizzie Lundgren <elundgren@seas.harvard.edu>
…hmark This table is optional and is off by default. Signed-off-by: Lizzie Lundgren <elundgren@seas.harvard.edu>
lizziel
force-pushed
the
feature/add_mass_accumulation_table_to_1mo_benchmark
branch
from
d944f43 to
51b4e8b
Compare
hannahnesser
pushed a commit
to hannahnesser/gcpy
that referenced
this pull request
Jan 22, 2024
This merge brings PR geoschem#216 (by @lizziel) into the GCPy 1.4.0 development stream. PR geoschem#216 adds an option for a mass accumulation table (full column only) as a 1-month benchmark option. The mass accumulation table compares the difference in mass change for each species across two different runs, ref and dev. The mass change per species is computed as the difference between start and end based on values in the restart files (end restart mass minus start restart mass). Concentrations are converted to mass in the same way as done for the benchmark mass tables. Signed-off-by: Bob Yantosca <yantosca@seas.harvard.edu>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Name: Lizzie Lundgren
Institution: Harvard University
Description:
The PR adds a mass accumulation table (full column only) as a 1-month benchmark option. The mass accumulation table compares the difference in mass change for each species across two different runs, ref and dev. The mass change per species is computed as the difference between start and end based on values in the restart files (end restart mass minus start restart mass). Concentrations are converted to mass in the same way as done for the benchmark mass tables.
Here is an example of what the accumulation table looks like.
This table can be used with the operations budget table to look at changes in mass across a run, and to validate the operations budget diagnostics. Its values correspond to the ACCUMULATION entries in the operations budget table and is an alternative (and cheaper) way to get those values.
The table is currently only produced for full column and is limited to the 1-month benchmark. It can be expanded in a future PR if there is demand.
Expected differences:
None. This table is off by default in the 1-month benchmark yaml configuration file.