You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some streams files are intended to be static, but that's seemingly not allowed. Instead, every streams file (and, presumably, every variable being read from streams files) must have a time axis. This requires the addition of a "dummy" time axis on files that don't need it.
I think it would be better if a time axis were optional. This would make the code cleaner (avoiding time-related stuff that's not needed), avoid headaches (making an input file but forgetting to add the dummy time axis), and improve strictness (throw an error if a user supplies a streams file with a time axis for an input that's supposed to be static).
As far as what this would look like, I'd think the following arguments to shr_strdata_init_from_inline() would be made optional:
stream_yearFirst
stream_yearLast
stream_yearAlign
stream_offset
stream_taxmode
stream_dtlimit
stream_tintalgo
If any of these were provided, then the streams file would require a time axis, and all those arguments would need to be provided.
If those arguments weren't provided but the user-supplied streams file does have a time axis, CDEPS would throw an error.
The text was updated successfully, but these errors were encountered:
Of course, the data file still need to have time axis to support this. CDEPS always requires it to read data. I am not sure if we could make those variables optional in the namelist file. BTW, this is ESMF config format which is not used by the CESM as I know. CESM used XML instead.
Yes, it's possible to handle static streams files by just supplying a file with one timestep. We do it in at least three places in CTSM, plus one more that I'm working on now. My point is that it's annoying to have to do, for the reasons I outlined up above.
Some streams files are intended to be static, but that's seemingly not allowed. Instead, every streams file (and, presumably, every variable being read from streams files) must have a time axis. This requires the addition of a "dummy" time axis on files that don't need it.
I think it would be better if a time axis were optional. This would make the code cleaner (avoiding time-related stuff that's not needed), avoid headaches (making an input file but forgetting to add the dummy time axis), and improve strictness (throw an error if a user supplies a streams file with a time axis for an input that's supposed to be static).
As far as what this would look like, I'd think the following arguments to
shr_strdata_init_from_inline()
would be made optional:stream_yearFirst
stream_yearLast
stream_yearAlign
stream_offset
stream_taxmode
stream_dtlimit
stream_tintalgo
If any of these were provided, then the streams file would require a time axis, and all those arguments would need to be provided.
If those arguments weren't provided but the user-supplied streams file does have a time axis, CDEPS would throw an error.
The text was updated successfully, but these errors were encountered: