Change dyn_bgd_n_faint default to 2 and fix faint force-include bug #403
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Change the proseco dyn_bgd_n_faint default to 2.
This had originally been left at 0 for continuity and regression testing convenience / historical compatibility, but at this point it is just confusing that the default isn't the "2" that is being used in FOT operations.
Also fixes a bug that force-included guide stars could be discarded if faint.
Interface impacts
Testing
Unit tests
Independent check of unit tests by @taldcroft:
Functional tests
test_guides_include_close is a functional test that faint force-included guide stars are included in the final catalog.