Marten van Kerkwijk

I hope this can be for the ASP format that @misanthropealoupe is implementing: https://github.com/misanthropealoupe/baseband/tree/asp

Part of making vdif more robust is in https://github.com/mhvk/baseband/tree/vdif-more-robust But that would not work all that well either, or at least be very inefficient. Better might be to read quite...

Looking at this again, I think the best solution would in fact be to read and reorder the file ourselves (using the raw VDIF writer). It might make sense to...

For really regularly behaved data, an intermediate file reader that does the reordering on the fly is also possible.

@IMFardz - could you provide a bit more detail: once the even-numbered threads appear, do they have the frame number? I think the trick would be to just start a...

@IMFardz - interestingly different... I think you could indeed just wrote two files. Alternatively, open the file in two readers, one for odd and one for even, and just collect...

@IMFardz - yes, that looks pretty good! Small comments (not functionally important, but to help understanding): opening the files with 'rb' and 'wb' allows you to avoid using `fh_raw`; this...

Concretely, I guess this might be implemented as a new `verify='strict'` in `VDIFFrameSet` (given that we have data that fails the test, I'd prefer not to make it the default...)....

@TheMartianLife - thanks so much for offering to help! I have not thought about this issue for quite a while, but I think consistency with the specification would be first....

In principle, the current machinery can sort-of deal with it, but it would help to have a way to mark frames as impossible to reach, maybe in `RawOffsets`?