Changes between Version 74 and Version 75 of Procedures/NEODCDelivery

Timestamp:

Mar 1, 2012, 5:01:17 PM (13 years ago)

Author:

knpa

Comment:

--

Procedures/NEODCDelivery

@@ -3 +3 @@
 This page documents the procedure to follow when sending data to NEODC.
 
- 1. Choose a project. 
+ 1. Choose a project:
   - A project is ready to be archived when all sensors have been delivered. 
   - If it is 2010 or earlier then it will need to be fully r-synced from the workspace.
@@ -14 +14 @@
 }}}
      Check the output. Delete hidden/temporary/broken files. Fix incorrect file name formats and any other obvious errors. Everything in the delivery should be close to perfect, but don't worry too much about things in the main project.
-   1. Make sure that the main delivery data is present and the raw data is present. Run a quick eye over the rest of the file tree.
-   1. Remove unwanted large files. The project should have been cleaned up by the processor but often large files remain which are not needed. In particular, there are sometimes duplicates of data in processing/<sensor> which are included in delivery. Free up as much space as possible but deleting unwanted large files.
+   1. Make sure that the delivery sensor data is present and the raw data is present (incl. navigation). Run a quick eye over the rest of the deliveries.
+   1. Remove unwanted large files. The project should have been cleaned up by the processor but often large files remain which are not needed. In particular, there are sometimes duplicates of data in processing/<sensor> which are included in delivery. Free up as much space as possible by deleting unwanted large files.
    1. Add a copy of the relevant trac ticket(s) ; run:
 {{{
@@ -24 +24 @@
 }}}
    1. Set permissions:
-    1. Remove executable bit on all files (except the point cloud filter and the run[aceh] scripts): 
+    1. Remove executable bit on all files (except the point cloud filter and the run[aceh] scripts):[[BR]]
+       ** Note - if you are processing 2011 or later, you will need to run the below commands as both arsf and airborne **
 {{{
-find -type f -not -wholename '*pt_cloud_filter*' -and -not -regex '.*/run[aceh]/.*sh' -and -perm /a=x -exec chmod a-x {} \;
+find -type f -user `whoami` -not -wholename '*pt_cloud_filter*' -and -not -regex '.*/run[aceh]/.*sh' -and -perm /a=x -exec chmod a-x {} \;
 }}}
     1. Give everyone read permissions (and execute if it has user execute) for the current directory and below: 
 {{{
-chmod -R a+rX .
+find -user `whoami` -exec chmod a+rX {} \;
 }}}