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 realize this is something that most users would have rarely encounter, since most of them would certainly know how their newick string looks like before trying to read it into R. And It wouldn't make any sense trying to read a phylogeny with one tip only.
However, I discovered this behaviour when I was trying to read a bunch of newick strings I have not looked before into R. They were generated with the rphylotastic package, which basically takes a vector of taxa and subsets trees from databases by matching those taxa. Sometime only one taxon is matched in the source tree, so the subset tree looks like the following: "Ursus_americanus;"
Then, trying to read this into a phylo object with read.newick(text = "Ursus_americanus;" freezes R.
Not a big deal, just thought it might be useful to share that this is happening.
The text was updated successfully, but these errors were encountered:
LunaSare
changed the title
read.newick freezes when reading newick text with one string only
read.newick freezes when reading newick text with one tip only
Oct 18, 2018
I realize this is something that most users would have rarely encounter, since most of them would certainly know how their newick string looks like before trying to read it into R. And It wouldn't make any sense trying to read a phylogeny with one tip only.
However, I discovered this behaviour when I was trying to read a bunch of newick strings I have not looked before into R. They were generated with the rphylotastic package, which basically takes a vector of taxa and subsets trees from databases by matching those taxa. Sometime only one taxon is matched in the source tree, so the subset tree looks like the following:
"Ursus_americanus;"
Then, trying to read this into a phylo object with
read.newick(text = "Ursus_americanus;"
freezes R.Not a big deal, just thought it might be useful to share that this is happening.
The text was updated successfully, but these errors were encountered: