This is a tree created out of a 16S NGS run (one sample). The rather unique feature about this type of data is that you'd expect a lot of 0-length branches when duplicate reads appear in the sample, so my first guess would either be something wrong with the tree file itself or a recursion depth issue in Dendroscope/java.
Here's the tree that breaks Dendroscope (it just hangs after told to open the file):
cuke16s.zip
And here's another file (exactly the same sample, number of nodes/edges/etc) that works perfectly! --
cuke16s-working.zip
RAM is no issue as Dendroscope was told it could use up to 32GB of RAM during installation and doesn't use a fraction of that to render the working version of the tree.
This is a tree created out of a 16S NGS run (one sample). The rather unique feature about this type of data is that you'd expect a lot of 0-length branches when duplicate reads appear in the sample, so my first guess would either be something wrong with the tree file itself or a recursion depth issue in Dendroscope/java.
Here's the tree that breaks Dendroscope (it just hangs after told to open the file): cuke16s.zip
And here's another file (exactly the same sample, number of nodes/edges/etc) that works perfectly! -- cuke16s-working.zip
RAM is no issue as Dendroscope was told it could use up to 32GB of RAM during installation and doesn't use a fraction of that to render the working version of the tree.