Lightweight object designed to centralize the file-naming logic (& any associated configuration).
Cholla pathnames traditionally followed the following template: "{outdir}{nfile}{pre_extension_suffix}{extension}.{proc_id}" where each curly-braced token represents a different variable. In detail:
{outdir} is the parameter from the parameter file. The historical behavior (that we currently maintain), if this is non-empty, then all charaters following the last '/' are treated as a prefix to the output file name (if there aren't any '/' characters, then the whole string is effectively a prefix.{nfile} is the current file-output count.{pre_extension_suffix} is the pre-hdf5-extension suffix. It's the suffix that precedes the file extension (or {extension}){extension} is the filename extension. Examples include ".h5" or ".bin" or ".txt".{proc_id} represents the process-id that held the data that will be written to this file. Previously, in non-MPI runs, this was omitted.
Instances can be configured to support the following newer file-naming template "{outdir}/{nfile}/{nfile}{pre_extension_suffix}{extension}.{proc_id}" where the the significance of each curly-braced token is largely unchanged. There are 2 things worth noting:
- all files written at a single simulation-cycle are now grouped in a single directory
{outdir} never specifies a file prefix. When {outdir} is empty, it is treated as "./". Otherwise, we effectively append '/' to the end of {outdir}
- Note
- This could probably pull double-duty and get reused with infile.
