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
there exists a Mastodon project (opening will fail fidning image data, please open with DUMMY instead) in which the TrackScheme will not render a complete tree, will leave blank regions instead -- it happens at various scales, see below. The project above will open windows, in particular a TS window with a view set to demonstrate this effect.
The first view:
Resizing the window doesn't necessarily help:
Fails unf. even on a different scale:
(when zoom-in vertcially a bit, it get's better-- also a proof that the data is/should be there)
The text was updated successfully, but these errors were encountered:
I can reproduce the bug.
The data is super corrupted: the tables tell me there are no edges in the graph. So I don't know what is displayed in TrackScheme.
I suspect that the data was not generated in Mastodon, correct?
It is possible that edges are inserted in the graph with erroneous orientation. Mastodon can only deal with edges that go forward in time (t of target > t of source). Edges that would violate this could create a crash like the one we see.
Hi,
there exists a Mastodon project (opening will fail fidning image data, please open with DUMMY instead) in which the TrackScheme will not render a complete tree, will leave blank regions instead -- it happens at various scales, see below. The project above will open windows, in particular a TS window with a view set to demonstrate this effect.
The first view:
Resizing the window doesn't necessarily help:
Fails unf. even on a different scale:
(when zoom-in vertcially a bit, it get's better-- also a proof that the data is/should be there)
The text was updated successfully, but these errors were encountered: