tutorials
tutorials copied to clipboard
precice
ASTE Turbine Tutorial
ASTE was lack of a tutorial in tutorials.
This PR suggests a tutorial that shows the usage of ASTE tools: mesh partitioner, mesh joiner, calculator, beside ASTE itself.
The tutorial uses the turbine meshes from the preCICE repository. This way it provides a variety of meshes for different trials.
What is our strategy to explain users how to reproduce their setup with ASTE? Do we want to do this in this tutorial as well, in another tutorial, or simply "only" in the documentation of ASTE?
What is our strategy to explain users how to reproduce their setup with ASTE? Do we want to do this in this tutorial as well, in another tutorial, or simply "only" in the documentation of ASTE?
Not completely sure at the moment, but I guess it fits best into the replay mode. We will have another tutorial for this anyway.
What is our strategy to explain to users how to reproduce their setup with ASTE? Do we want to do this in this tutorial as well, in another tutorial, or simply "only" in the documentation of ASTE?
I think this tutorial just shows simply how users evaluate mapping of preCICE on their meshes, like the section on the reference paper. There would be another tutorial for reproducing their setup in ASTE (vector replay mode?).
Just to avoid confusion, "replay mode" is yet another use case. I see the following three use case of ASTE:
- To evaluate/study mapping methods on "artificial" geometries/meshes. This is what the tutorial here does.
- Reproducing a specific mapping setup of a coupled case. For example: case crashes since mapping fails. User exports both meshes and values and imports in ASTE. Tries to reproduce in ASTE. Then, we could debug for them or they could test different basis functions etc.
- Replay mode. Replace a participant in a coupled setup with ASTE. One then always gets a uni-directional coupling. This is useful for debugging, for developing new adapters, but also for efficiency reasons (explicit instead of implicit coupling etc).
@uekerman considering the use-cases: would it make sense to create an aste directory on the top level and the three use-cases as subdirectories?
@kursatyurt You can ignore the check-scripts CI (please run shellcheck locally). However, the markdown file still has some issues.
@uekerman considering the use-cases: would it make sense to create an
astedirectory on the top level and the three use-cases as subdirectories?
I am not yet sure about this, but I guess this is also a future problem. Let's first finish this one.
For the "test your mapping" use case, I am not sure whether we need a testcase (tutorial) at all. Maybe a step-by-step description in the docs would be better for this.
For the replay mode, I could imagine a:
- perpendicular-flap-one-way
- fluid-aste
- solid-dealii
- solid ...
Or we just tell the user to copy the solid folders.
This pull request has been mentioned on preCICE Forum on Discourse. There might be relevant details there:
https://precice.discourse.group/t/mapping-issue-forces-mapped-from-fluid-mesh-to-solid-mesh-look-weird-how-to-debug/1106/9
