multiphysics
Here are 38 public repositories matching this topic...
-
Updated
Apr 6, 2022 - C++
-
Updated
Apr 6, 2022 - Fortran
Describe your setup
Current preCICE develop version
Describe the problem
When we allowed multiple read mappings to the same mesh in #849, we forgot to update the following assignment (which still assumes that there is only one read mapping to a certain mesh).
I am using SimPEG.Utils.download for gpgLabs. The download messages are distracting in notebooks, so I wanted to suppress them. The option is controlled by "verbose=false", but it does not stop writing "Downloading ... Saved to:.." message.
Can verbose=false swtich kill all the print output?
![image](https://user-images.githubusercontent.com/5066933/28143500-b531e30c-671a-11e7-85d2-4d62d23d26a
-
Updated
Apr 5, 2022 - C++
-
Updated
Apr 5, 2022 - C++
-
Updated
Jan 19, 2022 - C++
-
Updated
Jan 3, 2022 - MATLAB
-
Updated
Mar 1, 2022 - Python
-
Updated
Apr 4, 2022 - C
-
Updated
Mar 29, 2022 - C++
-
Updated
Mar 31, 2022 - Python
Looking at the FluidSolver.py, I noticed that a few things are a bit uncommon in the time loop:
It looks like the checkpointing assumes that the solver time step is equal to the coupling time window. More specifically, whenever preCICE does not ask the solv
-
Updated
Oct 2, 2021 - C++
-
Updated
Jan 30, 2020 - Python
-
Updated
Feb 11, 2022 - Python
-
Updated
Jan 3, 2022 - MATLAB
-
Updated
Mar 21, 2022 - Python
-
Updated
Feb 27, 2022 - Julia
-
Updated
Apr 6, 2022 - Julia
-
Updated
Aug 5, 2018 - C++
-
Updated
Apr 6, 2022 - GLSL
-
Updated
Mar 28, 2022 - Python
-
Updated
Apr 5, 2022 - Jupyter Notebook
-
Updated
Apr 5, 2022 - TeX
-
Updated
Feb 8, 2022 - C++
-
Updated
Mar 17, 2022 - C++
-
Updated
Nov 6, 2021 - C++
-
Updated
Dec 12, 2017 - Python
Improve this page
Add a description, image, and links to the multiphysics topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the multiphysics topic, visit your repo's landing page and select "manage topics."
Reason
There is no reason to call the "higher level" app the "master"... better terminology is the "parent" app. We should change everything in the MultiApp system that mentions "master" including the documentation.
Design
See above.
Impact
May modify some documentation - but shouldn't do much more than that.