Changes between Version 22 and Version 23 of Procedures/NewDataArrival
- Timestamp:
- May 19, 2008, 5:51:49 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Procedures/NewDataArrival
v22 v23 21 21 * remove group & other write permission, `chmod go-w . -R` 22 22 23 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. 23 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. 24 24 25 == Verification == 25 26 Look at the logsheet and verify that we have copies of all relevant data mentioned there. 26 27 27 Check the filesizes of all data files (Eagle, Hawk, ATM, CASI) to make sure none a er28 Check the filesizes of all data files (Eagle, Hawk, ATM, CASI) to make sure none are zero bytes (or obviously broken in some way). 28 29 29 30 == Tickets and tracking ==