Adam Phillips

@billsacks thanks for writing this up. I can definitely come up with a list of proposed changes to output ancillary variable attributes as I'm one of the folks who is...

There are more inconsistencies across the components for the output time/time_bounds arrays beyond the naming of the time_bounds arrays. Below is a summary list of potential changes. Examples by component...

I'm honestly ambivalent on this, so I will defer on leaving time_bounds off. In response to @strandwg 's question, I believe average, min and max will be in one stream,...

After today's CISM meeting, I realized that we never spoke again of the fact that some components set time units to the start of the run with "days since YYYY-MM-DD...

I see a few priorities that have the potential to compete with one another: - Implement the changes detailed [above](https://github.com/ESCOMP/CESM/issues/194#issuecomment-961443965) with the possible exception of the Tier 3 change. -...

> That reminds me... maybe we should take this opportunity to drop the "2" from "clm2.h*"... or even go so far as to rename from "clm2" to "ctsm". Ha, that's...

@dabail10 the current plan is for a python-only CVDP release to happen in the latter half of 2024. That release will not have all the current CVDP/CVDP-LE capabilities in it....

Yes Justin you got it. The CVDP will get confused if there's multiple timeseries present in a single directory for the same run and variable. Is it possible to remove...

Yes, the behavior would be the exact same. This has been the case since the first version of the CVDP. One could easily say I should have coded it better...

Looking at /glade/work/tking/cupid_project/other_cupids/nov17/CUPiD/examples/247v234/CVDP_output/b.e30_alpha07c_cesm.B1850C_LTso.ne30_t232_wgx3.247/ the namelist_byvar directory hasn't been created, which says to me that the package likely hasn't started as that is the first step.