Repository navigation
Trouble with Dolfyn reading Nortek ad2cp files #468
Replies: 8 comments 3 replies
|
Hi @Greg-Ellis-NOAA, thank you for your interest in MHKiT-Dolfyn and bringing up this issue. It's not you, reading SigVM-generated ad2cp files has been a work in progress as Nortek has been making small changes with each firmware update. |
|
Thanks for the quick reply! Here's the contents of the log file dolfyn generated when attempting to read one of the offending files: root - INFO - 5641: A5, 10, 15, 2392, 0, 1, 1 root - INFO - 8043: A5, 10, 1C, 774, 0, 1, 1 root - INFO - 8827: A5, 10, 1C, 774, 1, 2, 2 root - DEBUG - Lost sync byte at pos: 9611 root - DEBUG - Header is not 10 or 12 bytes: 9611 root - INFO - No new header configuration string found root - DEBUG - Header is not 10 or 12 bytes: 12065 root - DEBUG - Lost sync byte at pos: 37777 root - DEBUG - Header is not 10 or 12 bytes: 37777 root - DEBUG - Lost sync byte at pos: 39331 root - DEBUG - Header is not 10 or 12 bytes: 39331 root - DEBUG - Lost sync byte at pos: 41050 root - DEBUG - Header is not 10 or 12 bytes: 41050 root - INFO - Invalid skip byte at pos: 41050 |
|
All of the files have the same symptom: the only read the first time value. The uploader does not like .ad2cp files (or presumably SigVM files either) so I've re-named an example SigVM to .zip and attached it. Thanks for all your help! |
|
Hi @Greg-Ellis-NOAA, I was able to read this file in the latest version of MHKiT installed via import mhkit
mhkit.__version__ds = mhkit.dolfyn.read("./data/106184_20261006T015132UTC.AD2CP")ds.info()And saving the file yields: mhkit.dolfyn.save(ds. "data/106184_20261006T015132UTC.nc")106184_20261006T015132UTC.nc.zip In the attached zipped nc file The output of dolfyn has 1 timestamp and did not yield any errors:
The 1 timestamp seems like an unexpected result and also the output nc file is much smaller than the input .AD2CP file . Can you confirm you are expecting more than 1 timestamp? |
|
@Greg-Ellis-NOAA, my bad. Just read through this. You are definitely seeing the same thing as my version. |
|
Wow this one's a doozy. PR #471 will allow you to read most of the file, but not the bottom track information. |
|
Glad you are making progress. This does not look like it's simple. Unfortunately I was not involved with configuring the instrument- I only got the SigVM files after the fact. As such, I'm unsure of the acquisition rates. Nortek's VM Review software shows an ensemble frequency of 1 Hz. When I look at the ground track data & echosounder, they are also reporting on a one-second basis, but I think the software may be interpolating those numbers to match the ensemble frequency. I've attached a second, longer file that shares the same problems as the one I sent before. I discovered the first file appears to have been acquired while the vessel was moored during deployment, so even once it's read successfully, it may look strange (it only has a couple of cells above the bottom). The second one is more representative of the remainder of the mission. thanks again! |
|
Will do, thanks- I'm travelling to a conference at the moment but I will
investigate as time permits.
…-Greg
On Mon, Oct 19, 2026 at 5:31 PM James McVey ***@***.***> wrote:
@Greg-Ellis-NOAA <https://github.com/Greg-Ellis-NOAA> Please check out PR
#471 <#471> and see if
that works for you. The first 3 datapoints for each variable are going to
contain zeros, but I'm still working through that
—
Reply to this email directly, view it on GitHub
<#468?email_source=notifications&email_token=B7B5AM4ZHYJLY6B6BNDK7UL5U2B2ZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJQGUZDEOBTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-19052283>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/B7B5AM3L33H6PE44HQUHR7T5U2B2ZAVCNFSNUABIKJSXA33TNF2G64TZHMZDEOBWG43TCOJQHNCGS43DOVZXG2LPNY5TCMJQGEYTQNBUUF3AE>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/B7B5AM7INDXE2JVLGW7MDMD5U2B2ZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJQGUZDEOBTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ>
and Android
<https://github.com/notifications/mobile/android/B7B5AMZ3GGWJ46PK5PUSCPT5U2B2ZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJQGUZDEOBTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>.
Download it today!
You are receiving this because you were mentioned.Message ID:
***@***.***
.com>
--
Gregory Ellis, PhD
Oceanographic Research Analyst (IBSS contractor)
Northeast Fisheries Science Center (remote)
239-404-2088
|

Uh oh!
There was an error while loading. Please reload this page.
Hi all,
I've used Dolfyn for a while now to read Teledyne ENX files and it's worked flawlessly for that. Recently I've been tasked with processing some Nortek data in SigVM files. I believe the instrument is a Signature 1000; I know it has an integrated echosounder (which may be the issue here, but also may not).
I've pulled the ad2cp files from the SigVM archives and tried reading them with Dolfyn, but the resulting netCDFs only contain the first time element. I can open the files in Nortek VM Review and all time elements are read, so the files don't appear to be flawed. I've tried 'reset index', but that hasn't solved things.
My guess is this is a rookie error since I haven't used SigVM/ad2cp files before. Anybody have any guesses where this is going wrong?
thanks in advance,
Greg
All reactions