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.

Sign up for GitHub

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

Jump to bottom

HypernetX specific warnings should be in hypernetx classes #131

Open
drj11 opened this issue Dec 6, 2023 · 0 comments
Open

HypernetX specific warnings should be in hypernetx classes #131

drj11 opened this issue Dec 6, 2023 · 0 comments
Labels
backlog joss

Comments

@drj11
Copy link

drj11 commented Dec 6, 2023

Is your feature request related to a problem? Please describe.

As per Tutorial 1, calling edge_distance (H.edge_distance(4, 6, s=2)) can generate a warning.

A mild improvement would be to make the warning a specific class in hypernetx (as the Exceptions are); this gives finer control over warnings to users.

(i do not require this to be fixed for my JOSS review)
@bonicim bonicim added the joss label Dec 6, 2023
@bonicim bonicim self-assigned this Jan 10, 2024
@bonicim bonicim removed their assignment Feb 16, 2024
bonicim added a commit that referenced this issue Feb 28, 2024
@bonicim
Pull request #131: Hotfix/HYP-362
440a9ba 
Merge in HYP/hypernetx from hotfix/HYP-362 to develop

* commit '1fd8505a5c63822408d1c0d07d6afc75e9b1891b':
  bump: version 2.1.1 → 2.1.2
  Run linter on LICENSE.rst
  updated License
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
backlog joss
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@drj11 @bonicim