Skip to content
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

Rename source and sink to empty set #658

Open
ugurdogrusoz opened this issue Apr 11, 2021 · 5 comments
Open

Rename source and sink to empty set #658

ugurdogrusoz opened this issue Apr 11, 2021 · 5 comments

Comments

@ugurdogrusoz
Copy link
Contributor

ugurdogrusoz commented Apr 11, 2021

The latest SBGN PD names these nodes "Empty set", so let's rename them. Let's review other node (glyphs) and edge (archs) types as well.

msalihaltun added a commit to iVis-at-Bilkent/sbgnviz.js that referenced this issue Jun 1, 2021
msalihaltun added a commit to iVis-at-Bilkent/chise.js that referenced this issue Jun 1, 2021
@msalihaltun
Copy link
Contributor

The related tests failed because the link in the test points to master version of one of our files which had the source and sink to empty set change.

@ugurdogrusoz
Copy link
Contributor Author

Let's find out whether "source and sink" should be used in SBGNML's when reading and writing with the UI using "empty set".

@msalihaltun msalihaltun mentioned this issue Jun 2, 2021
2 tasks
@ugurdogrusoz
Copy link
Contributor Author

ugurdogrusoz commented Jun 2, 2021

Let's accept both "source and sink", "empty set", and "emptyset" when reading. For writing, let's keep using "source and sink" since SBGNML is still outdated in this respect. The UI should refer to the node with the new name "empty set" though.

@ugurdogrusoz
Copy link
Contributor Author

This map with a single process passes the checks in public Newt but not the daily build. Could this be related to not renaming / using the new node class name?
Screenshot 2021-06-07 111403

@ugurdogrusoz
Copy link
Contributor Author

Since SBGNML, other tools, validator, etc. might be referring to the old name, let's keep this issue open for a while.

@ugurdogrusoz ugurdogrusoz removed their assignment Jun 7, 2021
@hasanbalci hasanbalci reopened this Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants