-
-
Notifications
You must be signed in to change notification settings - Fork 115
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
Growing mesh case #600
base: develop
Are you sure you want to change the base?
Growing mesh case #600
Conversation
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.
I know that this is still a draft, but I had a quick look anyway, so I left some comments that I know are probably already on your list.
- A who runs first | ||
- B who runs second |
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.
We so far avoid calling participants and data generic names, but try to relate to a specific physical domain and application use case. This is currently only partially described in the naming conventions.
Of course, this is fine for now (and fine for an integration test), but before merging, we should better have more descriptive names.
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.
They both represent the same mesh and don't model any physical behaviour.
Not sure what we would name them.
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.
There is a physical motivation for this scenario. We could borrow names there?
This PR adds a growing mesh case.
Two solvers define the same mesh, which grows at given points in time.
Inspiration for this case is the formation of additional residue layers on the floor of an ocean over time.
@MakisH is this how you envision the separate solver folder to work?
Checklist:
changelog-entries/<PRnumber>.md
.