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

VDIF output smearing #45

Open
bwmeyers opened this issue Apr 15, 2024 · 5 comments
Open

VDIF output smearing #45

bwmeyers opened this issue Apr 15, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@bwmeyers
Copy link
Contributor

@cplee1 has noticed that essentially for all MSPs with small-scale structures, we are not able to resolve them (whereas in the legacy beamformer, and even in the PSRFITS output we can at least see hints of structures).

This hints at two possibilities:

  • DSPSR's coherent dedispersion is not behaving as expected on our VDIF data (need to check headers, ensure consistency)
  • our VDIF writing is getting something wrong such that the signals are smeared even after coherent dedispersion

It's more than likely the latter, but the first is easier to check so we should do that.

@bwmeyers bwmeyers added the bug Something isn't working label Apr 15, 2024
@robotopia
Copy link
Contributor

robotopia commented Apr 15, 2024

Perhaps the easiest way to check the latter is to exploit the Power of Git to see whether any of the relevant VDIF-writing code has changed since the last time someone (Dilpreet??) used it successfully to look at fine structure.

@cplee1
Copy link
Contributor

cplee1 commented Apr 15, 2024

Below are examples for J0034-0534 (P=1.9 ms) and J2241-5236 (P=2.2 ms). I've checked that I can see smearing when processing both legacy and MWAX observations with VCSBeam/dspsr. I've also checked the dispersion delay over the filterbank channels to rule out intrachannel smearing. The dspsr filterbanks are processed with 80 kHz fine channels, which should allow for 12.5 us time resolution.

J2241_example
J0034_example

@robotopia
Copy link
Contributor

Possibly related to this is the fact that the VDIF output also had zeros at the front, and strange artefacts at the second boundaries. I believe I have fixed at least the zeros-out-the-front error in f0433e7 (branch "bug/ipfb_broken"). It remains to be seen whether this also fixes the other problems.
@cplee1 I'll leave it for you to check and report back.

@robotopia
Copy link
Contributor

FYI: the other commits in bug/ipfb_broken include patches for:

  • 7522679: including NPOL 2 in the VDIF header (but this may not be the best way to do it)
  • 7522679: Adding back in the -n option to the beamformer to chunk the processing
  • 25ac38e: Changed function names in accordance with mwa_hyperbeam's latest version (v0.7)

@bwmeyers
Copy link
Contributor Author

bwmeyers commented May 18, 2024 via email

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