Changes between Version 127 and Version 128 of Procedures/NewDataArrival


Ignore:
Timestamp:
Oct 1, 2010 12:28:14 PM (9 years ago)
Author:
knpa
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/NewDataArrival

    v127 v128  
    4141   * `ooffice -invisible  "macro:///Standard.Module1.SaveAsPDF(FULL_PATH_TO_FILE)"`
    4242
    43 == Verification ==
     43= Verification =
    4444
    45 = Unpack File Check =
     45== Unpack File Check ==
    4646
    4747In each project directory run 'unpack_file_check.py -l <admin/logsheet.doc(.txt)>'
     
    5555    * Check for nav-sync issues - THIS IS BASED ON A FALSE ASSUMPTION AND PROBABLY IS USELESS
    5656
    57 = proj_tidy.sh  =
     57== proj_tidy.sh  ==
    5858
    5959In the base of the project directory run proj_tidy:[[BR]]
     
    6161This will check that the directory structures look sensible and tell you where they don't. Correct anything significant that gets flagged up.
    6262
    63 = Final manual checks =
     63== Final manual checks ==
    6464
    6565Look at the logsheet and verify that we have copies of all relevant data mentioned there.
     
    7070Check the filesizes of all data files (Eagle, Hawk, ATM, CASI) to make sure none are zero bytes (or obviously broken in some way).
    7171
    72 == Move to permanent PML data storage ==
     72= Move to permanent PML data storage =
    7373
    74741. Move to appropriate location in the repository (~arsf/arsf_data/2009/flight_data/...)
     
    8686   * This will generate a qsub command script for use to submit processing of all eagle, hawk, atm and casi flight lines to the grid nodes.
    8787
    88 == Create subsidiary files ==
     88= Create subsidiary files =
    8989
    9090Run the DEM generating script if a UK flight. `nextmapdem.sh`
     
    9696(Not necessary any more) Run times4grafnav.py script to create a text file of time stamps and put the output into the applanix directory. May be of use for the GNSS processing.
    9797
    98 == Tickets and tracking ==
     98= Tickets and tracking =
    9999Raise a [http://arsf-dan.nerc.ac.uk/trac/newticket new trac ticket] (type 'flight processing') for the new data.
    100100 * Ticket summary should be of the form '''BGS07/02, flight day 172/2007, Keyworth'''
     
    118118Any other notes..
    119119
    120 == Sensors: ==
     120= Sensors: =
    121121 * Eagle
    122122 * Hawk
     
    127127When done, add details to the [http://www.npm.ac.uk/rsg/projects/arsf/status/addflight/addflight.php processing status page] and to the [wiki:Status/Order processing order page].
    128128
    129 == Vectors ==
     129= Vectors =
    130130
    131131If the site is in the UK, check the [wiki:Internal/Vector_Requests requested OS vectors wiki page] to see if we have vectors for the site in question. If not then email ARSF-Ops (Gary) and ask for them, specifying the 4 corner points of the area covered, in OS BNG grid coordinates (use the generated nextmap DEM to get the range of tiles, then do the conversion). This can take a couple of weeks before we get the vectors.
    132132
    133 == Finally.. ==
     133= Finally.. =
    134134
    135135Email the PI to inform them that their data has arrived for processing.  Sample text: