Skip to content

Conversation

aabills
Copy link
Contributor

@aabills aabills commented Dec 18, 2024

Description

make sei work with particle size distributions

Fixes # (issue)

Type of change

Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #) - note reverse order of PR #s. If necessary, also add to the list of breaking changes.

  • New feature (non-breaking change which adds functionality)
  • Optimization (back-end change that speeds up the code)
  • Bug fix (non-breaking change which fixes an issue)

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 tests pass: $ python -m pytest (or $ nox -s tests)
  • The documentation builds: $ python -m pytest --doctest-plus src (or $ nox -s doctests)

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

Further checks:

  • Code is commented, particularly in hard-to-understand areas
  • Tests added that prove fix is effective or that feature works

Copy link

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

Copy link

codecov bot commented Dec 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.25%. Comparing base (a7253b8) to head (abb8697).
Report is 18 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #4693      +/-   ##
===========================================
+ Coverage    99.22%   99.25%   +0.02%     
===========================================
  Files          303      303              
  Lines        23070    23232     +162     
===========================================
+ Hits         22891    23058     +167     
+ Misses         179      174       -5     

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

@rtimms rtimms added the release blocker Issues that need to be addressed before the creation of a release label Jan 2, 2025
@aabills aabills marked this pull request as ready for review January 2, 2025 20:15
@aabills aabills enabled auto-merge (squash) January 2, 2025 20:15
Copy link
Contributor

@rtimms rtimms left a comment

Choose a reason for hiding this comment

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

thanks @aabills looks good to me, just some commented code that i think can be removed

@aabills aabills requested a review from rtimms January 3, 2025 15:44
@aabills aabills merged commit a5616c9 into pybamm-team:develop Jan 3, 2025
11 of 23 checks passed
@kratman
Copy link
Contributor

kratman commented Jan 3, 2025

@rtimms, @aabills The failures are probably all outside of this PR, but this got merged with failing tests.

I am working on the tests though

@aabills
Copy link
Contributor Author

aabills commented Jan 3, 2025

Should we revert?

Looking at it I don't think it will be this but I think we need to be careful with PR's that mess with submodels, they're just so darn finicky.

@aabills
Copy link
Contributor Author

aabills commented Jan 3, 2025

How did it get merged? I had it on auto-merge which should wait until checks pass right??

@kratman
Copy link
Contributor

kratman commented Jan 3, 2025

Yeah it is just an issue with auto-merge and our CI. Tests are not required yet

The test failures are string precision, so I am fixing them now. I don't see any failures from your changes, I double checked locally

@aabills
Copy link
Contributor Author

aabills commented Jan 3, 2025

If auto merge doesn't wait for tests I think we should not let people use it if that's possible

@kratman
Copy link
Contributor

kratman commented Jan 3, 2025

How did it get merged? I had it on auto-merge which should wait until checks pass right??

A lot of tests were not required on PyBaMM because it blocked bot created PRs from merging. I am starting to enforce these things

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release blocker Issues that need to be addressed before the creation of a release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants