You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure as to what "nm" (or the referenced vector) is referring to here. I read in the bootstrap-labeled tree using read.tree() and the dates file as a named vector (converting dates to decimals using lubridate::decimal_date()), as usual, but I have never received this error before. Any help would be appreciated. issue.zip
The text was updated successfully, but these errors were encountered:
The tree might be a bit too much for treedater. I see more than 30k tips. I haven't been able to reproduce the error since it can't allocate the memory on my laptop. There are more scalable methods like least-squares-dating, or if there is a logical way to partition the data you can try that.
On Apr 27, 2021, at 6:56 PM, Erik Volz ***@***.***> wrote:
The tree might be a bit too much for treedater. I see more than 30k tips. I haven't been able to reproduce the error since it can't allocate the memory on my laptop. There are more scalable methods like least-squares-dating, or if there is a logical way to partition the data you can try that.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
I am not sure as to what "nm" (or the referenced vector) is referring to here. I read in the bootstrap-labeled tree using read.tree() and the dates file as a named vector (converting dates to decimals using lubridate::decimal_date()), as usual, but I have never received this error before. Any help would be appreciated.
issue.zip
The text was updated successfully, but these errors were encountered: