Skip to content

fix: make dropped coalescent prior explicit#866

Draft
ivan-aksamentov wants to merge 1 commit into
rustfrom
fix/timetree-coalescent-no-prior-visibility
Draft

fix: make dropped coalescent prior explicit#866
ivan-aksamentov wants to merge 1 commit into
rustfrom
fix/timetree-coalescent-no-prior-visibility

Conversation

@ivan-aksamentov

Copy link
Copy Markdown
Member

fix/timetree-coalescent-no-prior-visibility -> rust

When constant or skyline coalescent optimization failed with no previous value and no --coalescent seed to fall back on, the run proceeded with no coalescent prior while logging the misleading "keeping previous Tc" -- there was no previous value to keep.

This reports the failure explicitly, stating whether the previous prior is retained or the run proceeds with no coalescent prior this round [src].

Work items

  • Report the retained-versus-dropped coalescent prior explicitly on optimization failure [src]

When constant or skyline coalescent optimization failed with no previous value or --coalescent seed to fall back on, the run proceeded with no coalescent prior while logging the misleading "keeping previous Tc" (there was none to keep). Report the failure explicitly, stating whether the previous prior is retained or the run proceeds with no coalescent prior this round.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant