geoschem / gcpy

Python toolkit for GEOS-Chem. Contains basic plotting scripts, plus the suite of GEOS-Chem benchmarking utilities.
https://gcpy.readthedocs.io
Other
51 stars 24 forks source link

[FEATURE REQUEST] Transport tracer benchmark improvements #288

Open lizziel opened 10 months ago

lizziel commented 10 months ago

Name and Institution (Required)

Name: Lizzie Lundgren Institution: Harvard University

New GCPy feature or discussion

This issue is to document some nice-to-haves that I notice as I run the transport tracer benchmark code. None of this is urgent or even necessary, but it would be good to list it somewhere. Maybe one day we can make the updates.

  1. Copy the yaml configuration file to each of the benchmark output folders. This would give a record of the paths and settings used when running the benchmark and make it easier to rerun.
  2. An alternative to 1 above is to print all of the data path information to the log. Currently the log includes the path to the species database but not the paths to the data being compared.
  3. It would be useful to create mass conservation tables for both ref and dev. Right now you can only generate it for dev.
  4. The passive mass table (global mass time series) does not include version string in header and also only prints dev. It would be easier to read if the version string is included (not just the run directory name), along with both ref and dev.
  5. Compare ref and dev RnPbBe budget tables in one file. Currently ref and dev are sent to separate files and no comparison is done.
  6. Include day of month in mass table filenames. It is not obvious from the filename (e.g. Oct2019, Apr2019) that the mass is taken from the restart file and therefore is an instantaneous value.
  7. Include emissions plots and tables like we do for the full chemistry simulation.

I will keep adding to this as I run into more.

yantosca commented 9 months ago

@lizziel: Several of these updates are being addressed by PR #305.

yantosca commented 7 months ago

Point 3 above is being addressed by PR #309