Documentation

The MUSCLE library contains the API and configuration necessary to implement a multiscale model. Neither depends on the hardware that the model will executed on, whether that is local, distributed, or through a job scheduler. When using the Java API, the principle is write once, use everywhere. For C/C++ code, recompilation might be necessary depending on the operating system and hardware, but if the submodel code is standards-compliant, this should not pose a problem.

The MUSCLE runtime environment is then able to run the multiscale model on different resources. The actual runtime location only depends on the command-line arguments given to MUSCLE, not on the implementation of the submodels.

The MUSCLE library

• Using the MUSCLE API
  • Java
  • C/C++
  • Fortran (Eric Lorenz)
  • Real-world example (Mohamed)
• MUSCLE configuration file

The MUSCLE runtime environment

Manual Execution

• Command-line execution

Tools and Services

• Remote Execution using QosCosGrid and GridSpace tools? (Mariusz)

Cross-cluster connectivity

• [Muscle Transport Overlay (MTO)]
• QCG-GridSpace integration (Mariusz)