Skip to content

Updates for numpy 2 compatibility#372

Merged
BradyPlanden merged 4 commits into
developfrom
367-numpy-updates
Jun 24, 2024
Merged

Updates for numpy 2 compatibility#372
BradyPlanden merged 4 commits into
developfrom
367-numpy-updates

Conversation

@NicolaCourtier

Copy link
Copy Markdown
Member

Description

Updates are required to use Numpy 2.0. As for Pints (see their PR 1531), we just need to replace np.array(x, copy=False) with np.asarray(x).

Issue reference

Fixes #367.

Review

Before you mark your PR as ready for review, please ensure that you've considered the following:

  • Updated the CHANGELOG.md in reverse chronological order (newest at the top) with a concise description of the changes, including the PR number.
  • Noted any breaking changes, including details on how it might impact existing functionality.

Type of change

  • New Feature: A non-breaking change that adds new functionality.
  • Optimization: A code change that improves performance.
  • Examples: A change to existing or additional examples.
  • Bug Fix: A non-breaking change that addresses an issue.
  • Documentation: Updates to documentation or new documentation for new features.
  • Refactoring: Non-functional changes that improve the codebase.
  • Style: Non-functional changes related to code style (formatting, naming, etc).
  • Testing: Additional tests to improve coverage or confirm functionality.
  • Other: (Insert description of change)

Key checklist:

  • No style issues: $ pre-commit run (or $ nox -s pre-commit) (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
  • All unit tests pass: $ nox -s tests
  • The documentation builds: $ nox -s doctest

You can run integration tests, unit tests, and doctests together at once, using $ nox -s quick.

Further checks:

  • Code is well-commented, especially in complex or unclear areas.
  • Added tests that prove my fix is effective or that my feature works.
  • Checked that coverage remains or improves, and added tests if necessary to maintain or increase coverage.

Thank you for contributing to our project! Your efforts help us to deliver great software.

@NicolaCourtier NicolaCourtier linked an issue Jun 18, 2024 that may be closed by this pull request
@NicolaCourtier

Copy link
Copy Markdown
Member Author

The Pints's optimisers CMAES and NelderMead appear to be the only ones affected. Once these are updated by Pints PR 1531, our integration tests and examples should pass again.

@NicolaCourtier NicolaCourtier marked this pull request as ready for review June 18, 2024 15:50
@NicolaCourtier

Copy link
Copy Markdown
Member Author

We can merge this PR ahead of the Pints's updates.

@codecov

codecov Bot commented Jun 18, 2024

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.47%. Comparing base (c8db9f5) to head (e637110).
Report is 752 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #372      +/-   ##
===========================================
+ Coverage    97.29%   97.47%   +0.18%     
===========================================
  Files           46       42       -4     
  Lines         2805     2418     -387     
===========================================
- Hits          2729     2357     -372     
+ Misses          76       61      -15     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@BradyPlanden BradyPlanden left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Looks good, thanks for the changes @NicolaCourtier.

@BradyPlanden BradyPlanden merged commit 4fe242c into develop Jun 24, 2024
@BradyPlanden BradyPlanden deleted the 367-numpy-updates branch June 24, 2024 15:30
@MichaelClerx

Copy link
Copy Markdown

PINTS is fixed now!

@bessman bessman mentioned this pull request Nov 13, 2025
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.

[Bug]: Breaking numpy 2.0 release

3 participants