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

Show mutation split into homoplasic/unique/reversions also on terminal branches, not just internal ones #1752

Closed
corneliusroemer opened this issue Feb 16, 2024 · 16 comments · Fixed by #1753
Assignees
Labels
bug Something isn't working regression used to work but now doesn't

Comments

@corneliusroemer
Copy link
Member

Context

The Auspice feature to split mutations on branches into: homoplasic, unique, and reversions is very useful.

I noticed that this feature is not available for terminal branches. I can't see a reason why we shouldn't use the same feature for those branches, it's just as useful there.

See internal:
image

Vs. terminal:
image

@FedeGueli
Copy link

@corneliusroemer @ryhisner i think it was available until friday and now it changed and it has been removed.. if this is correct it is really a pain for us regularly checking singlets everyday maybe @ryhisner could add his point

@ryhisner
Copy link

ryhisner commented Feb 17, 2024

Terminal-branch mutations have always been visible. They just suddenly disappeared a day or two ago, and I REALLY miss them. It's hard to express just how much harder it is for me to do what I usually do without being able to view them. I've already wasted hours trying to sort out the mutations on long branches—something I used to be able to do quickly because shift-clicking the branch showed them immediately. And you could see a preview of the mutations just by hovering over the branch. If it was a relatively short terminal branch (<8 nuc mutations), you could see all the mutations this way.

@ryhisner
Copy link

I noticed that even the 21L tree has changed—you can no longer view the mutations on terminal branches by shift-clicking. Since there's no option to label branches with nucleotide mutations, it's extremely difficult to tell what synonymous (or non-synonymous ORF9b) mutations a terminal branch has.
image

@corneliusroemer
Copy link
Member Author

Thanks guys for suggesting this is a regression and that this happened recently.

It should be easy to revert for @jameshadfield - as it's not in the changelog I don't think it was intended.

@corneliusroemer corneliusroemer added bug Something isn't working regression used to work but now doesn't and removed enhancement New feature or request labels Feb 18, 2024
@FedeGueli
Copy link

Thanks guys for suggesting this is a regression and that this happened recently.

It should be easy to revert for @jameshadfield - as it's not in the changelog I don't think it was intended.

Thank you @corneliusroemer @jameshadfield

@corneliusroemer
Copy link
Member Author

I can confirm this is indeed a regression introduced between 2.51.0 and 2.52.0

This is 2.51.0 (npx [email protected]):
image

This is 2.52.0 (npx [email protected]):
image

@FedeGueli
Copy link

I can confirm this is indeed a regression introduced between 2.51.0 and 2.52.0

This is 2.51.0 (npx [email protected]): image

This is 2.52.0 (npx [email protected]): image

Thank you Cornelius as variant spotter that slows very much or disable our work efficiency . I know nextstrain is much more important than for our goals, but it is also a time where there aren't many people doing spotting systematically so it would be very important this will be fixed soon. thank you very much for your help.

@ryhisner
Copy link

Is a fix for this in the works? I'm trying workarounds to be able to figure out all the mutations on terminal branches, but they all require a lot more time.

@corneliusroemer
Copy link
Member Author

Using auspice/auspice.us 2.51.0 would work - though you'd have to host them locally AFAIK

@jameshadfield jameshadfield self-assigned this Feb 20, 2024
jameshadfield added a commit that referenced this issue Feb 20, 2024
Hovering on terminal branches incorrectly displayed tip-specific
information rather than branch-specific.

This bug was introduced in 86b8527 and
this commit reverts some of the changes introduced there.

Closes <#1752>
@jameshadfield
Copy link
Member

I've fixed this in PR #1753. I'll merge shortly and make a new Auspice release (2.52.1) and push this over to nextstrain.org. It should be available in the next few hours if all goes smoothly.

@FedeGueli
Copy link

I've fixed this in PR #1753. I'll merge shortly and make a new Auspice release (2.52.1) and push this over to nextstrain.org. It should be available in the next few hours if all goes smoothly.

Wow! great news thank you very much!

jameshadfield added a commit that referenced this issue Feb 20, 2024
Hovering on terminal branches incorrectly displayed tip-specific
information rather than branch-specific. This was first noticed in
<#1752> as the mutations are
summarised differently for branches vs nodes.

This bug was introduced in 86b8527 and
this commit reverts some of the changes introduced there.

Closes the original issue described in
<#1752>, but comments in
that issue also identified a separate bug related to the branch-click
modal.
jameshadfield added a commit that referenced this issue Feb 20, 2024
Clicking on terminal branches incorrectly behaved as if we had clicked
on the tip (the circle); the intended behaviour is for internal +
terminal branches to summarise the information the same way. This was
noticed in an issue comment
<#1752 (comment)>

The bug was introduced in f7e944d which
removed the ability to detect if a click occurred on a terminal node
(tip) or terminal branch.
jameshadfield added a commit that referenced this issue Feb 20, 2024
Hovering on terminal branches incorrectly displayed tip-specific
information rather than branch-specific. This was first noticed in
<#1752> as the mutations are
summarised differently for branches vs nodes.

This bug was introduced in 86b8527 and
this commit reverts some of the changes introduced there.

Closes the original issue described in
<#1752>, but comments in
that issue also identified a separate bug related to the branch-click
modal.
jameshadfield added a commit that referenced this issue Feb 20, 2024
Clicking on terminal branches incorrectly behaved as if we had clicked
on the tip (the circle); the intended behaviour is for internal +
terminal branches to summarise the information the same way. This was
noticed in an issue comment
<#1752 (comment)>

The bug was introduced in f7e944d which
removed the ability to detect if a click occurred on a terminal node
(tip) or terminal branch.
@jameshadfield
Copy link
Member

This issue has been closed because the PR has been merged, but the fix is yet to propagate to nextstrain.org. I'll write a message here when this happens.

For those interested in what happened, a recent PR (#1749) inadvertently removed the distinction between terminal branches and tips, which resulted in hovering or shift-clicking on terminal branches showing the wrong information. The intended behaviour is for hovering/shift-clicking on a branch to summarise the changes on that individual branch, whereas hovering/clicking on the tip should show information about the specific strain and (e.g.) collect all mutations between the tip and the tree root.

@jameshadfield
Copy link
Member

Changes released with Auspice 2.52.1, and nextstrain.org is updated. If you are still getting the old version (as shown in the page footer) please try refreshing the page holding the shift key.

@FedeGueli
Copy link

This issue has been closed because the PR has been merged, but the fix is yet to propagate to nextstrain.org. I'll write a message here when this happens.

For those interested in what happened, a recent PR (#1749) inadvertently removed the distinction between terminal branches and tips, which resulted in hovering or shift-clicking on terminal branches showing the wrong information. The intended behaviour is for hovering/shift-clicking on a branch to summarise the changes on that individual branch, whereas hovering/clicking on the tip should show information about the specific strain and (e.g.) collect all mutations between the tip and the tree root.

Thank you for the explanation and for the tip !

@ryhisner
Copy link

I've fixed this in PR #1753. I'll merge shortly and make a new Auspice release (2.52.1) and push this over to nextstrain.org. It should be available in the next few hours if all goes smoothly.

You guys are awesome! Thanks so much!

@corneliusroemer
Copy link
Member Author

Thanks @jameshadfield!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working regression used to work but now doesn't
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants