-
Notifications
You must be signed in to change notification settings - Fork 63
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
Create method to collapse introns in LGV #557
Comments
Implementation idea so far is to make the ruler of a displayed region just be its locstring label or similar thing, if the displayed region is narrow enough on the screen that there isn't room for meaningful ruler ticks in its ruler. |
Somewhat related #1084 |
I retitled this to be a more generic intron collapsing issue I made a demo where I manually stitched together some displayedRegions from the set of exons from one transcript in a gene (with 100bp on each side) https://jbrowse.org/code/jb2/main/?config=test_data%2Fconfig_demo.json&session=local-YuIbRHX9y It looks ok, it is pretty moderate in terms of total number of displayedRegions though so if there are e.g. 30-100 exons it would probably start looking messier and create ellided blocks, but that might be ok since you can zoom in on them |
script to stitch it together run in devtools after clicking a feature
copy output to test.json, then make nodejs script
then copy output to clipboard
then in devtools
|
From meeting:
|
This feature may benefit from being implemented alongside the canvas feature renderer. The floating labels don't work well on with the SvgFeatureRenderer with the many discontinous regions and the Svg exports are messy too. Each could potentially be fixed within the current SvgFeatureRenderer framework, but i do think a new feature renderer is a good investment |
Collapsed introns or collapsed other regions would result results in a big change in coordinates. The refName labeling would could be modified to allow it to display a more complete description of the displayed region instead of just the refName.
The text was updated successfully, but these errors were encountered: