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 - include user defined colours if set #630

Closed
8 tasks done
shawnlaffan opened this issue Dec 2, 2016 · 1 comment
Closed
8 tasks done

Tree exports - include user defined colours if set #630

shawnlaffan opened this issue Dec 2, 2016 · 1 comment
Assignees
Milestone

Comments

@shawnlaffan
Copy link
Owner

shawnlaffan commented Dec 2, 2016

If a user has assigned colours themselves (e.g. under the processes implemented in #600) then we should allow them to be exported.

This is simple for tabular trees, but nexus and newick need a bit of extra handling as we need to search for an ancestor that has a colour set.

Related to #503

Collated to do list:

  • Add tests for colour export functionality before merge
  • Option to export colours could probably be in the export metadata as a boolean.
  • Exported bootstrap blocks need to have a leading ampersand, and color keyword needs to be preceded by an exclamation mark, e.g. [&!color="#00000"] instead of ["colour"="#000000"]. Otherwise FigTree does not recognise the colours.
  • Quotes appear optional but have no apparent effect. Poss remove them if simple?
  • Needs to also apply to tabular tree. Looks like metadata just needs to be updated.
  • [[ WONTFIX - importing such data is sufficiently complex to warrant its own issue. nexus files - import annotations in node comment blocks #657 ]] Add roundtrip tests. SWL to generate some simple data using FigTree (which is the target package for colours). Currently get number format errors when reading an exported file.
  • Bootstrap block needs to go between label and number. "fred[&!color=red]:5"
  • disable for newick - figtree seems not to support it (only Nexus)
@shawnlaffan shawnlaffan added this to the Release_2.0 milestone Dec 2, 2016
LukedFitzpatrick added a commit that referenced this issue Dec 22, 2016
LukedFitzpatrick added a commit that referenced this issue Dec 22, 2016
LukedFitzpatrick added a commit that referenced this issue Dec 23, 2016
LukedFitzpatrick added a commit that referenced this issue Jan 1, 2017
LukedFitzpatrick added a commit that referenced this issue Jan 2, 2017
@LukedFitzpatrick
Copy link
Collaborator

LukedFitzpatrick commented Jan 2, 2017

  • Add tests for colour export functionality before merge

LukedFitzpatrick added a commit that referenced this issue Jan 18, 2017
Will eventually be added to each tree node, used initially to hold user defined colours.

Updates #630
LukedFitzpatrick added a commit that referenced this issue Jan 19, 2017
LukedFitzpatrick added a commit that referenced this issue Jan 19, 2017
LukedFitzpatrick added a commit that referenced this issue Jan 19, 2017
LukedFitzpatrick added a commit that referenced this issue Jan 20, 2017
LukedFitzpatrick added a commit that referenced this issue Jan 20, 2017
LukedFitzpatrick added a commit that referenced this issue Jan 20, 2017
LukedFitzpatrick added a commit that referenced this issue Jan 20, 2017
LukedFitzpatrick added a commit that referenced this issue Jan 22, 2017
LukedFitzpatrick added a commit that referenced this issue Jan 22, 2017
LukedFitzpatrick added a commit that referenced this issue Jan 23, 2017
…to the bootstrap block before export.

Updates #630
shawnlaffan added a commit that referenced this issue Feb 3, 2017
shawnlaffan added a commit that referenced this issue Feb 3, 2017
LukedFitzpatrick added a commit that referenced this issue Feb 13, 2017
… Also update tests for bootstrap block to reflect change.

Updates #630
LukedFitzpatrick added a commit that referenced this issue Feb 14, 2017
…weaks to bootstrap block encoding/decoding.

Updates #630
shawnlaffan added a commit that referenced this issue Feb 16, 2017
Also some style changes and minor inefficiencies.

Updates #630
shawnlaffan added a commit that referenced this issue Feb 17, 2017
shawnlaffan added a commit that referenced this issue Feb 21, 2017
Also remove exclusions blocks

Updates #630
shawnlaffan added a commit that referenced this issue Feb 21, 2017
The subhash makes the logic cleaner when wrangling colours and the like.
It also means we can have a label if appropriate.

Updates #630
shawnlaffan added a commit that referenced this issue Feb 21, 2017
This currently fails as the parser assumes json compatible strings
(which is a false assumption on my part)

[ci skip]

Updates #630
shawnlaffan added a commit that referenced this issue Feb 21, 2017
shawnlaffan added a commit that referenced this issue Feb 21, 2017
Might make a difference when parsing very large trees

Updates #630
shawnlaffan added a commit that referenced this issue Feb 21, 2017
shawnlaffan added a commit that referenced this issue Feb 21, 2017
They can be worked on under issue #657

Updates #630
shawnlaffan added a commit that referenced this issue Feb 21, 2017
It can be dealt with under #657

Updates #630
shawnlaffan added a commit that referenced this issue Feb 21, 2017
Otherwise they were appearing in the GUI.

Minor tweaks to methods otherwise.

Updates #630
shawnlaffan added a commit that referenced this issue Feb 21, 2017
shawnlaffan added a commit that referenced this issue Mar 3, 2017
This was missed in the updates to issue #630
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

2 participants