-
-
Notifications
You must be signed in to change notification settings - Fork 568
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
Issue 609 broadcast to cell edges #891
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #891 +/- ##
===========================================
+ Coverage 97.79% 97.79% +<.01%
===========================================
Files 210 207 -3
Lines 10603 10631 +28
===========================================
+ Hits 10369 10397 +28
Misses 234 234
Continue to review full report at Codecov.
|
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.
looks good thanks!
@@ -901,6 +901,9 @@ def x_average(symbol): | |||
:class:`Symbol` | |||
the new averaged symbol | |||
""" | |||
# Can't take average if the symbol evaluates on edges |
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.
why can't we average on edges? is it just that it isn't implemented? (if so, no need to do this now. it can be a separate issue if/when we need it)
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.
No reason why we can't in theory. I'm not sure what the proper implementation would be in a finite volume context though? For nodes it's clearly just sum all the values, but for edges I don't know what it should be: maybe N[-1] - N[0]
?
Description
Add
BroadcastToEdge
object and edit fluxes in relevant submodels to use this.Also edited the particle submodels, hopefully a bit clearer now.
Fixes #609
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:
$ flake8
$ python run-tests.py --unit
$ cd docs
and then$ make clean; make html
You can run all three at once, using
$ python run-tests.py --quick
.Further checks: