...
- SE/CPL use cdash originally for nightly tests, was flushing the test after a night, they cdash corrected that , display on the dashboard, works very well, 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 (>600 >70 system tests) . UVCDAT has 600 tests.
- Workflow uses 'ctest' and cmake, Andy thinks they will work on that in the summer
- 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.
Workflow - Ocean/Ice
- 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
...
Land needs a way to work with external libraries. Some will have joint development within ACME. We don't want a ton more code in our ACME git repo. On the other hand, making a separate library means a separate build system and some of these need to be re-built daily with development. Possibly multiple compilers (for Fortran-C interfacing)
Under iESM code base, coupling between GCAM and ALM is not in coupler. GCAM is not really "of" the land because it provides emissions over ocean and can be run in a case without land.
Land code is getting convoluted in terms of what can be switched on and off. Anshu: standardize your API between the pieces. Build system can help.
Also land is having programming style divergence. Makes it hard to read. Need to stick to one style. Land should enforce internally until there is an ACME-wide style guide.
mksurfdat is getting slow.
SE needs ne16 and even ne8 versions of all IC/BC files for fast-running tests.
Performance Group Notes
/wiki/spaces/PERF/pages/73793546
...