| 4 | | 1. ensure permissions on the SATA disk are correct and all files readable ("chmod a+rX /mnt/satadisk" as root) |
| 5 | | 1. copy to appropriate location on the filesystem (~arsf/arsf_data/in_progress/2007/flight_data/...) |
| 6 | | * ensure the directory name conforms to the standard - '''PROJECTCODE-YYYY_JJJxx_SITENAME''', e.g. ''GB2007_07-2007_102a_Inverclyde'', ''boresight-2007_198'', etc |
| 7 | | * rename any capitalised subdirectories |
| 8 | | * remove any spaces, brackets or other Unix-upsetting characters in filenames |
| 9 | | * move DCALM* files to applanix/Raw |
| 10 | | * prune empty directories? (''need to think about this, maybe only do after checking it's not a stub for later data'') |
| 11 | | * ''need to ensure backups are taken'' |
| 12 | | 1. look at the logsheet and verify that we have copies of all relevant data mentioned there |
| 13 | | 1. raise a trac ticket (type 'flight processing') for the new data |
| 14 | | * ticket summary should be of the form '''BGS2007/02, flight day 172/2007, Keyworth''' |
| 15 | | * ticket body should contain: |
| | 4 | |
| | 5 | If in any doubt about something (e.g. a dataset has two project codes), contact Gary. |
| | 6 | |
| | 7 | == Permissions fixing == |
| | 8 | Ensure permissions on the SATA disk are correct and all files readable ("chmod a+rX /mnt/satadisk" as root) |
| | 9 | |
| | 10 | == Copying to PML data storage == |
| | 11 | Copy to appropriate location on the filesystem (~arsf/arsf_data/in_progress/2007/flight_data/...) |
| | 12 | * ensure the directory name conforms to the standard - '''PROJECTCODE-YYYY_JJJxx_SITENAME''', e.g. ''GB2007_07-2007_102a_Inverclyde'', ''boresight-2007_198'', etc |
| | 13 | * rename any capitalised subdirectories |
| | 14 | * remove any spaces, brackets or other Unix-upsetting characters in filenames |
| | 15 | * move DCALM* files to applanix/Raw |
| | 16 | * prune empty directories (check these aren't stubs for later data first) |
| | 17 | |
| | 18 | == Verification == |
| | 19 | Look at the logsheet and verify that we have copies of all relevant data mentioned there. |
| | 20 | |
| | 21 | == Tickets and tracking == |
| | 22 | Raise a trac ticket (type 'flight processing') for the new data, then add details to the processing status page. |
| | 23 | * ticket summary should be of the form '''BGS2007/02, flight day 172/2007, Keyworth''' |
| | 24 | * add scientific summary (check ARSF application in ~arsf/arsf_data/in_progress/2007/ARSF_Applications-GB_2007) |
| | 25 | * note arrival time of data |
| | 26 | * note any specific comments that might help with processing |
| | 27 | * ticket body should contain: |