Fails with filterbanks by written by Your

[josephwkania]

RFIClean exits with error ERROR: ERROR: Input data to rficlean is not in filterbank format
when run on filterbanks written by Your.
I'm not sure where the problem is, the same files with headers made in alternative ways run fine.
My guess is there is some strange interaction with how Your headers are written and RFIClean's header parser, since
Sigproc's header and Presto's readfile work are able to read Your headers.

I've attached
small_fil.tar.gz
a small filterbank that reproduces the issue.

[ymaan4]

Thanks for bringing this up, and sorry for such a late response on this. Yes, this is a potential bug or a potential misunderstanding. The problem is that the "data_type" in your example file is set to 0, which is parsed as "raw data". A case for potential misunderstanding is whether the raw data means voltage data (in which case it will not be a valid sigproc format data) or just raw intensity/polarimetric-intensity data (in which case, it should be read as valid sigproc filterbank data). If latter is the case, then the following two lines should be added in the rficlean.c file "switch (data_type) { }" block: case 0: break; I will be happy to include it in the next release after a better understanding of what "raw data" means in this context. If you already have an understanding on that, please do share.

…

On Sun, Oct 23, 2022 at 6:48 AM Joseph Kania ***@***.***> wrote: RFIClean exits with error ERROR: ERROR: Input data to rficlean is not in filterbank format when run on filterbanks written by Your <https://github.com/thepetabyteproject/your>. I'm not sure where the problem is, the same files with headers made in alternative ways run fine. My guess is there is some strange interaction with how Your headers are written and RFIClean's header parser, since Sigproc's *header* and Presto's *readfile* work are able to read Your headers. I've attached small_fil.tar.gz <https://github.com/ymaan4/RFIClean/files/9845525/small_fil.tar.gz> a small filterbank that reproduces the issue. — Reply to this email directly, view it on GitHub <#12>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABXWLAFI5ILOH2UVXDCBZZLWESG5VANCNFSM6AAAAAARMCLBIM> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>