-
-
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
Cleaning up geometries and meshes #1029
Comments
Think this sounds great and I can't think of any reasons not to do it off the top of my head. I think the only time the submesh list is used is to get its length and as you say we should be able to get this from auxiliary domains. The keys "primary" etc. are used in |
Yeah, the discretisation would have to read |
The geometry and meshes are quite messy and hard to understand right now. Some ideas for cleaning them up:
auxiliary_domains
instead.auxiliary_domains
more, we don't need to distinguish between the geometries so much. The only distinction required will be 0-1-2D current collectors. So the messyGeometry
class can just be replaced by a single functionThis will be challenging to implement but should be doable. But it's possible that I'm missing something and this will be fundamentally too difficult.
The text was updated successfully, but these errors were encountered: