Closed ketansand closed 1 year ago
I tried adding the amplitude in the initial guess and the fit was not improved.
We can try with Fitburst_example_generic.py with preprocessing enabled as shared by Emmanuel in this slack chat - https://chime-experiment.slack.com/archives/C038CUXAH27/p1648067677124639
Use preprocessing of data reader to adjust baseline.
@emmanuelfonseca can you confirm that using the preprocessing step helped get rid of this issue? If I look in the fitburst_example_generic.py on the main branch, it seems like it is not used actually (https://github.com/CHIMEFRB/fitburst/blob/2ed613aa862f12d700c19452d1fb7ab8d7543579/fitburst/pipelines/fitburst_example_generic.py#L331)
This issue is indeed fixed with @emmanuelfonseca 's suggestion to change the variance_range to [0., 1.]. The fix is then that I can add a flag: preprocess = True / False that can be passed by command line that will do the pre-processing step OR we can just do the pre-processing every time. Note that one issue here is that the floor is off for some reason.
i believe this has been addressed: this is partly due to past issues with impropert flagging of channels with 0s, and also the astrophysical occurrence of scintillation in a number of cases.
Some burst are not fitting correct amplitude. We can provide the guess from our mcmc fits. This affecting very bright events.