Context Navigation

Changes between Version 193 and Version 194 of Procedures/NewDataArrival

v193	v194
15	15	* Look at the logsheet included and verify that we have copies of all relevant data mentioned there.
16	16	* 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 write in the ticket any changes made for tracking purposes.
17		* Verify ~~the details on the logsheet (esp. PI) by calling/emailing NERC-ARF Ops~~ - the application form and logsheet are not sufficient proof, nor do they track any changes in PI over the lifetime of the application.
	17	* Verify all details on the logsheet (esp. PI) by calling/emailing NERC-ARF Ops making them aware of the projects that have been unpacked - the application form and logsheet are not sufficient proof, nor do they track any changes in PI over the lifetime of the application.
18	18
19	19	Make a logsheet that is suitable for delivery to end users. Use the {{{generateLogsheet.py}}} script and follow instructions from: