No reviews found.
| Metadata | Start Date | End Date | Comment |
|---|---|---|---|
|
GI03FLMA |
9/12/14, 4:11 PM | 8/18/15, 6:41 AM |
Deployment 1: Mooring was deployed 10-15m shallower than planned. Id: 683 By: lgarzio |
|
GI03FLMA |
8/18/15, 7:48 PM | 7/16/16, 8:00 PM |
Deployment 2: Mooring was deployed 5-10m deeper than planned. Id: 684 By: lgarzio |
|
GI03FLMA-RIS01 |
1/21/16, 7:00 PM | 3/28/16, 8:00 PM |
Deployment 2: Secondary controller failed - no recovered_host or telemetered data expected. Id: 689 By: lgarzio |
|
GI03FLMA-RIS01 |
4/27/16, 8:00 PM | 7/16/16, 8:00 PM |
Deployment 2: Secondary controller failed - no leak was detected, but the battery for the controller board was drained at recovery. No recovered_host or telemetered data expected. Id: 690 By: lgarzio |
|
GI03FLMA-RIS01 |
8/30/16, 2:00 AM | 8/12/17, 7:36 AM |
Deployment 3: Secondary controller failed - no recovered_host or telemetered data expected. Id: 694 By: lgarzio |
|
GI03FLMA |
8/8/17, 11:59 AM | 6/15/18, 3:59 AM |
Deployment 4: Mooring was deployed 5-10m deeper than planned. Id: 1450 By: lgarzio |
|
GI03FLMA-RIS01 Method: telemetered |
6/10/18, 9:59 AM | 8/11/19, 4:25 PM |
Deployment 5: The secondary controller did not establish communications at deployment; there will be no telemetered data from the instruments connected to this controller. The instruments should be logging internally and data should be available at recovery. Id: 1427 By: cdobson |
| Metadata | Start Date | End Date | Comment |
|---|---|---|---|
|
GI03FLMA-RIS01 |
Annotation ID 1427 needs to be updated. By Lori Garzio, on 3/13/19 |
||
|
GI03FLMA-RIS01-00-SIOENG000 Deployment: 3 |
8/29/16, 12:00 AM | 8/29/16, 12:00 AM |
Controller stopped telemetering on 8/29/2016. Issue is under investigation.
By Lori Garzio,
on 10/20/16
|