The ddx.sh script is meant to facilitate the uploading of heron and mokai
mission data. It is meant to cut time time to prepare and upload files, making
it hopefully faster to finish a day of experimenting by getting the data
off the vehicles and uploaded to oceanai quickly. The automation is also meant
to ensure data is properly labelled and organized. 

Assumptions:
===========================

(1) all vehicles are on the network, and able to connect to oceanai

(2) all log files are of the format vname_D_M_Y____H_M_S. 

This is the standard MOOS/pLogger directory format. The "vname" 
component is set by having "file=vname" in the pLogger config block.

Likely the pLogger config block is a plug file, and likely it should
be configured with "file=$VNAME" where $VNAME is filled in during the
launch. 

If this is not the case, and all vehicles have the default prefix of
"MOOSLog", then this prefix will need to be changed before running the 
script. 

Getting the ddx.sh script:
===========================

On any pablo, presumably with pablo-common-aro in ~/

$ cd pablo-common-aro
$ svn update

Confirm by typing "which ddx.sh


Running the ddx.sh script:
===========================
 
To run, begin by cd'ing into the mission folder:

$ cd moos-ivp-aquaticus/trunk/missions/aquaticus2.0
$ ddx.sh -t

The script takes a few command line switches (see ddx.sh --help)

The -t switch means only handle today's log files.
The -a switch will handle all log files in this directory.
Otherwise you can name one or more folders explicitly on the command line.

What the output should look like:
=================================

A typical output will have six parts:

(1) Confirming which folders are being handled. 
(2) Confirming which date folders are being created. 
(3) Confirming the creation of tar files for each folder
(4) Confirming connection to oceanai
(5) Confirming the creation of date folder(s) on oceanai
(6) Confirming the upload of tar files to oceanai

By example:

====================================================
Beginning MOOS log file archive script.  MIT (c)2018
====================================================
(1/6) Confirming Log Folders under consideration:
      alpha_3_8_2018_____12_00_39
      alpha_3_8_2018_____12_01_23
(2/6) Creating local dated-folders:
      2018_08_03 ... OK (prev) 
(3/6) Creating Tar files:
      2018_08_03/alpha_3_8_2018_____12_00_39.tgz ... OK (prev)
      2018_08_03/alpha_3_8_2018_____12_01_23.tgz ... OK (prev)
(4/6) Ensuring proper local ssh-key in place for rsync:
      Launching an ssh-agent if needed ... OK (prev) 
      Adding the student2680 ssh-key  ... OK 
(5/6) Creating dated-folders on remote target:
      2018_08_03 ... OK (prev) 
(6/6) Uploading / Rsyncing Tar files:
      2018_08_03/alpha_3_8_2018_____12_00_39.tgz ... OK 
      2018_08_03/alpha_3_8_2018_____12_01_23.tgz ... OK 

In each case of file/folder creation/upload, you will see either
"FAIL", "OK", or "OK (prev)". The latter simply means this step
was completed in a prior invocation of ddx.sh. 

** You should feel comfortable in running ddx.sh multiple times if you
like. It will only do the work that needs to be done, and should confirm
in subsequent runs that all is ok. 


Files on Oceanai:
========================

Successful uploads should land on oceanai at:

/lacie/aquaticus_data
  2018_08_03/
    2018_08_03/robot1_3_8_2018_____12_00_39.tgz
    2018_08_03/robot2_3_8_2018_____12_02_19.tgz
    2018_08_03/robot3_3_8_2018_____12_05_33.tgz
    2018_08_03/robot4_3_8_2018_____12_01_32.tgz

    2018_08_03/mokai1_3_8_2018_____12_02_38.tgz
    2018_08_03/mokai2_3_8_2018_____12_00_49.tgz
    2018_08_03/mokai3_3_8_2018_____12_01_29.tgz
    2018_08_03/mokai4_3_8_2018_____12_00_37.tgz

(Likely multiple tar files per vehicle)