Closed taldcroft closed 4 years ago
The other impact being that, since starcheck force includes all the stars and halfwidths for review, that catalogs in that final review could have incorrect acquisition probabilities due to incorrect internal assignment of box sizes for that assessment.
We'll want to get this promoted on the HEAD side relatively quickly for that use case, but I don't see a big operational impact with proseco 4.8.0 on the FOT side. However, I also don't see work-around from ORViewer if we actually did need to specify halfwidths for stars that have candidates out of mag order.
Agreed. Note that your first impact is technically covered by what I said (multiple stars being force-included), but I edited to call out your point that this does regularly happen.
As mentioned I believe that in current practice the case of specifying multiple stars with explicit halfwidths is no longer going to happen in FOT planning. But in any case this bugfix will be available and it now looks like a smaller MATLAB release is going to happen before the 2019b update.
Description
This fixes #323 and supercedes #324. The actual bug fix is simple but I spent some time understanding how it can come about and why the original tests did not show a problem. In short the problem comes up when the initial
p_acq
for included candidate stars does not increase monotonically with decreasingmag
. This can happen because of a spoiler or hot pixel.This only impacts cases with more than one included star. In actual star selection with MATLAB choosing more than one star is not common and typical practice now would be to not explicitly select the halfwidths. It has a definite impact in starcheck which uses force-include of all stars and halfwidths for every catalog.
Testing
Also ran this test from #324 and confirmed that the update changes this test from fail to pass, but did not include in the final PR.
Fixes #323 Closes #324