Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tree exports - nexus - add lists within the comments blocks #503

Closed
4 tasks done
GoogleCodeExporter opened this issue Mar 27, 2015 · 4 comments
Closed
4 tasks done

Comments

@GoogleCodeExporter
Copy link

GoogleCodeExporter commented Mar 27, 2015

It would be useful to put list results within comments blocks within the
trees. These can be done as key=value pairs.

These can then be plotted/analysed etc using software which supports their use.

Original issue reported on code.google.com by shawnlaffan on 11 Sep 2014 at 6:44

To do:

  • add option to nexus export
  • update format to match spec
  • ensure we don't leave lists behind (clean up the comment block data as needed)
  • ensure colours are exported with lists if requested
@shawnlaffan
Copy link
Owner

See FigTree example data for a template.

@shawnlaffan shawnlaffan changed the title Tree exports - nexus and newick - add lists within the bootstrap block Tree exports - nexus and newick - add lists within the comments blocks Feb 21, 2017
@shawnlaffan shawnlaffan changed the title Tree exports - nexus and newick - add lists within the comments blocks Tree exports - nexus - add lists within the comments blocks Feb 21, 2017
@shawnlaffan
Copy link
Owner

shawnlaffan commented Feb 21, 2017

Most of the changes to implement this were done under the branch for issue #630

shawnlaffan added a commit that referenced this issue Aug 22, 2017
Tests need to be updated since the format of the lists
has changed to work with FigTree (which presumably follows
the spec).

Updates #503
shawnlaffan added a commit that referenced this issue Aug 22, 2017
shawnlaffan added a commit that referenced this issue Aug 22, 2017
shawnlaffan added a commit that referenced this issue Aug 22, 2017
shawnlaffan added a commit that referenced this issue Aug 22, 2017
This is handled inside the called sub

Updates #503
shawnlaffan added a commit that referenced this issue Aug 22, 2017
@shawnlaffan
Copy link
Owner

Mark as fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants