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:06:01] jang [2) ADJUST FILENAMES] |
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 54: | Line 57: | ||
- | ===== 3) CHECK FORMAT | + | ===== 3) check format |
Typical files must be checked prior to submission via a cf-compliance-checker. [[http:// | Typical files must be checked prior to submission via a cf-compliance-checker. [[http:// | ||
Line 63: | Line 66: | ||
- | ===== 4) OBTAIN ACCOUNT | + | ===== 4) obtain account |
...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) |
- | ===== 5) TRANSFER DATA ===== | + | ===== 5) transfer data ===== |
After obtaining an account, data can then be uploaded to the aerocom user server aerocom-users.met.no: | After obtaining an account, data can then be uploaded to the aerocom user server aerocom-users.met.no: | ||
* Create a directory under / | * Create a directory under / | ||
Line 76: | Line 79: | ||
| | ||
- | Large submissions (> 100 GB) may require extra attention (use rsync, scftp, not simple ftp clients). 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 83: | Line 86: | ||
- | ===== 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: |
- | ===== 7) LOG FILE SUBMISSION | + | ===== 7) submit a log file ===== |
- | FOR EACH SUBMISSION: Put an entry into the htap wiki page [[modelupdates|Log file]], describing what has been submitted. This is also obligatory if changes or updates (even partial) to the original submission are made. We also request | + | FOR EACH SUBMISSION: Put an entry into the htap wiki page [[modelupdates|Log file]], describing what has been submitted. This is also obligatory if changes or updates (even partial) to the original submission are made. We also request |
- | ===== 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). | ||