Changes between Version 16 and Version 17 of Procedures/NewDataArrival/ProjectSetUp
- Timestamp:
- Sep 19, 2018, 11:13:48 AM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Procedures/NewDataArrival/ProjectSetUp
v16 v17 3 3 On this page you will find practical instructions about how to proceed in case new data comes to our facilities (via SATA disk or other method) in order to do the Project Set Up. 4 4 5 First of all, copy everything without modification of the creation times to the desired unpacking directory. That is to say, copy all to the unpacking dir in its corresponding year in the arsf_data directory. To do this you will need to be the '''arsf''' user and run the following command:5 First of all, copy everything without modification of the creation times to the desired unpacking directory. To do this rsync the data across as "arsf", for example: 6 6 {{{ 7 7 rsync -av –progress * ~arsf/arsf_data/2017/unpacking/ … … 83 83 Do your best once more and check carefully the output. If the starting time is still written on the hdr files the script should no find any problem ordering and renaming files. If not, the script will not allow you to continue. If no major problems then use {{{ --final}}} 84 84 85 All files and directories are now sorted and everything has been unpacked and we are almost done. You only need to run the final checks from the top project directory. You can also select to save the output in a logfile so use the same than in the previous stages if you want to do so. Again, you can use year, julian and sortie instead of config file (have a look at the help). As an example run: 85 All files and directories are now sorted and everything has been unpacked. You only need to run the final checks from the top project directory. 86 86 87 {{{ 87 run_unpacked_checks.py -p ‘project_path’ -y yyyy -j jjj -s s 88 run_unpacked_checks.py -p . -c ‘config_path.cfg’ -l ‘./admin/should_move_log_here.log’ 88 89 }}} 90 It is possible to manually specify the year and day rather than using a config file. 89 91 90 92 At this stage the project set up is done! Before leaving, do not forget to remove writing permissions. As '''arsf''' user, go to the top project directory and use: … … 93 95 }}} 94 96 97 This will give errors for the folders owned by "airborne" but this isn't anything to worry about. 98 95 99 There are still a few tasks that remains to consider the project fully unpacked and ready to start processing. You will need to go back in the wiki and follow the instructions for: generate a logsheet, tickets and tracking, KML overview and emailing the PI. 96 100