Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
aerocom:data_submission [2013-12-12 17:06:09] michaels |
aerocom:data_submission [2021-04-16 07:55:11] annac [4) obtain account] |
||
---|---|---|---|
Line 1: | Line 1: | ||
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: |
+ | - [[#FORMAT DATA|format data]] to agreed netCDF htap standards, cf compliant | ||
+ | - [[#ADJUST FILENAMES |adjust filenames]] | ||
+ | - [[#CHECK FORMAT|check format]] with cf compliance checker, correct and check again | ||
+ | - [[#OBTAIN ACCOUNT|obtain account]] on htap server to access aerocom-users server | ||
+ | - [[#TRANSFER DATA|transfer data]] to the aerocom-users.met.no | ||
+ | - [[#NOTIFY MET.NO|notify metno]] that data have been submitted | ||
+ | - [[#LOG FILE SUBMISSION|log submission]] in [[aerocom: | ||
+ | - [[# | ||
- | === 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:// | ||
+ | ===== 2) adjust filenames ===== | ||
+ | The obligatory filename for using the cf checker and the submission of data is:\\ | ||
+ | **aerocom3_< | ||
+ | Details about new file naming can be found here: | ||
+ | [[https:// | ||
- | === 2) ADJUST FILENAMES === | + | Be aware of updates ! \\ |
- | The obligatory Filename for using the cf checker and the submission | + | |
- | " | + | versions will have a date attached.\\ |
- | OLD aerocom naming convention is also fine for now: | + | 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_< | ||
- | <!ModelName> | + | OLD (aerocom phase 2) aerocom naming convention is also fine for now: |
+ | **aerocom_< | ||
- | < | + | * < |
+ | * < | ||
+ | * <ExperimentName> | ||
+ | * < | ||
+ | * < | ||
+ | * < | ||
+ | * < | ||
+ | * < | ||
- | < | ||
- | < | + | ===== 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 | ||
- | <Frequency> => " | + | Per default, a check shall comprise at least one file of each VerticalCoordinateType and each Frequency |
- | << | ||
- | === 3) CHECK FORMAT | + | ===== 4) obtain account ===== |
- | 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 | + | ...for METNO aerocom servers and WIKI documentation server |
- | [[http:// | + | |
- | Typical files? A check shall comprise | + | An account |
- | === 4) OBTAIN ACCOUNT | + | ===== 5) transfer data ===== |
- | An account | + | After obtaining an account, data can then be uploaded to the aerocom user server aerocom-users.met.no: |
+ | * Create a directory under / | ||
+ | * upload | ||
+ | | ||
+ | Large submissions (> 100 GB) may require extra attention (use rsync). They might require prior coordination with Met.No/Anna Benedictow/ | ||
- | === 5) TRANSFER DATA === | + | On aerocom-users.met.no the directory / |
- | After obtaining an account, | + | |
- | via ftp.aerocom.met.no: make your directory under /incoming/ and put files there. Overall size limit of ca 500 GB ( limit for all users) | + | 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://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 anna.benedictow@met.no and jan.griesfeller@met.no | |
- | + | ||
- | + | ||
- | === 6) NOTIFY MET.NO === | + | |
- | When files are uploaded send email to jan.griesfeller@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 ftp server or aerocom-users: | ||
+ | ===== 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 modellers to record on the wiki information on known bugs, or any other relevant information needed for analysis of the model results by others. | ||
- | === 7) LOG FILE SUBMISSION | + | ===== 8) updates ===== |
- | 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 | + | |
- | + | ||
- | + | ||
- | === 7) 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). | ||