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
You are correct in thinking this doesn't look good to the user. For clarification, this is a symptom of a desired feature which was added here: graph-genome/component_segmentation#7 where large components get cut in half to fit in multiple files. We're going to need some way of detecting if a split is extraneous.
If the component.last_bin == chunk.last_bin and departures.length == 0 and next_component.arrivals.length == 0
then it's an unnecessary split on chunk boundary and should be rendered as continuous,
maybe even change the PangenomeSchematic.js representation to be one long component.
If a single component is split into chunks, there are meaningless connectors at the chunk boundaries. Example covid-19:
corresponding bin2file:
the chunk boundary in the middle (pan coord 2260) is unnecessary
The text was updated successfully, but these errors were encountered: