You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file has a large number of filled-in frames, in which the header has invalid_data=True, the correct frame size, all 0 otherwise in the first four words (so that nchan, seconds, etc., are wrong), and 0x11223344 in the second four header words as well as in the whole payload (i.e., the Mark 5B invalid data fill pattern). Specifically,
In [30]: fh.fh_raw.seek(7967*fh.header0.frame_nbytes)
Out[30]: 63990944
In [31]: f = fh.fh_raw.read_frame()
In [32]: [hex(i) for i in f.header.words]
Out[32]:
['0x80000000',
'0x0',
'0x3ec',
'0x0',
'0x11223344',
'0x11223344',
'0x11223344',
'0x11223344']
The text was updated successfully, but these errors were encountered:
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?
@00rebe wrote:
This file has a large number of filled-in frames, in which the header has
invalid_data=True
, the correct frame size, all 0 otherwise in the first four words (so thatnchan
,seconds
, etc., are wrong), and0x11223344
in the second four header words as well as in the whole payload (i.e., the Mark 5B invalid data fill pattern). Specifically,The text was updated successfully, but these errors were encountered: