Changes between Version 38 and Version 39 of CDDS

Timestamp:

11/12/19 12:09:19 (4 months ago)

Author:

valeriu

Comment:

—

CDDS

@@ -77 +77 @@
 use FILEPATHSTYPE="ARCHER" since this way the dir structure will comply with the Archer-type paths. We '''DO NOT''' support any other type of input data directory structure.
 
-5. Create the json request file, naming the same as {{{$REQUEST_JSON}}} set in 4. -- here's the one used in our example. Much of the information listed here is taken directly from the rose-suite.info file for the UM model suite that generated the data (u-bh543 for our example)
+5. Create the json request file, naming the same as {{{$REQUEST_JSON}}} set in 4. -- here's the one used in our example. Much of the information listed here is taken directly from the rose-suite.info file for the UM model suite that generated the data (u-bh543 for our example) - '''REMEMBER''' to consult https://rawgit.com/WCRP-CMIP/CMIP6_CVs/master/src/CMIP6_experiment_id.html and https://github.com/WCRP-CMIP/CMIP6_CVs/blob/master/CMIP6_experiment_id.json for information about individual experiments, specifically how to set your {{{parent_experiment_id}}} variable in the json file!!
 {{{
 {
@@ -177 +177 @@
 }}} 
 
-== 7. Move CMOR data to ESGF ==
+== 7 Bookkeeping your runs ==
 
+It is important to have a record of your run(s) both for debugging purposes and for knowing which runs have been done. For this purpose, please update the table here https://github.com/cedadev/jasmin-cdds/issues/31
+and follow the instructions here https://github.com/cedadev/jasmin-cdds/tree/master/cdds_runs how to upload to gitHub the files that need to be logged and linked to the table. Contact V or Ag if any issues with gitHub.
+
+== 8. Move CMOR data to ESGF ==
+