...
- Ocean wants to use Anaconda/Conda , Milena asks on how to use Classic Viewer
- UV-CDAT is now build through Anaconda, Ocean analysis package is installable through and sits under Anaconda.
- Ashish there is Anaconda and Conda, Conda is only for installation
- Ocean – they do not have the name for the package yet, they will have it as a package in Anaconda
- Ocean will have their interactive python notebooks that will be in the repo as scripts, they will be then exported and distributed through anaconda
- Ocean do not have it under repo yet, they are working on it
- Ocean package will distribute both notebooks and python scripts
- Workflow asked if Ocean would like to leverage and use classic viewer to display the analysis plots
- Samuel Fries (Unlicensed) presented a more generic viewer. Todd would like a database on top of every analysis created and run through the viewer, to keep track of the different runs and analysis as a searchable database ('cinema' through Kitware funded through Oscar very similar)
- obs data - they do not have it in repo yet, not a lot of data so far ~ a GB (Ashish - d not use githab for that then)
- Rob should be able to help to put the obs into the repo
- publishing Ocean analysis data to ESGF, use triage hub to for publication needs
Workflow - Performance
- provenance in implemented in CIME, fires up along the run, so even if the job dies you will get something, creates a world read/writable but some things are not, so someone has to clean it up (only works on ORNL but they will clean it up on Luster so it does need to be archived) on NERSC and MIRA it needs to be cleaned up manually users case and run directories
- Ben parses this data and puts into a database, Mark – can we then delete all other, Pat - this is not sufficient, there is more info there
- Pat you want stuff I am not collecting and I am collecting stuff you may not need
- send Pat email on confluence to update documentation on the provenance
- there are timers, profile timers per component, talk to Noel Keen about it, there are log files per simulated days it is captured in the coupler, profile timers are summaries - one text log file in case directory, only exist if the job finishes. When the jog is running you need to look at the coupler files
Atmosphere Group Notes
/wiki/spaces/ATM/pages/71336556
...