As discussed in #83 and the telecon it would be good to figure out whether our birdies are narrow or broadband to see if there are better ways of mitigating those.
A folded candidate for the LTE birdie looks like this:
I think that almost looks like we should maybe add a few channels at ~760 to the bad channels.
I created that using the command docker run --rm -v /data/chime/sps/raw:/data/chime/sps/raw -v /dev/shm:/dev/shm --shm-size=100gb -v /data/lkuenkel/rfi_test/fold_birdies/:/data/lkuenkel/rfi_test/fold_birdies/ chimefrb/champss_software:latest fold_candidate --date 20240615 --ra 325.06 --dec 51.55 --foldpath "/data/lkuenkel/rfi_test/fold_birdies" --dm 0 --f0 1.5625
I think it also would be good to have some script, which we can occasionally run to test whether we need to adjust our bad channel mask.
I won''t tackle this problem, before I focus on ML classification but if someone else wants to look into this I would be very happy.
As discussed in #83 and the telecon it would be good to figure out whether our birdies are narrow or broadband to see if there are better ways of mitigating those.
A folded candidate for the LTE birdie looks like this:
I think that almost looks like we should maybe add a few channels at ~760 to the bad channels.
I created that using the command
docker run --rm -v /data/chime/sps/raw:/data/chime/sps/raw -v /dev/shm:/dev/shm --shm-size=100gb -v /data/lkuenkel/rfi_test/fold_birdies/:/data/lkuenkel/rfi_test/fold_birdies/ chimefrb/champss_software:latest fold_candidate --date 20240615 --ra 325.06 --dec 51.55 --foldpath "/data/lkuenkel/rfi_test/fold_birdies" --dm 0 --f0 1.5625I think it also would be good to have some script, which we can occasionally run to test whether we need to adjust our bad channel mask.
I won''t tackle this problem, before I focus on ML classification but if someone else wants to look into this I would be very happy.