There is no pressure variable in the .nc files - this should be a coordinate.

By Lori Garzio, on 6/18/19

Several presf_wave_burst_pressure values (purple in attached plot) are suspect. Excluding from final data ranges.

By Lori Garzio, on 6/18/19

Several presf_wave_burst_pressure values (purple in attached plot) are suspect. Excluding from final data ranges.

By Lori Garzio, on 6/18/19

presf_tide_pressure values are around 183 dbar when the instrument was deployed at 446 according to asset management. Excluding from final data ranges. presf_wave_burst_pressure values are more reasonable around 459 dbar.

By Lori Garzio, on 6/18/19

For deployment 1, the deployment depth in asset management is 455, but the pressure in the files is 472. For the rest of the deployments, the difference between the AM depth and pressure in the files is 7-18.

By Lori Garzio, on 6/17/19

presf_tide_pressure and presf_wave_burst_pressure are all fill values for deployment 2. According to the provenance.json computed_provenance errors, the calibration values are missing. Provenance files here: https://marine.rutgers.edu/cool/ooi/data-eval/data_review/CP/CP04OSSM/CP04OSSM-MFD35-02-PRESFC000/

By Lori Garzio, on 6/18/19

It is unclear what the second dimension for the wave_burst seafloor pressure is. Right now it's an index from 0-1023. This dimension should be described in the documentation and/or global attributes.

By Lori Garzio, on 6/18/19

It is unclear what the second dimension for the wave_burst seafloor pressure is. Right now it's an index from 0-1023. This dimension should be described in the documentation and/or global attributes.

By Lori Garzio, on 6/18/19

It is unclear what the second dimension for the wave_burst seafloor pressure is. Right now it's an index from 0-1023. This dimension should be described in the documentation and/or global attributes.

By Lori Garzio, on 6/18/19

It is unclear what the second dimension for the wave_burst seafloor pressure is. Right now it's an index from 0-1023. This dimension should be described in the documentation and/or global attributes.

By Lori Garzio, on 6/14/19

Excluding erroneous data at the end of deployment 2

By Lori Garzio, on 6/14/19

Excluding erroneous data at the end of deployment 3

By Lori Garzio, on 6/14/19

The missing 81 days of data at the end of deployment 2 should be annotated.

By Lori Garzio, on 6/14/19

The missing 68 days of data at the end of deployment 3 should be annotated.

By Lori Garzio, on 6/14/19

gaps in the data need to be tied to the annotation in the system.

By Leila Belabbassi, on 6/14/19

suspect data

By Leila Belabbassi, on 6/14/19

suspect data

By Leila Belabbassi, on 6/14/19

suspect data

By Leila Belabbassi, on 6/14/19

suspect data

By Leila Belabbassi, on 6/14/19

suspect data

By Leila Belabbassi, on 6/14/19