Changes between Version 49 and Version 50 of Procedures/NewDataArrival


Ignore:
Timestamp:
Sep 16, 2008 1:07:36 PM (11 years ago)
Author:
mggr
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/NewDataArrival

    v49 v50  
    77== Mounting the SATA disk ==
    88To mount the SATA disk, put it into the computer. Then ssh onto the machine. Run `dmesg` to show information on the device names, the kind of thing we would be look for is:
    9 
     9{{{
    1010mptsas: ioc0: attaching sata device, channel 0, id 1, phy 1
    11 
    1211scsi 0:0:1:0: Direct-Access     ATA      ST3500630AS      E    PQ: 0 ANSI: 5
    13 
    1412sd 0:0:1:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
    15 
    1613sd 0:0:1:0: [sdb] Write Protect is off
    17 
    1814sd 0:0:1:0: [sdb] Mode Sense: 73 00 00 08
    19 
    2015sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    21 
    2216sd 0:0:1:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
    23 
    2417sd 0:0:1:0: [sdb] Write Protect is off
    25 
    2618sd 0:0:1:0: [sdb] Mode Sense: 73 00 00 08
    27 
    2819sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    29 
    3020sdb: sdb1
    31 
     21}}}
    3222where the name of the disk is sdb (sata disk b) and the partion is sdb1. SATA disks will be 500GB in size.  If paranoid and want to look at a time stamped version run
    3323 `sudo less /var/log/messages`.
     
    3626
    3727== Copying to PML data storage ==
    38 Copy to appropriate location on the filesystem (~arsf/arsf_data/in_progress/2007/flight_data/...)
    39   * when copying from the source media, preserve timestamps with `cp -a` or `rsync -av`
    40 === Scripting  method ===
     28=== Scripted method ===
    4129  * in the directory above the new project directories (eg '../flight_data/unpacking/') run 'unpack_folder_structure.py --dry-run'
    4230    * using --dry-run will output the commands it will run to the terminal. Check these look ok
     
    5644    * Run once for each sensor present
    5745    * The script should ignore blank lines on the logsheet and lines which are named test.
     46
    5847=== Non-scripting  method ===
     48Copy to appropriate location on the filesystem (~arsf/arsf_data/in_progress/2007/flight_data/...)
     49 * when copying from the source media, preserve timestamps with `cp -a` or `rsync -av`
    5950 * ensure the directory name conforms to the standard - '''PROJECTCODE-YYYY_JJJxx_SITENAME''', e.g. ''GB07_07-2007_102a_Inverclyde'', ''boresight-2007_198'', etc
    6051 * prune empty directories (check these aren't stubs for later data first) (use `rmdir *` in the project directory)
     
    7162   *`chmod go-w . -R`
    7263
    73 In some cases, the flight crew may fly two projects back-to-back but enter all the data onto a single logsheet.  If so, you may need to split the project directory into two, particularly if there's a large time gap (navigation needs separate processing) or the PIs are different (different delivery addresses/tracking).  If you do need to split a project, ensure both copies have copies of common files (logsheets, rinex, etc), but that non-common files are not duplicated (ie. don't include hawk data for part 1 in part 2..).  Also note in the ticket what was done for tracking purposes.
    74 
    7564== Verification ==
    7665
    7766Look at the logsheet and verify that we have copies of all relevant data mentioned there.
     67 * In some cases, the flight crew may fly two projects back-to-back but enter all the data onto a single logsheet.  If so, you may need to split the project directory into two, particularly if there's a large time gap (navigation needs separate processing) or the PIs are different (different delivery addresses/tracking).  If you do need to split a project, ensure both copies have copies of common files (logsheets, rinex, etc), but that non-common files are not duplicated (ie. don't include hawk data for part 1 in part 2..).  Also note in the ticket what was done for tracking purposes.
    7868
    7969Verify the details on the logsheet (esp. PI) are correct by cross-referencing against the ARSF application form.  If we do not have the application, call Kidlington to verify.