You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! When plotting arcs for BEDPE file format, if the first coordinate comes after the second coordinate (i.e. start_x > start_y), the arc is not drawn. I have fixed this issue by swapping the first coordinate with the second coordinate (see figure where the first track after the gene track shows some features, the second track is how it looks after my fix, and the third track is before the fix where some arcs are missing).
Is there some other more elegant fixes?
By the way, I am using coolbox version 0.3.3. I quickly checked the source of the latest version (i.e. 0.3.8) but I did not immediately find any indication that this is addressed in the latest version (but of course I may have missed it 🙂).
Thank you in advance for your consideration and response! 🙂
The text was updated successfully, but these errors were encountered:
When drawing, the diameter of arc is determined by pos2 - pos1 and becomes negative when plot the non-upper-triangular record(start_x > start_y).
A more elegant solution is to add a judgment to fetch_plot_data that converts all records to the upper-triangular form(start_x < start_y). fetch_plot_data is this function:
Hi! When plotting arcs for
BEDPE
file format, if the first coordinate comes after the second coordinate (i.e.start_x > start_y
), the arc is not drawn. I have fixed this issue by swapping the first coordinate with the second coordinate (see figure where the first track after the gene track shows some features, the second track is how it looks after my fix, and the third track is before the fix where some arcs are missing).Is there some other more elegant fixes?
By the way, I am using
coolbox
version0.3.3
. I quickly checked the source of the latest version (i.e.0.3.8
) but I did not immediately find any indication that this is addressed in the latest version (but of course I may have missed it 🙂).Thank you in advance for your consideration and response! 🙂
The text was updated successfully, but these errors were encountered: