-
-
Notifications
You must be signed in to change notification settings - Fork 132
Channel transport with particles #700
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
base: develop
Are you sure you want to change the base?
Conversation
|
The We need to rethink how we are distributing solver codes that are built directly in the build tree of the respective solver. A good place to document this then would be the adapter software engineering page. |
|
|
||
| Particle participant: | ||
|
|
||
| * MercuryDPM |
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.
More information needed here (I know you know, just for the overview).
|  |
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.
|  | |
|  |
and image missing
| ## Setup | ||
|
|
||
| We model a two-dimensional incompressible fluid flowing through a channel with an obstacle. The fluid problem is coupled to a particle participant for particle tracing. Similar to the transport problem (see the [channel-transport tutorial](tutorials-channel-transport.html)), particles are arranged in a circular blob close to the inflow. | ||
|
|
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.
You could add here the very nice picture from the PR description.
The open question is a bit how to handle the MercuryDPM participant, as the coupled code is entirely compiled with MerucryDPM
https://bitbucket.org/mercurydpm/mercurydpm/pull-requests/266
In principle, using
and copying the executable compiled in
./build/./Drivers/PreCICE/ChannelTransportis sufficient. Afterwards simply execute the case.Checklist:
changelog-entries/<PRnumber>.md.