-
Notifications
You must be signed in to change notification settings - Fork 1
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
hdfWaterfall with LWA-NA #14
Comments
In addition to the pulsar test this morning I also ran a two hour zenith pointing yesterday evening to look for packet loss/missing data/time tag things. I only see a couple of problems in that run so I'm hoping that that will solve this issue. Although we may still need to do additional tweaking in NDP to better meter what we send to the data recorders. |
That also reminds me - |
Last few observation files that I have been reading, after the changes to the command time handling + buffer, have worked completely fine. Those changes, and a few others noted here, probably solved this issue by proxy. |
Just kidding, looks like some of the recent changes to /lsl/reader/ldp.py are causing some fault. Made it half way through the file before losing the cFrames variable somehow. Going to look at some of these inputs to see if something weird is going on.
|
Using the -m flag with the metadata does not cause this error to present. (sometimes) |
What file/command signature threw the |
Oh for this it would have been this: |
This exception should be fixed now in main/lwana. |
hdfWaterfall.py seems to behave poorly with North Arm data. It appears to have trouble handling stale data at the start of a file, either denying to process the data because it thinks the observation is at the wrong start time, requested offsets not cooperating with the code, or something else.
The text was updated successfully, but these errors were encountered: