Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Please send Shaocheng a tentative title for each paper listed here.
  • Think about papers that you could write, especially papers focussed on ACME v1 model developments.
  • Brief explanations of each paper:
    • Hui, Kate, and Chris Terai have papers already submitted
    • Papers in preparation:
    • Po-Lun Ma:
      • Writing paper on aerosol indirect effects, and observational constraints from satellite simulator
      • Tuning papers: I can't write all these papers by myself.  If anyone is interested in any of the tuning experiments and wants to write it up, please come get the climo files from me.
    • Hailong: almost ready to submit paper on ACME aerosol radiative forcing, indirect effect
    • Susannah: writing paper on impact of marine organic emissions in ACME
    • Kai: working on paper on water conservation issues, would like to submit as soon as possible.
    • Yuying: working on paper on COSP simulator.  Plan to submit it in a month or two.
    • Salil: Looking at impact of NAO on extremes, would like to submit in GRL before end of year.
    • Wuyin: Paper focussed on tuning exercise, practical realities of tuning with limited resources.  How to use CAPT to tune the physics and quickly tune the physics response.
    • Yun: Hui and I have done the PPE simulations and will write a paper documenting the framework for UQ analysis and optimization.
    • Regionally-refined model paper was left off the list – it is in development but there were some issues with the v0.3 model, need to update thte model version that we use.
  • Shaocheng, a lot of papers based on v0 model.  Will we repeat these for v1?
    • Phil: sometimes we might write a paper about a methodology, other times we might want to write papers documenting the differences between the old and new models
  • Rich Neale: for v1, is it worth drawing a line and choose a version to run with that can be used to do science, with high-resolution output.
    • Phil: These are the papers that were already started.  There are a slew of papers that I think will be written about the v1 model.
  • Renata: add new planned papers to this list (or update them): Submit New Atmosphere Publication/wiki/spaces/ATM/pages/72450145


Diagnostics Discussion ACME_ATM_diags_discussion.pdf

...

  • 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.
    • Peter: I'm hearing ideas about different cool things we could do with diagnostics, keep thinking about that.  Also we should think about what requirements we would have.  I have a list of ideas (in the slides), but are there things missing?