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

[FEA]: Add kwarg to functions to allow users to skip input verification #70

Open
2 tasks done
rlratzel opened this issue Jan 29, 2025 · 0 comments
Open
2 tasks done
Assignees
Labels
feature request New feature or request

Comments

@rlratzel
Copy link
Contributor

Is this a new feature, an improvement, or a change to existing functionality?

New Feature

How would you describe the priority of this feature request

Low (would be nice)

Please provide a clear description of problem this feature solves

From #62 (comment)

Adding a kwarg to allow users to skip input verification checks could improve performance for users that have known safe/sanitized input. The option would be opt-in, since skipping this check and potentially allowing invalid inputs is not drop-in compatible with NX because invalid inputs could either be silently accepted in unexpected ways, or raise exceptions different than NX's.

Another approach could be to add a nx-cugraph config option that applies to all nx-cugraph functions, since it seems likely that a user would want this behavior for their entire workflow rather than just specific functions. Yet another approach could be to have both config and kwarg support.

Describe your ideal solution

example:

similarities = nx.jaccard_coefficient(G, [(0, 1), (1, 2)], backend_kwargs={"cugraph": {"check_ebunch": False}})

Describe any alternatives you have considered

No response

Additional context

No response

Code of Conduct

  • I agree to follow nx-cugraph's Code of Conduct
  • I have searched the open feature requests and have found no duplicates for this feature request
@rlratzel rlratzel added the feature request New feature or request label Jan 29, 2025
@rlratzel rlratzel self-assigned this Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant