Coastal Ocean Observation Labhttp://marine.rutgers.edu/cool

Coastal Observation and Prediction Sponsors:

Regional Ocean Prediction http://marine.rutgers.edu/po

Education & Outreachhttp://coolclassroom.org

RIMPAC 2008: Rutgers Glider MCM Operational

SupportPartners: ONR, Metron, WetLabs, and NAVO

Rutgers University(Largely support)

• Provided 3-100m Slocum Coastal Electric Gliders to NAVOCEANO

• On-site logistical support in case of emergency recoveries/redeployments

• Off-site support for NAVOCEANO (glider configurations, science payload sampling, etc.)

• QA/QC and dissemination of Inherent Optical Properties (IOPs):

– bb(λ): Optical backscatter (470, 532, 660nm)

– c(λ): : Optical attenuation (532nm)

• NAVOCEANO took the lead on Slocum glider field operations

The Slocum Coastal Electric Glider

Glider Specs.Length: 1.5 mHull Diameter: 21.3 cmWeight: 52 kg

Science Bay Specs.Length: 30 cmDiameter: 21.3 cmMax. Payload Weight: 4 kg

Science Payload Sensors(Modular, Swapable)

• CTD – hydrography (Temperature, Salinity, Density)• Optical Sensors –

– Eco bb3 pucks (blue, green and red light backscattering)– AUVB (green light attenuation)

Tactical Decision Aids

Traditional Glider Piloting/Visualization Software and Data Flow

Tactical Decision Aids

RIMPAC 2008 Glider Piloting/Visualization Software and Data Flow

Glider MCM Operations Summary:Penguin Banks (5 Deployments)

sl113 (NAVOCEANO): 6/28/2008 – 7/26/2008sl114 (NAVOCEANO): 6/28/2008 – 7/26/2008

ru05 (Rutgers): 7/07/2008 – 7/12/2008ru05 (Rutgers): 7/18/2008 – 7/26/2008ru16 (Rutgers): 7/03/2008 – 7/24/2008

Deployment Totals:5 deployments

90 in-water glider days1533km flown

> 10,000 profilesRU05: July 7, 2008 – July 12, 2008

Payload: CTD, OCR-504I, Eco bb puckDuration: 5 daysDistance Traveled: 112kmProfiles: 1150

RU05: July 18, 2008 – July 26, 2008Payload: CTD, OCR-504I, Eco bb puckDuration: 8 daysDistance Traveled: 131kmProfiles: 482

RU16: July 3, 2008 – July 24, 2008Payload: CTD, AUVB, Eco bb puck, Eco fl puckDuration: 21 daysDistance Traveled: 500kmProfiles: 4896

SL113: June 28, 2008 – July 26, 2008Payload: CTD, AUVBDuration: 28 daysDistance Traveled: 367kmProfiles: 2136

SL114: June 28, 2008 – July 26, 2008Payload: CTD, AUVBDuration: 28 daysDistance Traveled: 423kmProfiles: 1962

How Does this Array/Sampling Regime Help

Visual the Battlespace?

3-D Visualization of the Operational Area (Space and Time)

Glider/Software Issues• Glider Configuration:

– Payload configurations:• Instrument specific calibration coefficients for some instruments reside on

the glider• Other instruments require application of calibration coefficients on shore and

further processing.– Sampling configurations:

• Flight controller is heavily burdened with flight, navigation and communication priorities

• Glider sampling directives must be fine tuned to achieve optimum data collection.

• FUTURE: all science data logged on science controller, which should eliminate many (if not all) of these issues.

• Shore-Side Processing:– FTP of raw glider data files to Rutgers– Processing at Rutgers– FTP profile data back to NAVOCEANO/NRL

Long data pipelines = lag time between measurement and application of measurement for MCM operations!

Field Issues• Working across 5 timezones – lag

between when you want something done and when it is actually done!

• Damage as a result of Deployment/Recovery in heavy seas

• Final Data Collection (making sure all data is shore-side before wiping flash cards)

What Did We Achieve?

• Successful transfer of AUV control from Rutgers University to NAVOCEANO for 24-hour Operations

• Successful characterization of the Operational Area using a fleet of AUVs deployed outside the area of interest

Future Recommendations

• NAVOCEANO – more deployments, more deployments, more deployments!

• Shore-side data QA/QC (NAVOCEANO, NRL?)

• Data visualization tools (TWRC, NAVOCEANO, NRL?)