Changes between Version 4 and Version 5 of Procedures/NewDataArrival/ProjectSetUp

Timestamp:

Feb 3, 2017, 12:03:07 PM (8 years ago)

Author:

asm

Comment:

--

Procedures/NewDataArrival/ProjectSetUp

@@ -8 +8 @@
 }}}
 
-If you do not know how to access the data in order to copy to that directory, please visit:
+If you do not know how to access the data in order to do the copy, please visit:
  * [wiki:Procedures/NewDataArrival/Disk Data by SATA disk or DVD]
  * [wiki:Procedures/NewDataArrival/Network Data by network transfer]
@@ -60 +60 @@
 fenix_rename.py –config_path ‘config_path.cfg’ –path .
 }}}
-If at anytime you prefer to write year, julian and sortie you might do so instead of using the config file. Using the config file is recommended for simplicity. '''Check carefully the output'''. Come on, this is important now so pay attention and check carefully the output. Once done, you can use –final. I suggest you use as the log file the file created from unpack_project.py so we have all the information in the same file that should later be placed into project/admin directory.  Use:
+If at anytime you prefer to write year, julian and sortie you might do so instead of using the config file. Using the config file is recommended for simplicity. The script will check that the files have the correct julian day, year and will look for missing files (the same will be done later for the Owl sensor). '''Pay close attention and check carefully the output'''. Once done, you can use –final. I suggest you use as the log file the file created from unpack_project.py so we have all the information in the same file that should later be placed into project/admin directory.  Use:
 {{{
 fenix_rename.py  -c ‘config_path.cfg’  -p . -l ‘./admin/should_move_log_here.log’ --final
 }}}
-And there it is, everything sorted for the Fenix.
+Everything is sorted for the Fenix sensor.
 
 Let’s move to the Owl. The steps are almost the same. You can run from top project directory: