...
- SE/CPL use cdash originally for nightly tests, was flushing the test after a night, cdash corrected that , display on the dashboard, works very well, . Workflow also happy with cdsh.
- ctest works with batch? Might need an additional script.
- Use Jenkins
- Workflow is working on pushing test to dashboard and using Jenkins
- SE/CPL - 'create-test' - it is custom, comes with the system, being reworked to by parallel to run tests (>70 system tests) . UVCDAT has 600 tests.
- Workflow uses 'ctest' and cmake, Andy thinks they will work on that for ACME in the summer
- cdash can now capture timing info and flag "fail" if it take longer then before.
- kitware working on buildbot and github integration.
- We could have our own cdash server for more customization.
- SE - every test has its own executable , Anshu Dubey (Unlicensed) says 'flashtest' has also dashboad (reference to the FLASH paper:
- ACME license discussion - it will be modified BSD, need a discussion on how to license the data as well and restrictions, also need to settle on who holds copyright.
- Workflow is moving into using Anaconda (python package/container manager) and Docker container for both UV-CDAT and ESGF. SE is looking at Docker. You can run docker using MPI on HPC. Need the right Linux distro.
...
- Classic Viewer runs in ORNL only for now, we have a viewer that you can download to your machine to look at the diagnostics
- Kate Evans (Unlicensed) has some different diagnostics to be also displayed in the Classic Viewer, contact John to add that to the viewer
- Sam's offline viewer can display other data, needs a jason file to
- Chris Golaz – we will have 200 years of data non Edison next week, it would be great if workflow will take that to exercise the diagnostic on it and show to others how to work on it, document on confluence
- Kate has a top 10 plots to do for coupled, that needs to be added and created for the edison run– this is python scripts (contact Marcia Branstetter (Unlicensed))
- colormap is now flexible in uvcdat, workflow priority is to make Chris happy, then they will check with Atmosphere for next priorities, Chris can be a person to interface atmosphere and workflow for setting next priorities
- Chris likes the plots to be at NERSC so that he can share them to others, Dean we need to have Classic Viewer at NERSC
- Phil - it does not need to go to NERSC, but it can be done in other ways
- Classic Viewer is at ORNL, metadiags will automatically push the data and plots to CADES and enable Classic Viewer to display them, anyone can then view them, moving data is part of the script, it is done automatically, Kate – there is an authentication issue.
- Question on checking if the data is good enough to share with others, Chris is doing it on NERSC, he creates climo files and uses AMWG to display results, then shares with others through NERSC. We would then use metadiags to move the data to CADES and publish data to ESGF.
- There is a webinar and links to other online documentation on how to use publishing services on Workflow, see – /wiki/spaces/WORKFLOW/pages/66519289
Atmosphere Group Notes
/wiki/spaces/ATM/pages/71336556
...
SE needs ne16 and even ne8 versions of all IC/BC files for fast-running tests. .
SE-Ocean:
Andy summarized the CMDV-software proposal.
3D field transfer is on critical path for v2 ocean-ice plans.
metis offline vs. online. Would be good to have a "dumb" mode for online metis. Doing everything metis can do online would require lots of MPAS mods so still want offline metis files.
MPAS uses buildbot for testing. Still need to work on code coverage.
Performance Group Notes
/wiki/spaces/PERF/pages/73793546
...