Submission of Data Procedure
Any submission of data to the AeroCom database requires to follow the following steps:
format data to agreed netCDF htap standards, cf compliant
check format with cf compliance checker, correct and check again
obtain account on htap server to access aerocom-users server
transfer data to the aerocom-users.met.no at the Norwegian Meteorological Institute
notify metno that data have been submitted
update errors on submission log on htap wiki page
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, units and origin of the data.
See also frequently asked questions on CF: URL-link
2) adjust filenames
The obligatory filename for using the cf checker and the submission of data is:
Details about new file naming can be found here: AeroCom experiments diagnostics sheets 28.2.2019
Be aware of updates !
versions will have a date attached.
OLD (aerocom phase3) aerocom3_<ModelName>_<ExperimentName>_<VariableName>_<VerticalCoordinateType>_<Period>_<Frequency>.nc
OLD (aerocom phase 2) aerocom naming convention is also fine for now: aerocom_<ModelName>_<ExperimentName>_<VariableName>_<Period>_<Frequency>.nc
<ModelName> ⇒ can be chosen such that Model Name, Model version and possibly the institution can be identified. No underscores (_) are allowed in <!ModelName>, use (-) instead. Restrict <ModelName> to max 20 characters.
<MeteoConfigSpecifiers> ⇒ “met2010” (default, nudged to 2010 meteo) / “fSST” (fixed 2010 SST monthly fields, not nudged) / “CPL” (coupled AOGCM model, not nudged) A MeteoSpecifier has to be present
<ExperimentName> ⇒ see Experiment Specifications
<PerturbationName> see experiment descriptions on aerocom wiki, if required for the experiment, use exact case sensitive name from description
<VariableName> ⇒ see output variable names in excel sheet
<VerticalCoordinateType> ⇒ “Surface”, “Column”, “ModelLevel”, “SurfaceAtStations”, “ModelLevelAtStations”
<Period> ⇒ eg “2008”, “2010”
<Frequency> ⇒ “timeinvariant”,“hourly”, “3hourly”, “daily”, “monthly”, “sat1000”, “sat1330”, “sat2200”, “sat0130”
3) check format
Typical files must be checked prior to submission via a cf-compliance-checker. cfconventions.org maintains a list of working and frequently updated CF checkers. Some come as a script, and to others one can upload a file.
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
…for METNO aerocom servers and WIKI documentation server
An account at Met.No is needed to submit data and edit AeroCom wiki pages. A data server (aerocom-users.met.no) allows users also to access the data via ssh. Please contact firstname.lastname@example.org and/or email@example.com for password and user name. You will then be notified further about the procedure. A public ssh-key has to be sent to jan and/or anna to activate the account.
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/scratch/incoming/AEROCOM_AUTO_UPLOAD/<ModelName>/renamed/
Use exactly the same model name as used for file names. Attention to lower&upper case!!
Put files in that renamed directory. Overall size limit of ca 10 TB (limit for all users)
Large submissions (> 500 GB) may require extra attention (use rsync, sftp). 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.
On aerocom-users.met.no the directory /media/scratch/incoming/AEROCOM-P3-AUTO-UPLOAD allows for automatic incorporation into the AeroCom database and workup. Uploaded files are processed automatically by the AeroCom tools and transfered into the AeroCom phase III data directory. (Still in test phase - send also e-mail (ref. notify metno))
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 https://aerocom-classic.met.no/cgi-bin/aerocom/surfobs_annualrs.pl?PROJECT=AEROCOM&MODELLIST=AEROCOM-Phase-III
6) notify met.no
When files are uploaded send email to firstname.lastname@example.org and email@example.com and firstname.lastname@example.org (AND coordinator of project), so that the files can be transferred from aerocom-users to the database. When the data are included in the database the files appear on aerocom-users.met.no under /metno/aerocom-users-database/PROJECT(AEROCOM-PHASE-III)/<ModelName>_<exp>/.
After the data has been transferred to the database, it will be deleted form the aerocom-users' scratch area.
7) submit a log file
FOR EACH SUBMISSION: Put an entry into the htap wiki page 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.
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).