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 InVEST for numpy2 #1641

Closed
phargogh opened this issue Oct 8, 2024 · 0 comments · Fixed by #1642
Closed

Update InVEST for numpy2 #1641

phargogh opened this issue Oct 8, 2024 · 0 comments · Fixed by #1642
Assignees
Labels
in progress This issue is actively being worked on task Something needs to be done
Milestone

Comments

@phargogh
Copy link
Member

phargogh commented Oct 8, 2024

Now that pygeoprocessing 2.4.5 is released, we should update InVEST to handle numpy 2.

@phargogh phargogh added task Something needs to be done in progress This issue is actively being worked on labels Oct 8, 2024
@phargogh phargogh self-assigned this Oct 8, 2024
phargogh added a commit to phargogh/invest that referenced this issue Oct 10, 2024
phargogh added a commit to phargogh/invest that referenced this issue Oct 10, 2024
phargogh added a commit to phargogh/invest that referenced this issue Oct 10, 2024
phargogh added a commit to phargogh/invest that referenced this issue Oct 10, 2024
phargogh added a commit to phargogh/invest that referenced this issue Oct 10, 2024
phargogh added a commit to phargogh/invest that referenced this issue Oct 11, 2024
@dcdenu4 dcdenu4 added this to the 3.14.3 milestone Oct 15, 2024
phargogh added a commit to phargogh/invest that referenced this issue Oct 15, 2024
phargogh added a commit to phargogh/invest that referenced this issue Oct 15, 2024
An RST error in a footnote in Wave Energy was breaking the binary builds
in the main InVEST repository.  This is now addressed. RE:natcap#1641
phargogh added a commit to phargogh/invest that referenced this issue Oct 15, 2024
phargogh added a commit to phargogh/invest that referenced this issue Oct 16, 2024
phargogh added a commit to phargogh/invest that referenced this issue Oct 16, 2024
phargogh added a commit to phargogh/invest that referenced this issue Oct 16, 2024
The numpy2 update was producing slightly different numerical outputs,
but also we weren't asserting that they were numerically close, just
that they had the same number of digits after the decimal ... which
wasn't working well because most of these values were large.

RE:natcap#1641
phargogh added a commit to phargogh/invest that referenced this issue Oct 16, 2024
This is part of the numpy2 migration. RE:natcap#1641
phargogh added a commit to phargogh/invest that referenced this issue Oct 16, 2024
phargogh added a commit to phargogh/invest that referenced this issue Oct 16, 2024
phargogh added a commit to phargogh/invest that referenced this issue Oct 16, 2024
phargogh added a commit to phargogh/invest that referenced this issue Oct 16, 2024
phargogh added a commit to phargogh/invest that referenced this issue Oct 16, 2024
phargogh added a commit to phargogh/invest that referenced this issue Oct 16, 2024
phargogh added a commit to phargogh/invest that referenced this issue Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in progress This issue is actively being worked on task Something needs to be done
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants