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

BUG[Visual]: Mutations at beginning and end of mut view are invisible due to insufficient padding #712

Open
corneliusroemer opened this issue Jan 28, 2022 · 1 comment
Labels
needs triage Mark for review and label assignment package: nextclade_web t:bug Type: bug, error, something isn't working

Comments

@corneliusroemer
Copy link
Member

When there are mutations in the first or last 0.1% of the genome (e.g. pos 10 in SC2), they are not as visible as they should be because they crash against the edges of the mutation view.

Padding should be increased to make such mutations properly visible.

Consider for example sequence OU187687 in the example dataset, it has lots of mutations in the range 4-30, but these are hardly visible.
image

image

@corneliusroemer corneliusroemer added t:bug Type: bug, error, something isn't working needs triage Mark for review and label assignment package: nextclade_web labels Jan 28, 2022
ivan-aksamentov added a commit that referenced this issue Jan 31, 2022
Addresses some of the concerns for #712

Here I shifted sequence (peptide) view's SVG viewBox 1/n of nucleotide (peptide) width to the right. This allows for the markers close to the begging or end of the view to be visible.

This is required after adjustments made for centering markers in 
#638 #644 #709
@ivan-aksamentov
Copy link
Member

ivan-aksamentov commented Jan 31, 2022

I tried to improve it a little in #713, so that at least one could distinguish single mutations at the positions near 1.

I am not sure more padding would help. Padding will only squeeze the available space making the mutations overlap more.

In the particular case on the screenshot, the mutations are packed tightly, and overlap, and also obscured by the gray marker of Ns, which makes them even harder to read.

I cannot think immediately about what can be done further here, but glad to hear ideas.

The #295 is probably the ultimate solution here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage Mark for review and label assignment package: nextclade_web t:bug Type: bug, error, something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants