With the dev branch now having both airy and gaussian fits which fit decides how many valid beads there are? We have a SoRa superres (maybe, lets not argue that here!) dataset that has relatively low s:n and bad airy fits. When passed through the R^2 thresholds of 0.85 for both fits we get back no valid beads and so no data is saved. If I set the airy R^2 threshold to 0.5 and the Gaussian to .85 then I get a bunch of valid fits and output data is saved.
The long term solution is to go with whatever we are using for the final fit, or toggle between the two. Short term I think the as the Gaussian fits have much higher R^2 we should use the Gaussian to make valid/invalid decisions.
With the dev branch now having both airy and gaussian fits which fit decides how many valid beads there are? We have a SoRa superres (maybe, lets not argue that here!) dataset that has relatively low s:n and bad airy fits. When passed through the R^2 thresholds of 0.85 for both fits we get back no valid beads and so no data is saved. If I set the airy R^2 threshold to 0.5 and the Gaussian to .85 then I get a bunch of valid fits and output data is saved.
The long term solution is to go with whatever we are using for the final fit, or toggle between the two. Short term I think the as the Gaussian fits have much higher R^2 we should use the Gaussian to make valid/invalid decisions.