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

Modify K-Truss python to call C API connecting to legacy implementation #3754

Closed

Tracked by

ChuckHastings opened this issue Jul 27, 2023 · 0 comments · Fixed by #3843

Closed

Tracked by

Modify K-Truss python to call C API connecting to legacy implementation #3754

ChuckHastings opened this issue Jul 27, 2023 · 0 comments · Fixed by #3843

Collaborator

ChuckHastings commented Jul 27, 2023

Depends on #3753

Modify the python/cython code for K-Truss to use the new C API for connecting to the legacy implementation.

There's some ugly code in the legacy implementation that can be simplified and replaced by using this approach.

ChuckHastings mentioned this issue

Algorithm Migration - K-Truss #2167

Open

ChuckHastings mentioned this issue

Refactor legacy k truss #3843

Merged

rapids-bot bot closed this as completed in #3843

rapids-bot bot pushed a commit that referenced this issue


          Refactor legacy k truss (#3843)

eed1223

This PR refactor legacy k truss by leveraging the `C API`  instead of the `legacy:COO` graph. This also stands as a preliminary work to later provide a new implementation of `k_truss` matching the `C API`.

Closes #3753 
Closes #3754

Authors:
  - Joseph Nke (https://github.com/jnke2016)
  - Chuck Hastings (https://github.com/ChuckHastings)

Approvers:
  - Chuck Hastings (https://github.com/ChuckHastings)
  - Brad Rees (https://github.com/BradReesWork)
  - Don Acosta (https://github.com/acostadon)

URL: #3843

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment