...
- Coupled team had a severe need for a package to produce "top-ten" diagnostics. We produced this tool in response to their request.
- We designed it to be familiar to you, look-and-feel is similar to AMWG. But some improvements:
- Unlike AMWG, this package is python-based and modular.
- You can more easily add new plots, code to produce these can be written in python, but other languages can also be used if package can call/link to them.
- currently using matplotlib (in python)
- can use other things such as NCL if willing to maintain these on an "opt-in basis"
- Extensible to include tier 1B
- quick and easy to run, has validation, reproducibility
- conda-based (runs in conda python environment)
- Questions?
- Rich: Do you envisage this as a single script that could control all the Tier 1b collections? Could see some benefits, but also some drawbacks to doing it that way.
- Kate: could use this as a top-tier script that calls other things, or the other way around, or run it within a larger outer shell as one of a number of other things.
- Kate: hopefully people will work on improving components (e.g. the web page)
- Rich: graphics: how good are they at doing non-standard plots? Is the functionality really there in python?
- Answer: yes. Matplotlib is very powerful, lots of other community-contributed libraries and packages exist. PyNGL allows
- Scott: will you use this for doing regridding?
- Kate: Other ACME folks have developed regridding scripts which we are using.
- Philip: Will you have a set of automatically calculated metrics?
- Kate: yes we can add that.
- Todd: We could save these diagnostics in a searchable database. We should keep that forever. This is a form of provenance, then people would come back and look at it.
- Peter: I'm hearing ideas about different cool things we could do with diagnostics
- Phil: we have already thought about some of these issues, so maybe we can make connections between us.
- Susannah: Bibi Raju from the workflow team is based at PNNL and is working on database technologies for provenance, and we have been discussing that with them.
- Phil: Peter and Susannah and I also came up with some ideas about provenance that we would like to track, and some basic mechanisms for doing that which could set a "low bar" for provenance capture.
- Rich: Do you envisage this as a single script that could control all the Tier 1b collections? Could see some benefits, but also some drawbacks to doing it that way.