The computation didn't finished, thus, I canceled it. The "time" call outputs:
real 919m58.089s
user 0m5.080s
sys 0m3.236s
With other branch lengths in the tree (e.g. all set to 0.1) and the same genomes there is no problem and the computation finished after some hours. The smallest branch length in the displayed tree is 0.0001. I allready heard about a problem with too small branch lengths, thus, I increased them. But in the displayed tree the biggest lengths is 0.378917857 and it's maybe not good to increase it much more.
Is my presumption right? What is your experience in that case? What can you recommend?
It would be good, if progressiveCactus at least throw an error in that case.
Hello,
I updated progressiveCactus this week and started the program with the following tree:
(((((X199X:0.227695833,X249X:0.000304166667):0.0349386364,X23X:0.101061364):0.0332929687,(X45X:0.0136055556,X48X:0.00449444444):0.00913203125):0.020315625,X35X:0.063446875):0.0144236979,((X30X:0.052584375,X74X:0.083415625):0.0100923828,(X160X:0.00307096354,((((X172X:0.0001,X1X:0.378917857):0.0922365385,X36X:0.398263462):0.05896875,X10X:0.0001):0.0233650391,(X243X:0.00334242188,X246X:0.00272757812):0.000837460937):0.00550488281):0.029068099):0.0117294922,X270X:0.0319638021);
The computation didn't finished, thus, I canceled it. The "time" call outputs: real 919m58.089s user 0m5.080s sys 0m3.236s
With other branch lengths in the tree (e.g. all set to 0.1) and the same genomes there is no problem and the computation finished after some hours. The smallest branch length in the displayed tree is 0.0001. I allready heard about a problem with too small branch lengths, thus, I increased them. But in the displayed tree the biggest lengths is 0.378917857 and it's maybe not good to increase it much more.
Is my presumption right? What is your experience in that case? What can you recommend? It would be good, if progressiveCactus at least throw an error in that case.