Closed boopsboops closed 2 years ago
I don't think that rate scalers are the main problem here. Rather, you have a very low sites-to-taxa ratio (<0.1), which means the signal in the MSA is insufficient to resolve most branches. Hence, the extensive and time-consuming ML search as implemented and in raxml-ng (or old RAxML) is pretty pointless on this dataset.
We have discussed this topic multiple times on our RAxML google group, please search for keywords like "poor signal":
https://groups.google.com/g/raxml/search?q=poor%20signal
In short, your options are:
1) subsampling / clustering
2) use FastTree or parsimony
3) increase convergence epsilon, eg --lh-epsilon 10
Many apologies for confusing matters by mentioning why I was disabling the rate scalers, but thanks for the tips anyway!
The main purpose of the report was simply to highlight that I had turned the scalers off, but the software reports that they had been enabled regardless. This was a bit misleading, so I was concerned that it may be a bug.
ok I see, thanks for reporting!
I guess you are right and it's currently not possible to disable rate scalers for alignments with >2000 taxa. I will take care of this.
ok this should be fixed now, you can disable automatic rate scalers with --force model_rate_scalers
I'm trying to speed up raxml-ng by disabling the automatic per-rate scaling (it worked fine on old raxml which I think did not implement this feature?).
But with
--rate-scalers off --force
I get the following note:NOTE: Per-rate scalers were automatically enabled to prevent numerical issues on taxa-rich alignments. NOTE: You can use --force switch to skip this check and fall back to per-site scalers.
I'm assuming that it was disabled, but can't be sure, given this message?
Also, is it essential to have to use
--force
when combined with--rate-scalers off
, as I would rather not if possible?Full log below.
Cheers!