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

Add support for numpy 2.0.0 #599

Merged
merged 4 commits into from
Jun 26, 2024
Merged

Add support for numpy 2.0.0 #599

merged 4 commits into from
Jun 26, 2024

Conversation

R-Palazzo
Copy link
Contributor

CU-86b0y0zqa
Resolve #593

@R-Palazzo R-Palazzo self-assigned this Jun 24, 2024
@R-Palazzo R-Palazzo requested a review from a team as a code owner June 24, 2024 12:11
@sdv-team
Copy link
Collaborator

@R-Palazzo R-Palazzo removed the request for review from a team June 24, 2024 12:11
@@ -17,7 +18,7 @@ def test_end_to_end(self):
result = column_pair_trends.get_score(real_data, synthetic_data, metadata)

# Assert
assert result == 0.45654629583521095
assert np.isclose(result, 0.45654629583521095, atol=1e-8)
Copy link
Contributor

Choose a reason for hiding this comment

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

what causes the inconsistency in values now?

Copy link
Contributor

Choose a reason for hiding this comment

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

Seems with scipy 1.14, there is another decimal of accuracy added

@R-Palazzo R-Palazzo merged commit 8e79aa2 into main Jun 26, 2024
47 checks passed
@R-Palazzo R-Palazzo deleted the issue-593-numpy2.0 branch June 26, 2024 15:24
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.

Add support for numpy 2.0.0
5 participants