Differences
This shows you the differences between two versions of the page.
aerocom:data_submission [2013-12-12 16:54:38] michaels |
aerocom:data_submission [2022-05-31 09:29:31] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | AeroCom | ||
- | ==== SUBMISSION OF DATA PROCEDURE ==== | ||
- | Any submission of data to the AeroCom database requires to follow the following steps: 1) [[#FORMAT DATA|format data]] to agreed netCDF htap standards, cf compliant | ||
- | |||
- | << | ||
- | |||
- | === 1) FORMAT DATA === | ||
- | 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, | ||
- | |||
- | Formatting can be achieved with cmor tools (http:// | ||
- | |||
- | An example file as used for the previous AeroCom experiment is found here: http:// | ||
- | |||
- | << | ||
- | |||
- | ==== 2) ADJUST FILENAMES ==== | ||
- | The obligatory Filename for using the cf checker and the submission of data is | ||
- | |||
- | " | ||
- | |||
- | |||
- | < | ||
- | |||
- | < | ||
- | |||
- | < | ||
- | |||
- | < | ||
- | |||
- | < | ||
- | |||
- | < | ||
- | |||
- | << | ||
- | |||
- | ==== 3) CHECK FORMAT ==== | ||
- | Typical files must be checked prior to submission via the cf-compliance-checker. | ||
- | |||
- | Typical files? A check shall comprise at least one file of each VerticalCoordinateType and each Frequency and each experiment, best varying the variables! | ||
- | |||
- | << | ||
- | |||
- | ==== 4) OBTAIN ACCOUNT ON AeroCom SERVER ==== | ||
- | An account at Met.No is needed to submit data via ftp. A data server (aerocom-users.met.no) allows users also to access the data via ssh. Please contact jan.griesfeller@met.no for password and user name. You will then be notified further about the procedure. A public ssh-key has to be sent to Jan Griesfeller to activate the account. | ||
- | |||
- | << | ||
- | |||
- | ==== 5) TRANSFER DATA TO MET.NO ==== | ||
- | After obtaining an account, data can then be uploaded in two ways: | ||
- | |||
- | via ftp.aerocom.met.no: | ||
- | |||
- | via aerocom-users.met.no: | ||
- | |||
- | Very large submissions (> 10 GB) require prior coordination with Met.No/Jan Griesfeller& | ||
- | |||
- | << | ||
- | |||
- | ==== 6) NOTIFY MET.NO ==== | ||
- | When files are uploaded send email to jan.griesfeller@met.no AND michael.schulz@met.no, | ||
- | |||
- | After the data are transferred to the database, data are removed from ftp server or aerocom-users: | ||
- | |||
- | |||
- | << | ||
- | |||
- | ==== 7) LOG FILE SUBMISSION ==== | ||
- | 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 modelers to record on the wiki information on known bugs, or any other relevant information needed for analysis of the model results by others. | ||
- | |||
- | << | ||
- | |||
- | ==== 7) UPDATES / Error corrections ==== | ||
- | |||
- | 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). | ||
- | |||
- |