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

Generalize Mark 4 decoding #381

Open
mhvk opened this issue Feb 18, 2020 · 0 comments
Open

Generalize Mark 4 decoding #381

mhvk opened this issue Feb 18, 2020 · 0 comments

Comments

@mhvk
Copy link
Owner

mhvk commented Feb 18, 2020

#332 made clear that there are Mark 4 data in the wild that do not use the default track assignments. Closer reading of the docs indeed makes clear that those defaults were only recommendations for VLBA format, not fixed.

In principle, the Mark 4 header encodes all the information needed to determine how to decode the data, but will need a bit more information that just the (nchan, nbit, fanout) used now; instead it should use the full magnitude_bit array and probably the channel and sideband information. It should not even be too hard to auto-generated decoders/encoders on the fly. If that is done on first encounter, with the encoders/decoders dicts updated, it would not slow down things too much either.

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

No branches or pull requests

1 participant