aerocom:data_submission

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
aerocom:data_submission [2019-04-23 11:06:22]
jang [3) CHECK FORMAT]
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.met.no/|aerocom.met.no]]FOR LATEST INFO
 +
 +
 AeroCom  data submission requirements AeroCom  data submission requirements
  
Line 16: Line 19:
 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. 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 excel htap protocol file for variable names, standard names (http://iek8wikis.iek.fz-juelich.de/HTAPWiki/WP2.2#A1._HTAP2_experiments_and_output_variables).+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: [[https://github.com/graybealski/cf-conventions-work/blob/master/FAQ.md|URL-link]] See also frequently asked questions on CF: [[https://github.com/graybealski/cf-conventions-work/blob/master/FAQ.md|URL-link]]
Line 63: Line 66:
  
  
-===== 4) OBTAIN ACCOUNT =====+===== 4) obtain account =====
  
 ...for METNO aerocom servers and WIKI documentation server  ...for METNO aerocom servers and WIKI documentation server 
  
-An account at Met.No is needed to submit data via ftp and edit [[aerocom:|AeroCom wiki pages]]. A data server (aerocom-users.met.no) allows users also to access the data via ssh. Please contact jan.griesfeller@met.no and/or anna.benedictow@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 and/or anna to activate the account.+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 and/or anna.benedictow@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 and/or anna to activate the account.
  
  
-===== 5) TRANSFER DATA =====+===== 5) transfer data =====
 After obtaining an account, data can then be uploaded to the aerocom user server aerocom-users.met.no: 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 6 TB (limit for all users)      * 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 6 TB (limit for all users)   
Line 76: Line 79:
      
  
-Large submissions (> 100 GB) may require extra attention (use rsync, scftp, not simple ftp clients). 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. +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. 
  
 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 MET.NO|notify metno]])) 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 MET.NO|notify metno]]))
Line 83: Line 86:
  
  
-===== 6) NOTIFY MET.NO ===== +===== 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 the ftp disk or 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>/.+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 /metno/aerocom-users-database/PROJECT(AEROCOM-PHASE-III)/<ModelName>_<exp>/.
  
-After the data are transferred to the database, data are removed from ftp server or aerocom-users:scratch server.+After the data are transferred to the database, data are removed from aerocom-users:scratch server.
  
  
-===== 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 modelers to record on the wiki information on known bugs, or any other relevant information needed for analysis of the model results by others.+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.
  
  
-===== 8) 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).
  
                
  • aerocom/data_submission.1556017582.txt.gz
  • Last modified: 2022-05-31 09:23:10
  • (external edit)