precice / precice/code_aster-adapter
Wrong order of writing data
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 16
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
These should be reverted:
But we have a deeper issue here: Since we use a list (self.writeDataNames[0]) and not a dictionary, it is easy to mess up the order. These are set here:
Reported by a user in the forum: https://precice.discourse.group/t/unexpectedly-high-interface-temperature-in-openfoam-code-aster-heat-transfer-coupling/2377/4
Contributor guide
No contributing guide indexed for this repository
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 in cht/adapter.py at lines 182-192 and 244-245, then compare the configured data-name order with the linked forum report. Confirm the intended write order before making the focused correction. Done means the adapter writes the coupled quantities in the expected order.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100