taylor13
taylor13
I didn't see the suggestion to check that the cmor_table value is part of the file name, but it would be good thing to do (but not critical).
I don't think CMOR needs to check this, but PrePARE should check and it would be a good idea to make the check smart enough to only consider the stuff...
Yes, this is a good idea. Not sure I will have time soon to think about this.
Running PrePARE on a million files (if that is what is suggested), especially the very large files in the CMIP6 archive, would seem to be inefficient, and perhaps not even...
I'm not sure the number of files matters, especially if they are all QC'd files in the CMIP6 archive. How would such files test PrePARE's ability to identify *non-compliant* files?...
Yes. If you note them somewhere else, this issue can be closed.
Before rewriting PrePARE, we'll need to write down a prioritized lists of things we want to check. We can then see if this one is high enough priority to include...
To expand on the above, we shouldn't need to define the lat and lon coordinates for two monthly mean fields, just because they happen to be hosted in two separate...
Originally, we had different string lengths for different attributes, but that go simplified, as I recall, so that all have the same length 1024 (internally in CMOR). I think there...
Would it be difficult to double the length of the ``references`` attribute, but not the others? Would this cause any problems? Would doubling be sufficient? Note that if any single...