New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DM-43033: Update to fgcm 3.10.5 with reserved refstar updates. #41
Conversation
This can kick in for the first iteration, or for very limited coverage.
Fix some small issues when using/reserving reference stars.
Additional fixes for reference star reserving that were not properly handled with last PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. See one minor comment...
@@ -576,6 +576,10 @@ def loadStars(self, fgcmPars, | |||
if test.size > 0: | |||
self.fgcmLog.info('Flagging %d stars as reference star outliers from previous cycles.' % | |||
(test.size)) | |||
test, = np.where((flagFlag[a] & objFlagDict['REFSTAR_RESERVED']) > 0) | |||
if test.size > 0: | |||
self.fgcmLog.info('Flagging %d stars as reference star reserved from previous cycles.' % |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sentence isn't very clear. Something like 'Flagging %d stars as reference stars that were reserved from previous cycles.' (if I am correctly interpreting the original sentence) would be better.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changing it at this point will have to wait for the next version of fgcm, unless I go through a whole rigmarole. But thank you for pointing this out.
No description provided.