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

Obtain a sub-optimum tree with LH cutoff? #44

Closed
oushujun opened this issue May 7, 2018 · 5 comments
Closed

Obtain a sub-optimum tree with LH cutoff? #44

oushujun opened this issue May 7, 2018 · 5 comments
Labels

Comments

@oushujun
Copy link

oushujun commented May 7, 2018

Hello,

Thanks for developing and maintaining this fascinating method.

I want to search an ML tree in my population data. I know it will be very difficult to converge into a bifurcating tree, but I only want to learn about large branches currently, and not hoping to spend a large chunk of time to "optimize" tips. I notice the likelihood value increased quickly and keep increasing just a slight bit (but taking a couple hours each round). In this case, can I stop the run and get the current tree? Or is that any way to set a likelihood cutoff to stop the run? I notice the "--spr-cutoff" parameter but not quite understand what it means and how to set a proper value.

Below is the command I used.

raxml-ng --msa Chr1.imputed.fa --model GTR+G --threads 50 --seed 12315

Any suggestions are welcome. Thanks ahead!

Shujun

@amkozlov
Copy link
Owner

amkozlov commented May 8, 2018

Hi Shujun,

the relevant option for this would be --lh-epsilon which defines the likelihood cutoff to terminate SPR cycles.

--spr-cutoff is a different cutoff which is used in the subtree traversal heuristic, described in section 3.2 of this paper here:

https://sco.h-its.org/exelixis/pubs/VLSI2007.pdf

Hope this helps,
Alexey

@oushujun
Copy link
Author

oushujun commented May 8, 2018

Hi Alexey,

Thank you for your clarification. I have problems to understand the concept of LH epsilon. I see the cutoff of this parameter is 0.1, is that mean once the LH difference between this round and the previous round is less than 0.1, the ML search will stop?

To implement this parameter, can I just add it to my previous command and run it in the same folder to harvest the checkpoints that raxml-ng stored and run without this parameter?

Thanks,
Shujun

@stamatak
Copy link
Collaborator

stamatak commented May 8, 2018 via email

@oushujun
Copy link
Author

oushujun commented May 8, 2018 via email

@amkozlov
Copy link
Owner

amkozlov commented May 8, 2018

Thank you for your clarification. I have problems to understand the concept of LH epsilon. I see the cutoff of this parameter is 0.1, is that mean once the LH difference between this round and the previous round is less than 0.1, the ML search will stop?

that's exactly how it works. Please note, that lh-epsilon applies to model and branch length optimization as well. So you might want to run --evaluate command on a resulting topology with a lower lh-epsilon to refine model/brlen estimates.

To implement this parameter, can I just add it to my previous command and run it in the same folder to harvest the checkpoints that raxml-ng stored and run without this parameter?

yes, this should work.

Best,
Alexey

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants