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 [2013-12-12 17:06:09] michaels |
aerocom:data_submission [2022-05-31 09:29:31] (current) |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | AeroCom | + | ATTENTION - THIS WIKI PAGE IS NO LONGER UPDATED - PLEASE GO TO [[http:// |
| - | ==== 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 | ||
| + | AeroCom | ||
| - | === 1) FORMAT | + | ====== SUBMISSION OF DATA PROCEDURE ====== |
| - | Each variable should be stored in ONE cf-compliant netCDF file, which includes all time steps for a given year. The list of variables | + | Any submission |
| - | + | - [[#FORMAT DATA|format | |
| - | CF-compliance implies that sufficient attributes, coordinates and coordinate describing variables are included in each file to describe metadata needed to understand grid representation, | + | - [[#ADJUST FILENAMES |adjust filenames]] |
| - | + | - [[#CHECK FORMAT|check format]] with cf compliance checker, correct and check again | |
| - | Formatting can be achieved with cmor tools (http://www-pcmdi.llnl.gov/ | + | |
| - | + | - [[#TRANSFER DATA|transfer data]] to the aerocom-users.met.no | |
| - | An example file as used for the previous AeroCom experiment is found here: http://aerocom.met.no/ | + | - [[#NOTIFY MET.NO|notify metno]] that data have been submitted |
| + | - [[# | ||
| + | | ||
| + | ===== 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. | ||
| - | === 2) ADJUST FILENAMES === | + | CF-compliance implies that sufficient attributes, coordinates |
| - | The obligatory Filename for using the cf checker | + | |
| - | " | + | See also frequently asked questions on CF: [[https:// |
| - | OLD aerocom naming convention is also fine for now: | ||
| - | " | ||
| + | ===== 2) adjust filenames ===== | ||
| + | The obligatory filename for using the cf checker and the submission of data is:\\ | ||
| + | **aerocom3_< | ||
| - | < | + | Details about new file naming |
| + | [[https:// | ||
| - | <!ExperimentName> | + | Be aware of updates |
| - | < | + | versions will have a date attached.\\ |
| - | < | + | Examples: |
| + | * aerocom3_GOCARTv7.2_AP3-CTRL_od550aer_Column_2010_monthly.nc | ||
| + | * aerocom3_GISS-MATRIX-met2010_AP3-ACRI-AFRICA_od550aer_Column_2010_daily.nc | ||
| + | * aerocom3_GOCARTv7.2-met2010_AP3-CTRL-od550aer_Column_1850_monthly.nc | ||
| + | * aerocom3_GISS-MATRIX-fSST_AP3-CTRL-od550aer_Column_1850_monthly.nc | ||
| - | < | + | OLD (aerocom phase3) |
| + | **aerocom3_< | ||
| - | <Frequency> => " | + | OLD (aerocom phase 2) aerocom naming convention is also fine for now: |
| + | **aerocom_<ModelName>_< | ||
| - | <<Anchor(CHECK)>> | + | * <ModelName> |
| + | * < | ||
| + | * < | ||
| + | * < | ||
| + | * < | ||
| + | * < | ||
| + | * < | ||
| + | * < | ||
| - | === 3) CHECK FORMAT === | ||
| - | Typical files must be checked prior to submission via the cf-compliance-checker. | ||
| - | Read also there the help section. Note: Errors indicate section in the original | + | ===== 3) check format ===== |
| - | [[http://cf-pcmdi.llnl.gov/documents/cf-conventions/ | + | Typical files must be checked prior to submission via a cf-compliance-checker. |
| - | Typical files? A check shall comprise at least one file of each VerticalCoordinateType and each Frequency and each experiment, best varying | + | For the upload checker you want to check a typical but small file. To achieve this, you can cut out the first time steps with the nco command: |
| + | ncks -O -d time,0,10 sourcefile.nc filetest.nc | ||
| + | Per default, a check shall comprise at least one file of each VerticalCoordinateType and each Frequency and each experiment, best varying the variables! | ||
| - | === 4) OBTAIN ACCOUNT === | ||
| - | 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. | ||
| + | ===== 4) obtain account ===== | ||
| - | === 5) TRANSFER DATA === | + | ...for METNO aerocom servers and WIKI documentation server |
| - | After obtaining an account, data can then be uploaded in two ways: | + | |
| - | via ftp.aerocom.met.no: | + | An account at Met.No is needed to submit data a data server (aerocom-users.met.no) via ssh and edit [[aerocom:|AeroCom wiki pages]]. Please contact jan.griesfeller@met.no |
| - | via aerocom-users.met.no: | ||
| - | Very large submissions (> 10 GB) require prior coordination with Met.No/Jan Griesfeller&Michael Schulz via email, | + | ===== 5) transfer data ===== |
| + | After obtaining an account, data can then be uploaded to the aerocom user server aerocom-users.met.no: | ||
| + | * Create a directory under /media/ | ||
| + | * upload | ||
| + | | ||
| + | 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 / | ||
| - | === 6) NOTIFY MET.NO === | + | If correct in format and with correct file names, results |
| - | When files are uploaded | + | |
| - | After the data are transferred to the database, data are removed from ftp server or aerocom-users: | ||
| + | ===== 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 aerocom-users.met.no to the database. When the data are included in the database the files appear on aerocom-users.met.no under / | ||
| + | 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 |
| - | === 7) 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). | ||