co-simulation
Here are 31 public repositories matching this topic...
When running parallel cases with the adapter, it just prints the number of interface nodes/faces on rank 0.
Hence, in larger
-
Updated
Jan 19, 2021 - C++
Currently PADE mix behaviours and protocols in a same file located in /pade/behaviours/protocols.py.
The idea is split behaviours and protocols in different files.
-
Updated
Jan 3, 2021 - C++
-
Updated
Jan 17, 2021 - C++
Once #61 is merged, serialization of the state functions should be tested using FMPy.
Maybe other stuff like the XML could be checked too.
-
Updated
Jan 16, 2021 - C++
-
Updated
Apr 13, 2020 - Ada
-
Updated
Apr 23, 2020 - C
-
Updated
Jun 17, 2019 - MATLAB
-
Updated
Jan 8, 2021 - Java
-
Updated
Jan 19, 2021 - C++
-
Updated
Apr 7, 2020 - HTML
-
Updated
Mar 27, 2020 - Python
-
Updated
Dec 13, 2018 - R
-
Updated
Nov 2, 2019 - C++
Describe the bug
The pi-exchange examples for different languages have differences in implementation that make some of them behave differently.
What is the expected behavior?
The pi-exchange federates written in different languages should be drop in replacements for each other when running examples. A pisender written in Python should work with a pireceiver written in C.
-
Updated
Jan 18, 2021 - C++
-
Updated
Aug 31, 2020 - CSS
-
Updated
Oct 29, 2020 - Python
-
Updated
Feb 14, 2019 - C++
-
Updated
Sep 17, 2019
-
Updated
Jan 14, 2021 - Kotlin
-
Updated
Sep 24, 2020 - Jupyter Notebook
-
Updated
Sep 17, 2019
-
Updated
Feb 15, 2020 - C
-
Updated
Jun 3, 2020 - C
The HELICS helper SetupFederate function currently creates a new federate each time it gets called. There should be a check to see if it has already been initialized before creating a new federate.
Improve this page
Add a description, image, and links to the co-simulation topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the co-simulation topic, visit your repo's landing page and select "manage topics."
We currently have a quite low test coverage in the PETSc radial-basis function mapping.
To be more precise, we only test the
Treepreallocation strategy. All remaining strategiesCompute,Save,Estimate,Noneare not tested at all.See the file on [CodeCov](https://codecov.io/gh/precice/prec