-
Notifications
You must be signed in to change notification settings - Fork 16
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
Introduce Cell types #99
Comments
I don't really have particularly strong feelings about how exactly we do things in the I'm presuming based on our conversation earlier:
|
I would try to stay as close as possible to the current interface. I don't know exactly what changes are needed until I work on this. |
I'm ok with this, provided that we have enough sugar that I don't have to go down to the cell datastructure when I just want to get the cell vectors out of a system. Because that's one thing I really dislike about the packages that abstract away the vectors in a cell structure is that this makes working with them quite inconvenient at times. |
|
I am okay with this, I don't have strong feelings about how |
This is a proposal based on the zoom call on 15 / 5 / 2024, that replaces #97 .
(1) remove
bounding_box
andboundary_conditions
from the system and replace it with a cell object that encodes the same information.(2) Implement a type
Cell
orParaCell
that contains fieldscell_vectors
andpbc
(true / false)(3) At the same time I would like to replace the
AbstractVector
withVector
in order to remove that type instability as well.It would look something like this:
I think this will do two things:
FlexibleSystem
type stableI'll start on the PR if I get tentative agreement from a few people.
The text was updated successfully, but these errors were encountered: