Open mahf708 opened 1 day ago
For rhist files, you have [case_name].[model_name].rhist.[any_string].[output_spec].[restart_spec].[date_spec].nc
. I don't think we need to put [restart_spec]
in the filename. The driver (or, better the OM) can reconstruct the rest from runtime options, but with this pattern it would have to know restart_specs of the previous run, which is annoying. Besides, with [any_string].[output_spec]
in the filename, we are already guaranteed to be unique. Also, without [restart_spec]
, the .h file name is very close to the .rhist file name, so we can easily match them.
Side question: do ppl prefer .h
or .hist
? I don't have a strong preference, but since we have .rhist
, having .hist
may make things more consistent? Dunno, just a thought. I'm fine either way.
Maybe just .h
and .rh
? To call them history files feels anachronistic to me anyways, so might as well bury the meaning entirely while minimizing name length?
We should likely settle on a naming scheme for our IO. Currently, we have three different file classes of interest, with differing schemes
Proposed changes
Some notes
Rationale
Comment and vote below!