Summary of Buoy Setup, Testing, Recoveries and Deployments

Buoy Setup:

1. Make sure that mooring_plan, config_mooring, config_buoy, config_cable and umecb_pre entries have been made for the new buoy.

2. Use monitor.php 'Test' function to set up entries in gomoos_processing.mooring and gomoos_control.mooring.

Buoy Testing:

1. Make main buoy (/data/gomoos/buoy/archive/Axxxx) and subdirectories (sensor-raw, realtime, goes-sensor-raw, goes-realtime, daily (for optics).

2. In Matlab, cd to main buoy direction (/data/gomoos/buoy/archive/Axxxx) and run write_script('Axxxx'). This generates script.sed file needed to edit .cdl files.

3. Run /data/gomoos/buoy/bin/make_cdlfiles.sh Ayyyy sensor-raw (Ayyyy is a previous deployment with appropriate .nc files). This copies all .cdl template files to sensor-raw. Repeat for realtime, goes-sensor-raw, goes-realtime, and daily (if needed).

4. From main buoy directory, runsed */*.cld (this runs script.sed on all .cdl files).

5. Move down to sensor-raw. Run

   /data/gomoos/buoy/bin/make_ncfiles.sh Axxxx

   If there are errors, edit the .cdl file and make corrections. Generate individual files by

   ncgen -o Axxxx.met.sensor-raw.nc met.sensor-raw.cdl

   Repeat for all sub-directories (realtime, goes-sensor-raw, goes-realtime, daily). Either delete or move the .cdl files to a subdirectory.

6. In Matlab,

   options=get_options('Axxxx'); init_deployment (options,'archive/Axxxx')

   If there are errors, you need to correct and try again. This will go through each .nc file and populate gomoos_processing.processing_files and gomoos_processing.processing_datatypes mySQL tables.

7. Edit /data/gomoos/buoy/matlab/buoy-mfiles/core_processing/mretrieve_goes_buffer.m if necessary.

8. Add link in /data/gomoos/buoy/incoming

   ln -s cellphone/DATA/Axxxx.DAT Axxxx.dat

9. Check crontab for goes and cellphone processing of Axxxx.

Buoy Recovery.

1. Edit crontab file to comment out both goes and cellphone processing.

2. 'Recover' the buoy in monitor.php (update all mySQL tables).

3. Add realtime files to history files

   /data/gomoos/buoy/bin/ncradd_history.sh Axxxx realtime

   Doppler files have to be manually added. In matlab,

   dop=nc_getbuffer('Axxxx.doppler.realtime.nc')

   nc_archive_buffer(dop,'/data/gomoos/buoy/archive/A01/A01.doppler.historical.nc');

4. Send email to buoy, portland and optics (if optics buoy).

Buoy Deployment.

1. Check to make sure that data is good for all buffers.

2. 'Deploy' the buoy in monitor.php

3. Cut out any pre-deployment data from .nc files so bad data doesn't go to GoMoos:

   cd /data/gomoos/buoy/archive/Axxxx; /data/gomoos/buoy/bin/ncrcut_deploy.sh jd1 jd2 Axxxx

   (where jd1 is julian date of first good sample after anchor drop, jd2 is current time + an hour or two. In matlab, use julian([yyyy mm dd hh mm ss]) to get values for jd1, jd2.)

4. Check .nc files to make sure they are correct (load into matlab with

   met=get_ncfile('Axxxx.met.realtime.nc'); met.wind_speed.data

   or from command prompt:

   ncdump Axxxx.met.realtime.nc |more

5. Check that the incoming directory files have been zeroed (cb)

   /data/gomoos/buoy/incoming/cellphone/DATA/xxxxx.DAT

   or

   /data/gomoos/buoy/incoming/irridium/xxxxx.DAT

   If they have not, there was a processing error which needs to be corrected (check for mail msgs).

6. Check rollover map and buoy.php pages to make sure that the new data are displayed.

7. Check position in diagnostics buffer. In matlab, use adjust_latlon.m to update positions in all files. Adjust_latlon will also update the mySQL gomoos_processing.mooring and gomoos_control.mooring tables for the correct positions.

8. /data/gomoos/buoy/bin/rsync_buoy.sh Axxxx (makes sure GoMoos gets cleaned up files)

9. Send email to buoy, portland (and optics if buoy has optics).