-
-
Notifications
You must be signed in to change notification settings - Fork 563
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
Allow for cylindrical and spherical shell domains #3237
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## develop #3237 +/- ##
========================================
Coverage 99.71% 99.71%
========================================
Files 248 248
Lines 18861 18861
========================================
Hits 18807 18807
Misses 54 54
☔ View full report in Codecov by Sentry. |
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
…aMM into issue-3115-shell-domains
This is now ready to review |
spatial_methods = {"domain": pybamm.FiniteVolume()} | ||
disc = pybamm.Discretisation(mesh, spatial_methods) | ||
disc.process_model(model) | ||
solver = pybamm.CasadiAlgebraicSolver() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a bit strange to have a solver inside this test. Not the end of the world but would be better without, so that this is really a unit test (and not dependent on the solver). Is there another way to test the same thing?
It's an integration test though, isn't it fine to have a solver there? |
Ah yes true, then it's fine |
Description
Now we only throw and error for non zero-Neumann bcs if the boundary is at
r = 0
, which means cylindrical and spherical shells can be solved with any boundary condition. Also added some integration tests to check it works.Fixes #3115
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.
Key checklist:
$ 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)$ python run-tests.py --all
(or$ nox -s tests
)$ python run-tests.py --doctest
(or$ nox -s doctests
)You can run integration tests, unit tests, and doctests together at once, using
$ python run-tests.py --quick
(or$ nox -s quick
).Further checks: