Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DOLfYN reading a .VEC file indefinitely #370

Open
akeeste opened this issue Jan 7, 2025 · 1 comment · May be fixed by #372
Open

DOLfYN reading a .VEC file indefinitely #370

akeeste opened this issue Jan 7, 2025 · 1 comment · May be fixed by #372

Comments

@akeeste
Copy link
Contributor

akeeste commented Jan 7, 2025

Describe the bug:

@jmcvey3 I'm assisting another user with reading their .VEC file. DOLfYN gets stuck and reads it indefinitely. Other VEC files from this user are read normally.

The issue occurs when _NortekReader.init_ADV() is attempting to determine the code spacing. In code_spacing, the first call to self.findnextid() gets stuck in the while loop, seemingly because the ID it is searching for is never found.

To Reproduce:

ds_adv2 = dolfyn.io.api.read("SANDIA02.VEC"). @akeeste can share the data directly if needed.

Expected behavior:

Run without error, as on other VEC files

Screenshots:

If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: Windows 11
  • MHKiT Version: v0.9.0

Additional context:

@akeeste akeeste linked a pull request Jan 9, 2025 that will close this issue
@akeeste akeeste linked a pull request Jan 9, 2025 that will close this issue
@jmcvey3
Copy link
Contributor

jmcvey3 commented Jan 14, 2025

File appeared to be either corrupted or filled with "fill" bytes added during real-time operation. There were two "while loops" that the script became hung up on, and PR #372 added logic to escape these loops.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants