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.

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

Number of starting networks in NetRAX #7

Open
lutteropp opened this issue Nov 25, 2020 · 9 comments
Open

Number of starting networks in NetRAX #7

lutteropp opened this issue Nov 25, 2020 · 9 comments

Comments

@lutteropp
Copy link
Owner

We agreed earlier that all random starting networks should be random trees.

5 random starting networks are not enough, even if the "true" network is a tree. RAxML-NG uses by default 10 parsimony + 10 random starting trees. I tried NetRAX (with only 5 random start networks) on a small (10 taxa) tree dataset and it got stuck in a local optimum.

I suggest copying the default from RAxML-NG and also using 10 random starting trees + 10 random parsimony trees in NetRAX.
For later, we could think about replacing the parsimony trees by parsimony networks.

@lutteropp
Copy link
Owner Author

lutteropp commented Nov 25, 2020

How about these two experimental setups:

A: Start NetRAX from 10 random + 10 parsimony trees
B: Start NetRAX from only the best RAxML-tree

@lutteropp
Copy link
Owner Author

I implemented the two setups I suggested above. Let's see how it behaves in our experiments now! :)

@stamatak
Copy link
Collaborator

stamatak commented Nov 25, 2020 via email

@lutteropp
Copy link
Owner Author

Turns out 10 random + 10 parsimony trees are a bit much... especially since the current NetRAX version is only single-threaded and not optimized for runtime performance yet (it wastes much time in branch-length optimization and in trying and rejecting arc insertion moves). Trying out what happens if I reduce them by a lot.

@stamatak
Copy link
Collaborator

stamatak commented Nov 30, 2020 via email

@lutteropp
Copy link
Owner Author

lutteropp commented Nov 30, 2020

If we don't care aabout runtime at all: Should I also switch to the slower network search algorithm? So far, I accepted the first move that improved the BIC score. But I already observed that I get a bit better results if I evaluate the entire 1-move-neighborhood and then accept the move that lead to the largest improvement in BIC score...

@stamatak
Copy link
Collaborator

stamatak commented Nov 30, 2020 via email

@lutteropp
Copy link
Owner Author

With the new wavesearch algorithm, I do not see any advantage in starting from multiple starting trees vs. starting from best raxml-ng tree.

@stamatak
Copy link
Collaborator

stamatak commented Jan 18, 2021 via email

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

No branches or pull requests

2 participants