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

Different nodes naming conventions in the output formats may cause confusion when user may want to relay on them as input #544

Closed
shmfr opened this issue Jul 3, 2023 · 1 comment

Comments

@shmfr
Copy link
Collaborator

shmfr commented Jul 3, 2023

There may be several places when users need to refer to node names as input (like in the subset or explainability features).
In those cases, users may intuitively conclude that node names for inputs are the same as those displayed in the output.

  1. We may want to align the same nodes naming conventions for all output formats.
  2. Meantime, all features that have node names input, should specify the exact format of the node naming expected for that feature.
@shmfr shmfr added the enhancement New feature or request label Jul 3, 2023
@zivnevo
Copy link
Member

zivnevo commented Jul 18, 2024

Moved to NP-Guard repo. See here

@zivnevo zivnevo closed this as not planned Won't fix, can't repro, duplicate, stale Jul 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants