Notes

Sort by:
  • Reference Designator
  • First Name
  • Created
  • Modified  
  • Metadata Start Date End Date Comment
    CE05MOAS-GL319
    6/20/16 6/21/16 Glider 319 recovered by fisherman Glider 319 recovered 2016-06-18 6pm PDT 5.4 nm west of Newport by a recreational fisherman. The glider was returned to OSU Sunday morning undamaged. Glider was redeployed on 2016-06-21.

    By Mike Smith, on 7/11/16
    Redmine Issue #10585

    CE06ISSM
    10/7/14 10/1/16 All of the inshore surface moorings suffer from an issue called the 'top of the day problem.' A race condition exists in the CPM firmware when transferring daily log files harvested from the various sub-components in a buoy system (e.g. DCL16, CPM3, DCL35, etc) over the Iridium RUDICS connection. The primary CPM rsync's data files from the various sub-components to a central data directory. The first time a daily file is created/copied into that directory (usually shortly after midnight),...

    By Mike Smith, on 7/11/16
    Redmine Issue #8151

    CE01ISSM
    4/17/14 10/1/16 All of the inshore surface moorings suffer from an issue called the 'top of the day problem.' A race condition exists in the CPM firmware when transferring daily log files harvested from the various sub-components in a buoy system (e.g. DCL16, CPM3, DCL35, etc) over the Iridium RUDICS connection. The primary CPM rsync's data files from the various sub-components to a central data directory. The first time a daily file is created/copied into that directory (usually shortly after midnight),...

    By Mike Smith, on 7/11/16
    Redmine Issue #8151

    CE07SHSM-RID26-01-ADCPTA000
    6/24/16 10/1/16 Instrument Failure: CE07SHSM-RID26-01-ADCPTA000 Deployment: 3 Issue: ADCP battery has been depleted. There is probably a leak or short somewhere.

    By Mike Smith, on 7/11/16
    Redmine Issue #10693

    CE09OSSM-SBD11-06-METBKA000
    12/23/15 5/12/16 Issue: The Relative Humidity measurement (RELHUMI) from the METBK data logger started reporting erroneous values on 2015-12-23. This instrument was damaged during a storm and replaced on May 12, 2016.

    By Mike Smith, on 7/11/16
    Redmine Issue #9425

    CE01ISSM
    8/8/16 10/4/16 Correcting the iridium data telemetry issues, permitting full telemetry of data files, resulting in greater power consumption than anticipated. Result is power level of the battery pack has dropped below operational limits and subsystems can no longer power instruments. Shutting the mooring down, and placing in a low power maintenance mode.

    By Mike Smith, on 8/11/16
    Redmine Issue #10922

    CE06ISSM
    7/27/16 10/4/16 Correcting the iridium data telemetry issues, permitting full telemetry of data files, resulting in greater power consumption than anticipated. Result is power level of the battery pack has dropped below operational limits and subsystems can no longer power instruments. Shutting the mooring down, and placing in a low power maintenance mode. 11 instruments offline. Will need to recover and redeploy new mooring during Fall 2016 cruise

    By Mike Smith, on 8/11/16
    Redmine Issue #10927

    CE09OSSM-SBD11-06-METBKA000
    8/17/16 10/4/16 The METBK-CT data signal flatlined on 2016/08/17 15:48:20.780. Data from that date forward should be considered as suspect. Disposition: Will need to recover mooring and redeploy new instance.

    By Mike Smith, on 8/22/16
    Redmine Issue #11024

    CE05MOAS-GL319-05-CTDGVM000
    8/7/14 8/21/14 Deployment 2 - test deployment, no data on the server.

    By Lori Garzio, on 8/31/16

    CE05MOAS-GL319-05-CTDGVM000
    11/20/15 11/22/15 Deployment 3 - buoyancy pump failure and leak in fwd compartment, recovered early on 11/22/2015

    By Lori Garzio, on 8/31/16
    Redmine Issue #9402

    CE05MOAS-GL320
    10/6/14 12/29/14 Deployment 1 - Power consumption was greater than 1% per day and battery ran down to 10% before the end of the deployment. Glider was drifting before it was recovered.

    By Lori Garzio, on 9/1/16

    CE05MOAS-GL320-01-PARADM000
    10/6/14 12/29/14 Deployment 1 - PAR ball bent upon recovery of the glider

    By Lori Garzio, on 9/1/16

    GS01SUMO-RII11-02-CTDBPP031
    5/1/16 11/30/16 Deployment 2 - instrument is sending bad data that likely cannot be parsed by the system. Instrument expected to be replaced in Nov 2016

    By Lori Garzio, on 9/13/16
    Redmine Issue #11172

    CE06ISSM-RID16-03-CTDBPC000
    Deployment: 5
    7/18/16 Battery on CTDBP1 has been depleted. Unit is no longer recording data.

    By Mike Smith, on 10/13/16

    CE06ISSM-RID16-07-NUTNRB000
    Deployment: 5
    5/15/16 > > The NUTNR is starting to show signs of degraded performance, variable values spanning +- ranges. > > NUTNR failed, now reporting only 0. Unit has completely failed. No longer getting any data.

    By Mike Smith, on 10/13/16

    CE02SHSM-RID26-06-PHSEND000
    Deployment: 3
    8/1/16 8/8/16 > Plots of the pH data for CE02SHSM indicate that unit may be experiencing biofouling, causing increased variability in the data signal. Whatever was causing the spiky signal appears to have cleared and resolved itself. Signal looks good for now.

    By Mike Smith, on 10/14/16

    CE02SHSM-RID27-01-OPTAAD000
    Deployment: 3
    7/16/16 10/4/16 The OPTAA on the CE02SHSM-00003 NSIF has failed. Unit started reporting variable values, including raw counts of 1 for all channels, before stopping completely on 2016-07-18.

    By Mike Smith, on 8/11/16
    Redmine Issue #10924
    Resolved: 9/28/16

    CE02SHSM-RID26-07-NUTNRB000
    Deployment: 3
    8/2/16 9/28/16 NUTNR has been showing light values equivalent to dark values (i.e. all zeros) since 2 August.

    By Mike Smith, on 10/14/16

    CE07SHSM-RID26-07-NUTNRB000
    Deployment: 3
    5/19/16 9/27/16 NUTNR has been showing light values equivalent to dark values (i.e. all zeros) since 19 May. Previous to all zeros, values reached +/- 600 uMol/l... Leave instrument on, and monitor to see if anything comes back...

    By Mike Smith, on 10/14/16

    CE09OSSM-RID26-07-NUTNRB000
    Deployment: 3
    7/14/16 9/22/16 > Stopped receiving any data from the NUTNR on 2016/07/14 06:00:02.808. No apparent reason. Will investigate. No obvious cause. Am disabling further logging of data by DCL.

    By Mike Smith, on 10/13/16

    1 of 11