Version 10 (modified by mggr, 16 years ago) (diff)


NEODC Data Delivery

This page documents the procedure to follow when delivering data to NEODC.

First, we need to have some data to send - these should be datasets that are 'completed'.

Work in progress'''

  1. Prepare the relevant datasets:
    1. Make sure everything is where it should be! (see this wiki page? for the layout)
    2. Check everything is there (PDF logsheet, delivery directories, scripts, applanix/rinex data)
    3. Add a copy of the relevant trac ticket(s) - save these as html (including images) as arsf_trac_ticket_XXX.html and put in the admin/ subdir.
  2. Scan the filesystem for any 'bad' things and fix them:
    1. delete any unnecessary files - backups of DEMs that weren't used, temp files created by gedit (~ at end of filename), etc
    2. Remove executable bit on all files (except bin/az* and the run[aceh] scripts) -> find -type f -not -wholename '*bin/az*' -and -not -regex '.*/run[aceh]/.*sh' -and -perm /a=x -exec chmod a-x {} \;
    3. Find all files/dirs with unusual characters (space, brackets, etc) - use find -regex '.*[^-0-9a-zA-Z/._].*' | ~arsf/usr/bin/ to give suggested commands, but check first
    4. Give everyone read permissions (and execute if it has user execute) for the current directory and below - chmod -R a+rX .
  1. Write a README.txt that explains:
    1. The layout of the disk and what's on it
    2. Any additional information that'll help explain unusual files/dirs
  2. Create a filelist (find -ls > file_list.txt)
  1. Note on ticket that it's been archived/sent to neodc and close the ticket.