Changes between Version 73 and Version 74 of Procedures/NEODCDelivery


Ignore:
Timestamp:
Mar 1, 2012 4:16:05 PM (7 years ago)
Author:
knpa
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Procedures/NEODCDelivery

    v73 v74  
    33This page documents the procedure to follow when sending data to NEODC.
    44
    5 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. Also, check the ticket and make sure there is nothing on there which suggests something still needs to be done with the dataset (ask the processor if need be).
    6 [[BR]]
     5 1. Choose a project.
     6  - A project is ready to be archived when all sensors have been delivered.
     7  - If it is 2010 or earlier then it will need to be fully r-synced from the workspace.
     8  - Check the ticket and make sure there is nothing on there which suggests something still needs to be done with the dataset (ask the processor if need be).
    79 1. If there is a workspace version, move it into workspace/being_archived
    8  1. Prepare the repository version for archiving:
    9    1. Make sure everything is present and where it should be! (see [wiki:Processing/FilenameConventions] for the required layout and name formats) [[BR]]
    10       Things to look out for: '''Delivery folders, applanix/rinex data, las files, DEMs''' [[BR]]
    11       Use proj_tidy.sh to highlight any problems:
     10 1. Prepare the repository version for archiving:
     11   1. Run proj_tidy.sh to highlight any problems:
    1212{{{
    1313proj_tidy.sh -p <project directory> -c
    1414}}}
     15     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.
     16   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.
     17   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.
    1518   1. Add a copy of the relevant trac ticket(s) ; run:
    1619{{{
     
    2023popd
    2124}}}
    22    1. Scan the filesystem for any 'bad' things and fix them:
    23     1. Delete any unnecessary files - backups of DEMs that weren't used, temp files created by gedit (~ at end of filename), hidden files, duplicates in lev1 dir etc
    24     1. Find all files/dirs with unusual characters (space, brackets, etc), ignoring the admin/trac_ticket folder:
    25 {{{
    26 find -regex '.*[^-0-9a-zA-Z/._].*'  -o -path './admin/trac_ticket' -prune | ~arsf/usr/bin/fix_naughty_chars.py
    27 }}}
    28        This will give suggested commands, but check first.
    2925   1. Set permissions:
    3026    1. Remove executable bit on all files (except the point cloud filter and the run[aceh] scripts):
     
    3632chmod -R a+rX .
    3733}}}
     34
    3835 1. Create the tarballs for NEODC to download:[[BR]][[BR]]
    3936   ''If AIMMS or GRIMM data is present then you will first need to separate these and put into separate tarballs. [[BR]]