From: Hilmar L. <hl...@ne...> - 2010-11-01 03:30:44
|
On Oct 29, 2010, at 11:28 AM, William Piel wrote: > Why would this be the case for some trees but not others? I'm > guessing that instead of writing the newick on the fly, TreeBASE is > just grabbing the newick string from a stored version (table: > phylotree field: newickstring), and for some reason the stored > version is missing a semicolon (could be that the authors rerooted > the trees using our reroot tool, and our reroot tool has a bug > wherein it doesn't return a string with a semicolon -- hence why we > don't see this problem with all trees). Is that bug in the tracker? Is it difficult to fix? I.e., is this more complicated than finding the property setter and changing it so that it makes sure that there is always a semicolon at the end? -hilmar -- =========================================================== : Hilmar Lapp -:- Durham, NC -:- informatics.nescent.org : =========================================================== |