FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Add micro-dumux-surrogate participant to two-scale heat conduction by IshaanDesai · Pull Request #684 · precice/tutorials · GitHub

Add micro-dumux-surrogate participant to two-scale heat conduction - #684

Draft
IshaanDesai wants to merge 21 commits into
precice:developfrom
IshaanDesai:micro-dumux-surrogate
Draft

Add micro-dumux-surrogate participant to two-scale heat conduction#684
IshaanDesai wants to merge 21 commits into
precice:developfrom
IshaanDesai:micro-dumux-surrogate

Conversation

IshaanDesai commented Dec 1, 2025
edited
Loading

Copy link
Copy Markdown
Member

This PR adds a surrogate variant to the existing participant micro-dumux, called the micro-dumux-surrogate. The surrogate is created using the tool BayesValidRox. The surrogate is built using PCE (Polynomial Chaos Expansion). This participant is built to highlight the functionality of model adaptivity in the Micro Manager: precice/micro-manager#198

Checklist:

  • I added a summary of any user-facing changes (compared to the last release) in the changelog-entries/<PRnumber>.md.
  • I will remember to squash-and-merge, providing a useful summary of the changes of this PR.

IshaanDesai self-assigned this Dec 1, 2025
IshaanDesai marked this pull request as ready for review December 28, 2025 10:31

MakisH left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

I have not yet tried to run it, but here are some first, easy-to-address comments.

Comment thread changelog-entries/684.md
@@ -0,0 +1 @@
- Added PCE-base surrogate for micro-dumux in two-scale heat conduction [#684](https://github.com/precice/tutorials/pull/684)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

The README.md file of the tutorial also needs to document this alternative and what kind of surrogate it is.

In other cases (e.g., perpendicular-flap), we had participants named -fake? Is this case doing something similar?

Comment on lines +4 to +7
python3 -m venv .venv
. .venv/bin/activate

pip install -r requirements.txt

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

See #680 for some updates (or directly copy from other run.sh in the same tutorial).

Copy link
Copy Markdown
Member Author

Thanks for the comments. I am still thinking about how to structure the folders so that only the full-order model and the surrogate model are exposed to the user. By adding a surrogate model at the micro scale, we have a unique scenario in which the Micro Manager runs not one but two solvers simultaneously. Technically, the solvers are not participants of the coupling; the Micro Manager is. But having the solvers in individual folders makes sense because it highlights which physics is being used and which software is being run.

IshaanDesai marked this pull request as draft January 23, 2026 09:54

uekerman commented Feb 3, 2026

Copy link
Copy Markdown
Member

Thanks for the comments. I am still thinking about how to structure the folders so that only the full-order model and the surrogate model are exposed to the user. By adding a surrogate model at the micro scale, we have a unique scenario in which the Micro Manager runs not one but two solvers simultaneously. Technically, the solvers are not participants of the coupling; the Micro Manager is. But having the solvers in individual folders makes sense because it highlights which physics is being used and which software is being run.

Makes sense to me. The only real alternative would be a subfolder micro or micro-manager and in there multiple folders with the different models.

MakisH left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Since there is now activity on this PR, notice some recent changes in the rest of the tutorials, regarding:

  • venv
  • requirements.txt
  • metadata.yaml

You could also directly try to update the tests.yaml to add a test case.

Don't forget to update the tutorial README.md file to add the cases to the overview.

@@ -0,0 +1,3 @@
numpy
bayesvalidrox
micro-manager-precice

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Recent update: Please also add pyprecice here, even if implied by the micro-manager-precice.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Choose a reason Spam Abuse Off Topic Outdated Duplicate Resolved Low Quality

Recent: This will need some updates regarding the venv setup. See how the other tutorials now (consistently) handle that.

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants


Back | FazBrowse Home | New Git URL