Notes

Sort by:
  • Reference Designator
  • First Name
  • Created
  • Modified  
  • Metadata Start Date End Date Comment
    GA01SUMO-RII11-02-PCO2WC052
    Deployment: 2
    12/1/15 12/1/15 Data telemetry became irregular in Dec 2015. The instrument is powered and records are being telemetered, but they contain little data. Data may be logged internally on instrument.

    By Lori Garzio, on 7/6/16
    Redmine Issue #9889

    GA01SUMO-RII11-02-PCO2WC051
    Deployment: 2
    12/1/15 12/1/15 Telemetered data are irregular. The instrument is functional but is failing to send files regularly at the intended schedule.

    By Lori Garzio, on 7/6/16
    Redmine Issue #9889

    GS01SUMO-RII11-02-PCO2WC053
    Deployment: 2
    3/1/16 3/1/16 Instrument offline. Data became irregular in late Feb 2016 and ceased to contain any PC02W data. Data may be logged internally on instrument, but no files being sent by telemetry.

    By Lori Garzio, on 7/6/16
    Redmine Issue #9890

    GI05MOAS-GL478
    Deployment: 1
    9/12/14 9/12/14 Deployment 1 - deployed on 09/11/2014 and lost communications on 09/12/2014. Glider lost at sea.

    By Lori Garzio, on 7/5/16

    GA05MOAS-GL495
    Deployment: 1
    3/13/15 3/14/15 Glider was deployed for ~1 day, card data were not recovered.

    By Lori Garzio, on 11/1/16

    GA05MOAS-GL494
    Deployment: 1
    3/24/15 3/24/15 Glider lost after a digifin crack and leak. No recovered data

    By Lori Garzio, on 11/1/16

    CE07SHSM-MFD37-01-OPTAAD000
    Deployment: 4
    9/20/16 5/1/17 Instrument not deployed during Fall 2016 cruise because its refurbishment was not complete before the cruise.

    By Mike Smith, on 10/25/16
    Redmine Issue #11427

    CE06ISSM-RID16-01-OPTAAD000
    Deployment: 5
    9/27/16 5/1/17 Instrument not deployed during Fall 2016 cruise because its refurbishment was not complete before the cruise.

    By Mike Smith, on 10/25/16
    Redmine Issue #11427

    CE06ISSM-MFD37-01-OPTAAD000
    Deployment: 5
    9/27/16 5/1/17 Instrument not deployed during Fall 2016 cruise because its refurbishment was not complete before the cruise.

    By Mike Smith, on 10/25/16
    Redmine Issue #11427

    CE01ISSM-MFD37-01-OPTAAD000
    Deployment: 6
    10/1/16 5/1/17 Instrument not deployed during Fall 2016 cruise because its refurbishment was not complete before the cruise.

    By Mike Smith, on 10/25/16
    Redmine Issue #11427

    CE01ISSM-RID16-01-OPTAAD000
    Deployment: 6
    10/1/16 5/1/17 Instrument not deployed during Fall 2016 cruise because its refurbishment was not complete before the cruise.

    By Mike Smith, on 10/25/16
    Redmine Issue #11427

    CE01ISSM-RID16-01-OPTAAD000
    Deployment: 5
    7/28/16 10/2/16 Port was overcurrenting, so mission file changed to disable instrument.

    By Mike Smith, on 10/13/16
    Resolved: 10/25/16

    CE04OSSM-RID26-07-NUTNRB000
    10/1/16 5/1/17 Instrument not deployed during Fall 2016 cruise because its refurbishment was not complete before the cruise.

    By Mike Smith, on 10/25/16
    Redmine Issue #11427

    CE01ISSM-MFD37-06-CAMDSA000
    Deployment: 6
    10/30/16 5/1/17 Instrument not deployed during Fall 2016 cruise because its refurbishment was not complete before the cruise.

    By Mike Smith, on 10/25/16
    Redmine Issue #11427

    CE06ISSM-MFD37-06-CAMDSA000
    Deployment: 5
    9/27/16 5/1/17 Instrument not deployed during Fall 2016 cruise because its refurbishment was not complete before the cruise.

    By Mike Smith, on 10/25/16
    Redmine Issue #11427

    CE09OSSM-MFD37-06-CAMDSA000
    Deployment: 4
    9/21/16 5/1/16 Instrument not deployed during Fall 2016 cruise because its refurbishment was not complete before the cruise.

    By Mike Smith, on 10/25/16
    Redmine Issue #11427

    CE06ISSM-SBD17-06-CTDBPC000
    Deployment: 5
    10/21/16 5/31/17 The CTDBP on the buoy (CTDBP3) stopped responding to commands/reporting strings of nonsense characters on Friday October 21, 2016 11:30 UTC. Nonsense characters most likely means the instrument failed/flooded.

    By Mike Smith, on 10/25/16
    Redmine Issue #11433

    CE07SHSM-MFD37-06-CAMDSA000
    Deployment: 4
    10/21/16 5/31/17 For no apparent reason, the CAMDS stopped reporting data on Friday October 21 at 12:30 UTC. Do not know if the system is continuing autonomously.

    By Mike Smith, on 10/25/16
    Redmine Issue #11434

    CE07SHSM-MFD35-06-PHSEND000
    Deployment: 4
    10/13/16 DCL35 stopped reporting data on 2016-10-13 04:26 UTC. The MPEA indicates the system is booting up and drawing current, but it is not fully booting up and powering on the instruments. There will no longer be any telemetered data for this instrument.

    By Mike Smith, on 10/20/16
    Redmine Issue #11395

    CE07SHSM-MFD35-05-PCO2WB000
    Deployment: 4
    10/13/16 DCL35 stopped reporting data on 2016-10-13 04:26 UTC. The MPEA indicates the system is booting up and drawing current, but it is not fully booting up and powering on the instruments. There will no longer be any telemetered data for this instrument.

    By Mike Smith, on 10/20/16
    Redmine Issue #11395

    8 of 11