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
{{ message }}
This repository has been archived by the owner on Sep 12, 2018. It is now read-only.
At present, this would only be necessary for GML files, I think?
Anyway, this would -- for GML files -- result in us ignoring the orientation of nodes and creating duplicate nodes for each (e.g. a node with id 1 would result in two nodes being created, a forward-oriented node with id 1 and a reverse-oriented node with id -1). Similarly, edges would also result in two edges being created; A -> B also implies -B -> -A.
The text was updated successfully, but these errors were encountered:
Made a bit of progress on this. Since I'd like to work on other collate-specific changes for now, I'm storing the affected .py files here so I can do a git reset and make different changes. These changes (+ more) can be integrated later. gml_unoriented_code.zip
At present, this would only be necessary for GML files, I think?
Anyway, this would -- for GML files -- result in us ignoring the orientation of nodes and creating duplicate nodes for each (e.g. a node with
id 1
would result in two nodes being created, a forward-oriented node withid 1
and a reverse-oriented node withid -1
). Similarly, edges would also result in two edges being created;A -> B
also implies-B -> -A
.The text was updated successfully, but these errors were encountered: