| Version 2 (modified by acc, 3 years ago) (diff) |
|---|
VLD-05_Coward_SETTE_inputs
Last edition: Wikinfo(changed_ts)? by Wikinfo(changed_by)?
The PI is responsible to closely follow the progress of the action, and especially to contact NEMO project manager if the delay on preview (or review) are longer than the 2 weeks expected.
Summary
| Action | VLD-05_Coward_SETTE_inputs |
|---|---|
| PI(S) | Andrew Coward |
| Digest | Rationalisation of SETTE inputs |
| Dependencies | If any |
| Branch | N/A |
| Previewer(s) | Names |
| Reviewer(s) | Names |
| Ticket | #2637 |
Description
Collection and rationalisation of SETTE inputs. The set of input files for the full suite of SETTE tests has evolved rapidly to keep pace with changes to the code (such as the removal of haloes from external files). The current set needs to be cleaned of unused data and chunked and compressed with setting consistent with exascale ambitions. A definitive set then needs to be hosted in a publically available location with a fixed DOI. A lighter version (for example, reduced time-levels in forcing data) may also be appropriate for future containerisation or cloud-deployment of testing services.
...
Implementation
Stage 1: Collect all input file sets for SETTE 4.2_RC (current trunk). Confirm successful SETTE results and store reference set of SETTE results. Remove redundant files and variables from contents. Make sure sensible chunking and compression choices have been made in all cases. Produce clean 'r4.2_RC_FULL' set
Stage 2: Reduce data volumes by selecting only sufficient forcing data for twice the period of each standard test. Run SETTE with reduced set and confirm unchanged results. Create recommended 'r4.2_RC' set
Stage3: Reduce data volumes further by limiting number of significant digits in all fields other than domain and coordinate variables. Confirm SETTE tests are still successful (results WILL be different). Create optional 'r4.2_RC_LITE' set.
Stage 4: Find a hosting and distribution option
Stage 5: Document and archive scripts so that the process can be repeated if(when) changes are made to the FULL set.
...
Documentation updates
...
Preview
...
Tests
...
Review
...
