... | ... | @@ -37,4 +37,8 @@ Our recommendations for header structure are based on the requirements stated ab |
|
|
|
|
|
### File Name Recommendations
|
|
|
Exempt from the SOLARNET recommendations for filenames:
|
|
|
> We recommend that file names only contain letters A-Z and a-z, digits 0-9, periods, underscoresand plus/minus igns. Each component of the file name should be separated with an underscore – not a minus sign. In this regard, a ange may be considered a single component with a minus sign between the min and max values (such as start/end ate). File name components with numerical values should be a) preceded with one or more identifying letters, and ) iven in a fixed-decimal format, e.g. (00.0300). Variable-length string values should be post-fixed with nderscores o a fixed length. Another common practice has been to start the file name with the “instrument name” – although typically defined in a consistent manner only on a per mission or per observatory basis - i.e. collisions may ppear with other missions. Thus, we recommend prefixing the instrument name with a mission or observatory dentifier (e.g. iris for IRIS or sst for SST). After the instrument name, the data level is normally encoded as e.g. “l0” and “l1” for level 0 and 1. Note, however, that the definitions of data levels are normally entirely roject/instrument-specific and does not by itself uniquely identify what kinds of processing have been applied. Within each data set it is often very useful to have file names that can be sorted by time when subject to a exical sort (such as with “ls”). This requires that the next item in the file name should be the date and time (YYYYMMDD_HHMMSS[.d]). The “d” part is fractional seconds, with enough digits to distinguish between any two consecutive observations. |
|
|
> We recommend that file names only contain letters A-Z and a-z, digits 0-9, periods, underscoresand plus/minus igns. Each component of the file name should be separated with an underscore – not a minus sign. In this regard, a range may be considered a single component with a minus sign between the min and max values (such as start/end ate). File name components with numerical values should be a) preceded with one or more identifying letters, and b) given in a fixed-decimal format, e.g. (00.0300). Variable-length string values should be post-fixed with underscores of a fixed length. Another common practice has been to start the file name with the “instrument name” – although typically defined in a consistent manner only on a per mission or per observatory basis - i.e. collisions may appear with other missions. Thus, we recommend prefixing the instrument name with a mission or observatory identifier (e.g. iris for IRIS or sst for SST). After the instrument name, the data level is normally encoded as e.g. “l0” and “l1” for level 0 and 1. Note, however, that the definitions of data levels are normally entirely project/instrument-specific and does not by itself uniquely identify what kinds of processing have been applied. Within each data set it is often very useful to have file names that can be sorted by time when subject to a lexical sort (such as with “ls”). This requires that the next item in the file name should be the date and time (YYYYMMDD_HHMMSS[.d]). The “d” part is fractional seconds, with enough digits to distinguish between any two consecutive observations.
|
|
|
|
|
|
tldr: make your filenames like this:
|
|
|
|
|
|
instrument_YYYYMMDD_HHMMSSFFF_other_fields_separated_by_underscore.fits |