Changes between Version 106 and Version 107 of Procedures/NewDataArrival

Timestamp:

Jul 2, 2010, 12:56:38 PM (14 years ago)

Author:

benj

Comment:

--

Procedures/NewDataArrival

@@ -18 +18 @@
 
 == Move to permanent PML data storage ==
+
+Check there is space in the repository for the project (`du -hs ~arsf/arsf_data/YYYY/flight_data` and `du -hs location_of_project_to_unpack`). If not then skip this bit and copy to the workspace instead, but put a comment in the ticket so we can rsync it to the repository later.
 
 Move to appropriate location on the filesystem (~arsf/arsf_data/2009/flight_data/...)
@@ -73 +75 @@
 Check the filesizes of all data files (Eagle, Hawk, ATM, CASI) to make sure none are zero bytes (or obviously broken in some way).
 
+In the base of the project directory run `proj_tidy.sh .`. This will check that the directory structures look sensible and tell you where they don't. Correct anything significant that gets flagged up.
+
 == Create subsidiary files ==
 
@@ -79 +83 @@
 Create the calibration sym link. This is done automatically if the unpacking scripts have been run.
 
-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.
+(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.
 
 == Tickets and tracking ==