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 16:39:36] michaels |
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 | ||
| - | ==== SUBMISSION OF DATA PROCEDURE ==== | + | ====== SUBMISSION OF DATA PROCEDURE |
| - | Any submission of data to the AeroCom database requires to follow the following steps: | + | Any submission of data to the AeroCom database requires to follow the following steps: |
| + | - [[# | ||
| + | - [[# | ||
| + | - [[# | ||
| + | - [[# | ||
| + | - [[# | ||
| + | - [[# | ||
| + | - [[# | ||
| + | - [[#UPDATES|update errors]] on submission log on htap wiki page | ||
| - | << | ||
| - | === 1) FORMAT DATA === | + | ===== 1) format data ===== |
| - | Each variable should be stored in ONE cf-compliant | + | Each variable should be stored in ONE cf-compliant |
| - | 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, |
| - | Formatting can be achieved with cmor tools (http://www-pcmdi.llnl.gov/software-portal/cmor/) and nco tools (http://nco.sourceforge.net/ | + | See also frequently asked questions on CF: [[https://github.com/graybealski/ |
| - | An example file as used for the previous AeroCom experiment is found here: http:// | ||
| - | <<Anchor(ADJUST)>> | + | ===== 2) adjust filenames ===== |
| + | The obligatory filename for using the cf checker and the submission of data is:\\ | ||
| + | **aerocom3_<ModelName> | ||
| - | ==== 2) ADJUST FILENAMES ==== | + | Details about new file naming can be found here: |
| - | The obligatory Filename for using the cf checker and the submission of data is | + | [[https:// |
| - | " | + | 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 | ||
| - | <!ExperimentName> | + | OLD (aerocom phase3) |
| + | **aerocom3_< | ||
| - | <!VariableName> | + | OLD (aerocom phase 2) aerocom naming convention is also fine for now: |
| + | **aerocom_< | ||
| - | < | + | * < |
| + | * < | ||
| + | * < | ||
| + | * < | ||
| + | * < | ||
| + | * <VerticalCoordinateType> | ||
| + | * < | ||
| + | * < | ||
| - | < | ||
| - | < | + | ===== 3) check format ===== |
| + | Typical files must be checked prior to submission via a cf-compliance-checker. [[http:// | ||
| - | << | + | 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 | ||
| - | ==== 3) CHECK FORMAT ==== | + | Per default, a check shall comprise at least one file of each VerticalCoordinateType and each Frequency and each experiment, best varying |
| - | 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 ===== |
| - | ==== 4) OBTAIN ACCOUNT ON AeroCom SERVER ==== | + | ...for |
| - | 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 | + | |
| - | << | + | An account at Met.No is needed to submit data a data server |
| - | ==== 5) TRANSFER DATA TO MET.NO ==== | ||
| - | After obtaining an account, data can then be uploaded in two ways: | ||
| - | via ftp.aerocom.met.no: | + | ===== 5) transfer data ===== |
| + | After obtaining an account, data can then be uploaded to the aerocom | ||
| + | * Create a directory under / | ||
| + | * upload via ftp.aerocom.met.no has been discontinued due to security concerns. | ||
| + | |||
| - | via aerocom-users.met.no: make your directory under /media/scratch/incoming/ and put files there. Overall size limit of ca 500 GB ( limit for all users) | + | Large submissions (> 100 GB) may require extra attention (use rsync). They might require prior coordination with Met.No/Anna Benedictow/Jan Griesfeller/Michael Schulz via email, in particular in times of simultaneous heavy upload activity. |
| - | Very large submissions (> 10 GB) require prior coordination with Met.No/Jan Griesfeller& | + | On aerocom-users.met.no the directory |
| - | << | + | If correct in format and with correct file names, results uploaded here will be processed over night and appear after a day as image catalogue on http:// |
| - | ==== 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:scratch server. | + | ===== 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 | ||
| + | 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 / Error corrections | + | ===== 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). | ||
| - | << | + | |
| - | + | ||
| - | ==== 9) SUBMIT MODEL DESCRIPTION DOCUMENT ==== | + | |
| - | FOR EACH MODEL: | + | |