Gary Strand

Adam nails every issue exactly. My only comment is that for Tier 3 it would be nice for all components to use the same fixed absolute time start date of...

There's a discussion of this issue here https://github.com/cf-convention/cf-conventions/issues/298

"time_bounds" doesn't make sense for instantaneous values, and for our MIP data, instantaneous data aren't required to have it for the time axis. I'd leave it out of instantaneous output...

"time_bounds" isn't applicable for an instantaneous value, so it's not needed. The critical issue about differentiating instantaneous and averaged fields is keeping them separate. It's not uncommon to save the...

Getting all components to have the same "days since YYYY-MM-DD HH:MM:SS" units for time and time bounds is more important at this point, IMHO. If it's not unreasonable to have...

It's true that while cell_methods is the canonical means to determine if a field is averaged or instantaneous, that can only be determined by opening and inspecting the file. Given...

Thanks, @phillips-ad, for succinctly describing the two choices. One issue is that output file naming is only by convention, not enforced requirements. "cam.h0" is traditionally monthly-means, "cam.h1" is daily data,...

> > @gold2718, at some point some years ago, CAM output was changed from "cam2.h[0-9]" to "cam.h[0-9]", without too much fuss, so I expect something similar will be done to...