Changes between Version 147 and Version 148 of Procedures/NewDataArrival

Timestamp:

May 26, 2011, 3:51:10 PM (14 years ago)

Author:

knpa

Comment:

--

Procedures/NewDataArrival

@@ -21 +21 @@
 The next stage can be manual or semi-automated. Even if the script works, go through and check it has correctly done each of the manual steps.
 
-=== Semi-scripted method ===
-  * In the directory above the new project directories (eg '.../flight_data/unpacking/') run 'unpack_folder_structure.py' [[BR]] NOTE: If you want to just run this on just one project (and as we usually only unpack one at a time) then you will need to move this project into a temporary containing folder when running this script (will change script at some point so can specify a single project).
-    * By default, it runs safely in a dry-run mode and will output the commands it will run to the terminal. Check these look ok.
-    * If happy, either re-run with --execute (and optionally --verbose)
-    * Each project directory should be re-formatted to the current standard
+=== Script ===
+* Run unpack_convert_proj.sh in the target project directory. This will change the project from the old-syle to the new whilst correcting a few errors.
 
-=== Non-scripting  method ===
+=== Other steps ===
  * Prune empty directories (check these aren't stubs for later data first) (use `rmdir *` in the project directory)
  * Rename any capitalised subdirectories
- * Move DCALM* files to applanix/raw
  * Remove any spaces, brackets or other Unix-upsetting characters in filenames
    * use `find -regex '.*[^-0-9a-zA-Z/._].*' | ~arsf/usr/bin/fix_naughty_chars.py`
@@ -40 +36 @@
  * Convert the .doc logsheet to .pdf
    * `ooffice -invisible  "macro:///Standard.Module1.SaveAsPDF(FULL_PATH_TO_FILE)"`
- * Rename 'rinex' to 'basestation' in top directory (if present). Move all basestation data to here, then create a symlink to it from inside both applanix and leica/ipas.
 
 = Verification =
@@ -46 +41 @@
 == Unpack file check ==
 
-In each project directory run 'unpack_file_check.py -l <admin/logsheet.doc(.txt)>'
-  * This will convert .doc logsheet to .txt, or use the .txt if one available. NOTE to convert to .doc requires ooffice macro
-  * Will then do various checks of data against logsheet as listed below. Information will be output to terminal. Important (error) messages are printed again at the end. 
-    * Check file sizes against a 'suitable' size and also against header file (Eagle + Hawk)
-    * Check number of files against logsheet
-    * Check number of logsheets
-    * Check GPS start/stop times in header file (Eagle + Hawk)
-    * Check .raw, .nav, .log, .hdr for each Eagle + Hawk line
-    * Check for nav-sync issues - THIS IS BASED ON A FALSE ASSUMPTION AND PROBABLY IS USELESS
+knpa: This will need to be rewritten to work with the new file structure.
 
 == proj_tidy.sh  ==
 
-In the base of the project directory run proj_tidy:[[BR]]
-`proj_tidy.sh -p ./ -e`[[BR]]
-This will check that the directory structures look sensible and tell you where they don't. Correct anything significant that gets flagged up.
+knpa: ditto!
 
 == Final manual checks ==
@@ -67 +52 @@
  * 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.
 
-Verify the details on the logsheet (esp. PI) by calling/emailing ARSF-Ops (probably Gary) - the application form and logsheet are not reliable enough, nor do they track any changes in PI over the lifetime of the application.
+Verify the details on the logsheet (esp. PI) by calling/emailing ARSF-Ops (probably Gary) - the application form and logsheet are not reliable enough, nor do they track any changes in PI over the lifetime of the application. Get the alpha grading as well.
 
 Check the filesizes of all data files (Eagle, Hawk, ATM, CASI) to make sure none are zero bytes (or obviously broken in some way).
 
-= Move to permanent PML data storage =
-
-Move to appropriate location in the repository (~arsf/arsf_data/2009/flight_data/...)
-  * ensure the project directory names conform to the standard - '''PROJECTCODE-YYYY_JJJxx_SITENAME''', e.g. ''GB07_07-2007_102a_Inverclyde'', ''boresight-2007_198'', etc
-
-= Create subsidiary files =
-
-Run the DEM generating script if a UK flight. `nextmapdem.sh`
-
-If the flight is outside the UK you'll need to process the LiDAR data first or use the ASTER/SRTM dem (see http://arsf-dan.nerc.ac.uk/trac/wiki/Processing/SRTMDEMs) 
-
-Create the calibration sym link. This is done automatically if the unpacking scripts have been run.
 
 = Tickets and tracking =
@@ -160 +133 @@
 
 }}}
+
+= Move to permanent PML data storage =
+
+Move to appropriate location in the repository (~arsf/arsf_data/2009/flight_data/...)
+  * ensure the project directory names conform to the standard - '''PROJECTCODE-YYYY_JJJxx_SITENAME''', e.g. ''GB07_07-2007_102a_Inverclyde'', ''boresight-2007_198'', etc
+
+= Create subsidiary files =
+
+Run the DEM generating script if a UK flight. `nextmapdem.sh`
+
+If the flight is outside the UK you'll need to process the LiDAR data first or use the ASTER/SRTM dem (see http://arsf-dan.nerc.ac.uk/trac/wiki/Processing/SRTMDEMs) 
+
+Create the calibration sym link. This is done automatically if the unpacking scripts have been run.