Looking at the recent VEL3D deployments for CE02SHBP and CE04OSBP, it appears that the reported velocities are an order of magnitude less than prior deployments. The GoldCopy files all report the units as m/s. Was there a processing change? If the issue is unit related, could someone please confirm the units of the data for each deployment? Many thanks.
Hi Ian,
Can you send me the time periods/parameters you are looking at? When I plot the last deployment and current one (fall 2024 - spring 2026) for east and north, they are looking fairly consistent on OOINet. I’m wondering if there is a discrepancy between the gold copy thredds server files and M2M.
Hi Wendi,
Here is what is shown in Data Explorer if you zoom in on the last half of 2023 and the first part of the 2024 deployment.
I compiled deployments 5-12 on the OOI JupyterHub and here are the 0.1 and 0.9 quantiles for the northward component for each deployment. D0010-D0012 seem off to me compared to prior deployments.
D0005, -0.47, 1.00
D0006, -0.61, 0.58
D0008, -0.84, 0.48
D0009, -0.45, 0.71
D0010, -0.08, 0.23
D0011, -0.22,0.17
D0012, -0.10, 0.06
Thanks!
- Ian
Ian,
The code to calculate the velocity was updated in late 2023 (see commit link below). There is data in the Gold Copy THREDDS catalog that predates this. We will need to issue a reload request for those two sensors.
Chris
Great, thanks for looking into this everyone.
I can implement this fix in the files I have created for myself. A reload fix would be great in the long term. Then I won’t have to worry about keeping an edge case in my code or about others misinterpreting results if recycling/replicating my work in the future. Thanks again!