Changes between Version 49 and Version 50 of Procedures/NewDataArrival
- Timestamp:
- Sep 16, 2008, 1:07:36 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Procedures/NewDataArrival
v49 v50 7 7 == Mounting the SATA disk == 8 8 To 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 {{{ 10 10 mptsas: ioc0: attaching sata device, channel 0, id 1, phy 1 11 12 11 scsi 0:0:1:0: Direct-Access ATA ST3500630AS E PQ: 0 ANSI: 5 13 14 12 sd 0:0:1:0: [sdb] 976773168 512-byte hardware sectors (500108 MB) 15 16 13 sd 0:0:1:0: [sdb] Write Protect is off 17 18 14 sd 0:0:1:0: [sdb] Mode Sense: 73 00 00 08 19 20 15 sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA 21 22 16 sd 0:0:1:0: [sdb] 976773168 512-byte hardware sectors (500108 MB) 23 24 17 sd 0:0:1:0: [sdb] Write Protect is off 25 26 18 sd 0:0:1:0: [sdb] Mode Sense: 73 00 00 08 27 28 19 sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA 29 30 20 sdb: sdb1 31 21 }}} 32 22 where 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 33 23 `sudo less /var/log/messages`. … … 36 26 37 27 == 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 === 41 29 * in the directory above the new project directories (eg '../flight_data/unpacking/') run 'unpack_folder_structure.py --dry-run' 42 30 * using --dry-run will output the commands it will run to the terminal. Check these look ok … … 56 44 * Run once for each sensor present 57 45 * The script should ignore blank lines on the logsheet and lines which are named test. 46 58 47 === Non-scripting method === 48 Copy 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` 59 50 * ensure the directory name conforms to the standard - '''PROJECTCODE-YYYY_JJJxx_SITENAME''', e.g. ''GB07_07-2007_102a_Inverclyde'', ''boresight-2007_198'', etc 60 51 * prune empty directories (check these aren't stubs for later data first) (use `rmdir *` in the project directory) … … 71 62 *`chmod go-w . -R` 72 63 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 75 64 == Verification == 76 65 77 66 Look 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. 78 68 79 69 Verify 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.