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

Make the size of the splice junction tracks proportionate to counts > 50 #1015

Closed
hbeale opened this issue Aug 10, 2021 · 11 comments
Closed
Milestone

Comments

@hbeale
Copy link

hbeale commented Aug 10, 2021

Currently the height of the arc and its thickness are proportional to the depth of read coverage up to 50 reads. I would like to be able to change 50 to an arbitrary number. Currently I have one arc representing 813 reads and another representing 62 reads, and they look the same.

image

Tagging @maximilianh who suggested I submit this request.

@zukailiu
Copy link

zukailiu commented Sep 9, 2022

Hi hbeale,

Did you solve this problem at the end? I came across exactly the same issue with you.

Thanks,
Zukai

@jrobinso jrobinso added this to the 2.14.2 milestone Sep 9, 2022
@jrobinso
Copy link
Contributor

jrobinso commented Sep 9, 2022

I'll look into this for the next point release.

@jrobinso
Copy link
Contributor

@hbeale @zukailiu Did either of you try setting the track to "Autoscale"? That works for me, although there is a refresh problem (autoscale doesn't take effect until a repaint is forced, e.g. by dragging).

@jrobinso
Copy link
Contributor

I'll add a menu item to set an explicit value, that should be there in any event, but autoscale works in the meantime.

@hbeale
Copy link
Author

hbeale commented Oct 24, 2022 via email

@jrobinso
Copy link
Contributor

@hbeale I might need a test set to reproduce that, it works for me with all my test datasets. For example, load the attached (after unzipping as a session) and select "Autoscale" for the Liver track, then drag to force refresh.
rnaSeq.xml.zip

@zukailiu
Copy link

@jrobinso I tried the 'autoscale' on my IGV 2.12.3 and it worked!! Thank you so much!

@hbeale
Copy link
Author

hbeale commented Oct 24, 2022

Interesting! I get similar results with your test data as I do with my data. It looks like the data is scaled even above 50 reads within a track (or what do you call it, probably not a track, but the distinct rows within a track that appear when you set the junction track to "expanded"), but not across "tracks".

Here's before
before autoscale

Here's after:
Untitled 3

After, in the top "track", the middle-ish junction representing 1495 reads is now taller than one to the left in the same horizontal line with 693 reads, but both junction arcs are smaller than the one representing 40 reads in the "track" below it.

@jrobinso
Copy link
Contributor

OK, I will look into that, I had not looked at "expanded" mode. The rows are just rows, tracks in this case would be liver and heart.

@jrobinso
Copy link
Contributor

Yes I see what's happening, its autoscaling each row, which of course is not what we want.

jrobinso added a commit that referenced this issue Oct 25, 2022
* Autoscale correctly in expanded mode
* Refresh view on scaling state change
* Add menu item to explicitly set depth
* Save autoscale & maxDepth state to session
@jrobinso
Copy link
Contributor

This is released in 2.15.1

jrobinso added a commit that referenced this issue Dec 14, 2022
* Autoscale correctly in expanded mode
* Refresh view on scaling state change
* Add menu item to explicitly set depth
* Save autoscale & maxDepth state to session
jrobinso added a commit that referenced this issue Dec 15, 2022
* Autoscale correctly in expanded mode
* Refresh view on scaling state change
* Add menu item to explicitly set depth
* Save autoscale & maxDepth state to session
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants