Changes between Version 2 and Version 3 of Procedures/NewDataArrival


Ignore:
Timestamp:
Jun 28, 2007 12:13:05 PM (12 years ago)
Author:
mggr
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/NewDataArrival

    v2 v3  
    33This procedure should be followed on receipt of new flight data from ARSF.
    44
    5 1. copy to appropriate location on the filesystem (~arsf/arsf_data/2007/flight_data/...)
    6   1. ensure the directory name conforms to the standard - PROJECTCODE-YYYY_JJJxx, e.g. ''GB2007_05-2007_116b'', ''boresight-2007_198'', etc
    7   1. rename any capitalised subdirectories
    8   1. prune empty directories? (''need to think about this, maybe only do after checking it's not a stub for later data'')
    9 1. raise a trac ticket (type 'flight processing') for the new data
     5 1. copy to appropriate location on the filesystem (~arsf/arsf_data/2007/flight_data/...)
     6   * ensure the directory name conforms to the standard - PROJECTCODE-YYYY_JJJxx, e.g. ''GB2007_05-2007_116b'', ''boresight-2007_198'', etc
     7   * rename any capitalised subdirectories
     8   * prune empty directories? (''need to think about this, maybe only do after checking it's not a stub for later data'')
     9 1. raise a trac ticket (type 'flight processing') for the new data
    1010
    1111= Other data types =