... | ... | @@ -17,7 +17,7 @@ We've compiled a list of requirements and recommendations for data quality and s |
|
|
|
|
|
Our recommendations and requirements are:
|
|
|
* Define what constitutes as an observation for your instrument. Help and examples can be found [here](standards_and_references/Observation-Segmentation)
|
|
|
* Use filenames that allow a direct association with an unique observation also see our [file name recommendations](https://gitlab.leibniz-kis.de/sdc/sdc_wiki/wikis/standards_and_references/FITS-Header-Specifications#file-naming-conventions)
|
|
|
* Use filenames that allow a direct association with an unique observation also see our [file name recommendations](https://gitlab.leibniz-kis.de/sdc/sdc_wiki/wikis/standards_and_references/FITS-Header-Specifications#file-name-recommendations)
|
|
|
* Ensure that your ***level1 science-ready data*** is as well formatted as possible. This means:
|
|
|
* ***ALWAYS*** adhere to the [FITS-Standard](https://fits.gsfc.nasa.gov/fits_standard.html)
|
|
|
* Adhere to the [SOLARNET fits Header recommedations](https://wolke7.leibniz-kis.de/s/yHRnLJEH9YgZj9f) as far as possible. This makes [formal description of observations](standards_and_references/Observation-Document-Structure) much easier for us. If you need help, feel free to contact us or look at our [list of header specifications](standards_and_references/FITS-Header-Specifications).
|
... | ... | |