Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Investigate what we need to do after a nni- and branchelngth_optim! #38

Open
nossleinad opened this issue Aug 28, 2024 · 0 comments
Open

Investigate what we need to do after a nni- and branchelngth_optim! #38

nossleinad opened this issue Aug 28, 2024 · 0 comments

Comments

@nossleinad
Copy link
Collaborator

nossleinad commented Aug 28, 2024 •
edited
Loading

We could maybe drop the felsenstein_down! calls and replace log_likelihood! with log_likelihood in tree_polish! for instance.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nossleinad