11 | | * Using the MUSCLE API |
12 | | * [[Java API|Java]] |
13 | | * [[C++ API|C/C++]] |
14 | | * [[Fortran API|Fortran]] |
| 11 | The MUSCLE library contains the means to write a submodel and couple it to other submodels. The design is such that submodels do not have to know with which other submodels they communicate, and the coupling is fixed later during configuration phase. The Java API is the most extensive, while the C++ and Fortran API provide the basic needed functionality. Also for performance reasons it may make sense to use the Java API. |
| 12 | |
| 13 | * [[Java API|Java]] |
| 14 | * [[C++ API|C/C++]] |
| 15 | * [[Fortran API|Fortran]] |
| 16 | |
| 17 | Configuration is done with a Ruby file with some MUSCLE-specific commands, here the coupling can be specified. |
| 18 | |