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

Adds quality_opposites parameter to mutually_exclusive() #270

Merged
merged 1 commit into from
Nov 10, 2022

Conversation

johnbradley
Copy link
Contributor

@johnbradley johnbradley commented Nov 3, 2022

Adds an optional quality_opposites parameter to mutually_exclusive().
This parameter requires a dataframe with "quality.a" and "quality.b" columns that contain opposite IRIs.

Fixes #240

@johnbradley johnbradley force-pushed the 240-opposite-qualities branch 4 times, most recently from cea86c0 to cd0bb14 Compare November 3, 2022 18:35
@johnbradley johnbradley marked this pull request as ready for review November 3, 2022 19:19
@johnbradley johnbradley requested a review from hlapp November 3, 2022 19:19
@hlapp hlapp added this to the pre-2023-TraitFest milestone Nov 4, 2022
Copy link
Member

@hlapp hlapp left a comment

Choose a reason for hiding this comment

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

Looks good. I made a few minor changes to the parameter documentation. One thing I'm wondering is whether we couldn't put a few IRI pairs into a CSV in the examples directory, read that in as part of the example 4 and then simply rerun the same thing as in the previous example as a contrast. But we can make that a separate issue, with perhaps lower priority than this one.

@johnbradley
Copy link
Contributor Author

I created issue #271 to improve the example.

@johnbradley
Copy link
Contributor Author

@hlapp Should I combine these two commits into one before merging into master?

@hlapp
Copy link
Member

hlapp commented Nov 10, 2022

@hlapp Should I combine these two commits into one before merging into master?

Yes that's fine!

Adds an optional quality_opposites parameter to mutually_exclusive().
This parameter requires a dataframe with "quality.a" and "quality.b"
columns that contain opposite IRIs.

Fixes #240

Co-authored-by: Hilmar Lapp <hlapp@drycafe.net>
@johnbradley johnbradley force-pushed the 240-opposite-qualities branch from 64e460a to 3159d17 Compare November 10, 2022 16:08
@johnbradley johnbradley merged commit 3159d17 into master Nov 10, 2022
@github-pages github-pages bot temporarily deployed to github-pages November 10, 2022 16:20 Inactive
@johnbradley johnbradley deleted the 240-opposite-qualities branch June 20, 2023 15:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow supplying opposite qualities for use in mutual exclusion
2 participants