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

Investigate/Fix empty output for first second of VDIF data #26

Open
robotopia opened this issue Jun 16, 2023 · 3 comments
Open

Investigate/Fix empty output for first second of VDIF data #26

robotopia opened this issue Jun 16, 2023 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@robotopia
Copy link
Contributor

No description provided.

@robotopia robotopia added the bug Something isn't working label Jun 16, 2023
@robotopia robotopia self-assigned this Jun 16, 2023
@bwmeyers
Copy link
Contributor

@cplee1 Is investigating. It appears that the first second of data is essentially random or near-zero data, indicating it's related to accessing a buffer before it's been populated correctly. Comparing the PSRFITS and VDIF timestamps indicates that they are matching and correct if the first second is ignored, so it really does look like an extra second of "nothing" is being written for no apparent reason.

@cplee1
Copy link
Contributor

cplee1 commented Apr 29, 2024

Below is a screenshot of the native-resolution detected timeseries output from the combination of CDMT and dedisp at a DM of 0. It seems that the first second is mostly constant followed by some offset chunks at the edges of the timeseries, presumably from scales/offsets computed at the edge. I'll also add that the last chunk of the timeseries is always offset as well.

nchan01

@bwmeyers
Copy link
Contributor

See #45 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants