-
Notifications
You must be signed in to change notification settings - Fork 0
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
Use dyn_bgd_n_faint = 2 #412
Conversation
@taldcroft I was thinking about updating this WIP to set dyn_bgd_n_faint to 2 by default but include a starcheck cmdline option (mostly if we needed to run with dyn_bgd_n_faint = 0 for transition weeks or regression). What are your thoughts? I think we don't need to take the dyn_bgd_n_faint value from the pickle, though if we did we'd then want to check it against 2 anyway and make sure that dyn_bgd_n_faint wasn't set to an unexpected value of != 2. What were you thinking on this topic? |
This is a good example of where our infrastructure does not handle changing configurations very well. We need some data source to tell starcheck what is the expected value of Overall I don't think that I agree with the concept of exporting values like |
I just figured a cmdline option was the easiest way to let me see "what would this be without the bonus" which I thought could have value for load review to me and testing during the transition. (Well.. and I thought it was likely that an override to dyn_bgd_n_faint = 3 might be useful). |
Updated to use local date-based selection. |
I'm not sure why we need to answer that question going forward. The program has agreed that mission loads shall be planned using the bonus when dyn bgd is enabled and it is extremely unlikely that we'll ever plan observations using the legacy background. In the event that we do need to answer that question, it can be done easily enough with a local dev version with changed constants. |
And while I'd rerun the testing with the latest updates, I'd forgotten to update the description to indicate that the cmdline option is gone and the starcheck text output is gone. Done. |
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.
Finished review. There is only one substantive comment that might require re-running tests, but if so then you might as well address the code nitpicks.
# Pass 1 to _guide_count as third arg to use the count_9th mode | ||
my $bright_count = sprintf("%.1f", | ||
call_python("utils._guide_count", [ \@mags, $self->{ccd_temp}, 1 ])); | ||
# Pass 1 to _guide_count as fourth arg to use the count_9th mode |
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 comment is no longer accurate but can be removed now with the kwargs explicitly called out.
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.
I updated the comment.
@jeanconn - looks good. Is there any way in the functional testing to validate the new code which applies the bonus temperatures to the dark cal? From what I can see the code looks reasonable but still. I see you put the |
Good point on the functional testing. I think I just did some print statements when I was adding the code - I will look to see if it makes sense to grab t_ccd from that diagnostic dict or just print out some stuff for this PR. |
I think I still need @taldcroft to either agree this is done or decide that #418 is reasonable and should also be merged. |
Incremental updates to the testing outputs in the description are non-trivial across an agasc supplement update weekend, so I've set the outputs to be remade and will rereview. |
Co-authored-by: Tom Aldcroft <taldcroft@gmail.com>
Co-authored-by: Tom Aldcroft <taldcroft@gmail.com>
Co-authored-by: Tom Aldcroft <taldcroft@gmail.com>
Co-authored-by: Tom Aldcroft <taldcroft@gmail.com>
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 great!
👍 And I confirm I've re-reviewed the diff outputs and see only the expected changes from dynamic bonus. |
Add a unit test for dyn bgd hotpix imposter calc
Description
Update starcheck to apply dyn_bgd_n_faint bonus = 2 to guide_count and imposter checking.
Interface impacts
None.
Testing
Tested with ska3-matlab-2023.4rc6 on fido. This PR requires sparkles 4.22.1 .
Unit tests
Functional tests
Ran a set of weeks and tested the cmdline option with output from this script at
https://icxc.cfa.harvard.edu/aspect/test_review_outputs/starcheck-pr412