Squashing unintended test warnings due to model recombination rate #1626
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.
As triggered by #1598 (comment) I looked into the test warnings due to model specific mutation and recombination rate.
One test warning was not intended, so I fixed that.
I am a bit confused what to do with these ones:
As indicated by @nspope these seem to come from mitochondria (that have rec rate of 0), but I am getting lost in the code of how these tests are autogenerated and called. Can anyone suggest what I could do to capture these tests - they are making noise that we probably don't want?