taylor13

some questions for clarification: 1. If you ignore the warning, are you already able to do what you want? 2. If yes, then I guess you're just asking whether we...

I want to be sure I understand your "small use case". Is the following correct: the variable of interest: 12 2d fields the latitude of each grid cell: 1 2d...

I'm afraid I don't understand the publisher well enough to know how it is supposed to work. As you probably know, a single released version of the CMOR tables is...

I was planning to speak with Sasha today about this, but he is on travel until next week. Assuming the default tables accessed by the publisher (based on "data_specs_version") can...

to be sure, multiple CMOR/PrePARE CMIP6_CV.json tables are associated with a single data request release (such as 01.00.27), so tagging a CMIP6_CV.json with 01.00.27 may not get you to the...

oh, that's pretty cool. So the publisher will generate a new CMIP6_CV.json, drawing on the one tagged, e.g., 01.00.27, but modifying the part of that .json that is taken from...

Got it (I think). you end up with the .json files that contain data request information from the CMOR table release tagged with the number retrieved from "data_specs_version". But you...

Not sure about this, but I thought the cmor_version was supposed to list the first version of CMOR that would be able to read and interpret a table correctly. If...

@dnadeau4 is cmor_version read from these tables? If so, is it used in any way by CMOR3? If the answer is no to either one of the above, then Paul's...

Perhaps we should include all 3 integers in cmor_version, and it's value should be set to the latest existing version of CMOR (at the time any of the tables was...