flow-over-plate-steady-state: Missing code_aster solid.export file
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 142
- Forks
- 167
- Avg merge
- 20h 24m
- Merged PRs (30d)
- 11
Description
This case currently suffers from a need for a manual, system-specific configuration step, which mainly sets a few paths and system variables. This step even depends on ASTK, a graphical tool.
In https://github.com/precice/vm/pull/20, I generated such a file on the fly, based on a similar approach in the systemtests repository. We could extract this and make a script to call in the beginning of run.sh.
We should then also update the documentation.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the flow-over-plate-steady-state case and its run.sh, then compare the generated code_aster solid.export approach in the referenced preCICE VM pull request with the similar systemtests approach. The work is done when the configuration file is generated without the manual ASTK step and the corresponding tutorial documentation is updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- documentation, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100