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

Update count_if_e, transform_reduce_e, and transform_e to support edge masking #4001

Merged
merged 17 commits into from
Nov 30, 2023

Conversation

seunghwak
Copy link
Contributor

Update transform_e to support graphs with edge masking. This is necessary for K-truss.

@seunghwak seunghwak added feature request New feature or request non-breaking Non-breaking change labels Nov 15, 2023
@seunghwak seunghwak added this to the 24.02 milestone Nov 15, 2023
@seunghwak
Copy link
Contributor Author

@jnke2016 FYI

@seunghwak seunghwak changed the title Update transform_e to support edge masking Update count_if_e, transform_reduce_e, and transform_e to support edge masking Nov 17, 2023
@seunghwak seunghwak marked this pull request as ready for review November 17, 2023 01:27
@seunghwak seunghwak requested a review from a team as a code owner November 17, 2023 01:28
@seunghwak seunghwak self-assigned this Nov 17, 2023
@naimnv
Copy link
Contributor

naimnv commented Nov 18, 2023

/ok to test

@seunghwak seunghwak changed the base branch from branch-23.12 to branch-24.02 November 29, 2023 18:17
edge_mask_view_ = edge_mask_view;
}

void clear_edge_mask() { edge_mask_view_ = std::nullopt; }
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have no preference. Is there a reason to prefer this syntax over edge_mask_view_.reset()?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume they are same. I guess mainly personal preference.

According to
https://stackoverflow.com/questions/47441623/how-to-assign-nothing-to-stdoptionalt

It seems like = {} or = std::nullopt were initially recommended and .reset() is added later.

Copy link
Contributor Author

@seunghwak seunghwak Nov 30, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But consistency matters, so if we are mainly using .reset() elsewhere in our codebase, I am OK to make a change.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That was my assessment. A quick check in the code, I see a few calls to .reset() and a bunch more assignments to std::nullopt.

I'm going to merge this PR. We should probably pick a way and create a PR to update things to be consistent.

@ChuckHastings
Copy link
Collaborator

/merge

@rapids-bot rapids-bot bot merged commit 5eaae7d into rapidsai:branch-24.02 Nov 30, 2023
73 checks passed
@seunghwak seunghwak deleted the fea_transform_e_mask branch May 22, 2024 17:37
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 non-breaking Non-breaking change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants