Details
-
Type:
Bug
-
Status: Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 2.8, 2.9, 2.10.0, 2.11.0, 2.11.5.0, 2.11.5.1
-
Component/s: colourschemes, renderer
-
Labels:None
Description
Per-group clustal shading should always reflect conservation in the local group. This works when the group is first created, but whenever a global colourscheme update triggers a refresh a group's colourscheme, the clustal shading shown for a group is based on the consensus profile for the alignment rather than just the sequences in the group.
Workarounds are unreliable - sometimes clicking in the group will change the clustal shading to reflect the local consensus, but the next global refresh will revert.
Noticed whilst testing [~geoff.barton]'s annexins exercise which includes explicit steps to give the system "a kick" by changing the colourscheme to another, then back to clustal, in order to workaround this problem.
Specific instances where this is seen:
Workarounds are unreliable - sometimes clicking in the group will change the clustal shading to reflect the local consensus, but the next global refresh will revert.
Noticed whilst testing [~geoff.barton]'s annexins exercise which includes explicit steps to give the system "a kick" by changing the colourscheme to another, then back to clustal, in order to workaround this problem.
Specific instances where this is seen:
Attachments
Issue Links
- mentioned on
(7 mentioned on)