We currently have three catalogs for different CESM output accessible from cheyenne / dav (excluding the CMOR-ized CMIP output): campaign-cesm2-cmip6-timeseries, glade-cesm1-cmip5-timeseries, and glade-cesm1-le (which should actually point to data on campaign storage and be renamed campaign-cesm1-le. I think all three of these should follow the same naming convention for columns in the csv file, and should include
experiment
case
file_fullpath
file_basename
date_range
sequence_order
member_id
component
grid
stream
variable
year_offset
parent_experiment
parent_member_id
branch_year_in_parent
branch_year_in_child
pertlim
With the following notes:
- If
branch_year_in_parent == branch_year_in_child, can we define the catalog with a YAML file that simply specifies branch_year and sets both columns to that one value?
- If
pertlim is not specified in the YAML file, it should be set to zero.
I've toyed with the idea of including a machine column as well, namely as a way to note the differences between ensemble members 101 - 105 and 001 - 005 in the CESM1 Large Ensemble, but I think that might be too burdensome when creating future catalogs. I'm open to other peoples' thoughts on that, though.
Note that this issue supercedes #48 and #53 and a solution will do the same to PR #49 so I will close them in favor of tracking conversation in a single place (namely this ticket).
We currently have three catalogs for different CESM output accessible from cheyenne / dav (excluding the CMOR-ized CMIP output):
campaign-cesm2-cmip6-timeseries,glade-cesm1-cmip5-timeseries, andglade-cesm1-le(which should actually point to data on campaign storage and be renamedcampaign-cesm1-le. I think all three of these should follow the same naming convention for columns in the csv file, and should includeWith the following notes:
branch_year_in_parent == branch_year_in_child, can we define the catalog with a YAML file that simply specifiesbranch_yearand sets both columns to that one value?pertlimis not specified in the YAML file, it should be set to zero.I've toyed with the idea of including a
machinecolumn as well, namely as a way to note the differences between ensemble members 101 - 105 and 001 - 005 in the CESM1 Large Ensemble, but I think that might be too burdensome when creating future catalogs. I'm open to other peoples' thoughts on that, though.Note that this issue supercedes #48 and #53 and a solution will do the same to PR #49 so I will close them in favor of tracking conversation in a single place (namely this ticket).