Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
aerocom:data_submission [2019-04-23 11:09:04] jang [7) LOG FILE SUBMISSION] |
aerocom:data_submission [2022-05-31 09:29:31] (current) |
||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ATTENTION - THIS WIKI PAGE IS NO LONGER UPDATED - PLEASE GO TO [[http:// | ||
+ | |||
+ | |||
AeroCom | AeroCom | ||
Line 16: | Line 19: | ||
Each variable should be stored in ONE cf-compliant NetCDF file, which includes all time steps for a given year. The list of variables to be output is provided in a spreadsheet per experiment and a description is provided in the experiment specifications document on the same wiki page. | Each variable should be stored in ONE cf-compliant NetCDF file, which includes all time steps for a given year. The list of variables to be output is provided in a spreadsheet per experiment and a description is provided in the experiment specifications document on the same wiki page. | ||
- | CF-compliance implies that sufficient attributes, coordinates and coordinate describing variables are included in each file to describe metadata needed to understand grid representation, | + | CF-compliance implies that sufficient attributes, coordinates and coordinate describing variables are included in each file to describe metadata needed to understand grid representation, |
See also frequently asked questions on CF: [[https:// | See also frequently asked questions on CF: [[https:// | ||
Line 67: | Line 70: | ||
...for METNO aerocom servers and WIKI documentation server | ...for METNO aerocom servers and WIKI documentation server | ||
- | An account at Met.No is needed to submit data via ftp and edit [[aerocom: | + | An account at Met.No is needed to submit data a data server (aerocom-users.met.no) |
Line 76: | Line 79: | ||
| | ||
- | Large submissions (> 100 GB) may require extra attention (use rsync, scftp). They might require prior coordination with Met.No/Anna Benedictow/ | + | Large submissions (> 100 GB) may require extra attention (use rsync). They might require prior coordination with Met.No/Anna Benedictow/ |
On aerocom-users.met.no the directory / | On aerocom-users.met.no the directory / | ||
Line 84: | Line 87: | ||
===== 6) notify met.no ===== | ===== 6) notify met.no ===== | ||
- | When files are uploaded send email to anna.benedictow@met.no and jan.griesfeller@met.no and michael.schulz@met.no (AND coordinator of project), so that the files can be transferred from the ftp disk or aerocom-users to the database. When the data are included in the database the files appear on aerocom-users.met.no under / | + | When files are uploaded send email to anna.benedictow@met.no and jan.griesfeller@met.no and michael.schulz@met.no (AND coordinator of project), so that the files can be transferred from aerocom-users.met.no |
- | After the data are transferred to the database, data are removed from ftp server or aerocom-users: | + | After the data are transferred to the database, data are removed from aerocom-users: |
Line 93: | Line 96: | ||
- | ===== 8) UPDATES | + | ===== 8) updates |
In case of updates of files, the model version identifier should also contain information on the resubmission of model results. Additional files which do not change an earlier submission may contain the same version number as an older submission. Corrections and a model rerun should be accompanied by a new model version identifier. Old still valid files may be merged upon request with new data. Old versions of model submissions will be temporally moved to a separate directory by Met.No, and where possible, deleted after some time. An exception will be made for versions that have been used in publications. Modellers are responsible for communication of major updates to their models (e-mail and log-files, see below). Model analysers are responsible for frequently verifying changes in model submissions (e.g. before submitting a paper). | In case of updates of files, the model version identifier should also contain information on the resubmission of model results. Additional files which do not change an earlier submission may contain the same version number as an older submission. Corrections and a model rerun should be accompanied by a new model version identifier. Old still valid files may be merged upon request with new data. Old versions of model submissions will be temporally moved to a separate directory by Met.No, and where possible, deleted after some time. An exception will be made for versions that have been used in publications. Modellers are responsible for communication of major updates to their models (e-mail and log-files, see below). Model analysers are responsible for frequently verifying changes in model submissions (e.g. before submitting a paper). | ||