| Version 14 (modified by mmamonski, 12 years ago) (diff) |
|---|
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
- MUSCLE configuration file
The MUSCLE runtime environment
Manual Execution
Tools and Services
QosCosGrid
QCG SimpleClient (Command-line)
- Home Page: http://www.qoscosgrid.org/trac/qcg-broker
QCG-Icon (Desktop application)
- Home Page: http://www.qoscosgrid.org/trac/qcg-icon
- User Manual: http://www.qoscosgrid.org/trac/qcg-icon/wiki/UserManulaEN
- Downloads: http://www.qoscosgrid.org/trac/qcg-icon/downloads
QCG AdvancedClient (Command-line, cross-cluster)
- MAPPER Seasonal School tutorial: http://www.mapper-project.eu/web/guest/qoscosgrid
MaMe, MAD, GridSpace?
- MAPPER Seasonal School tutorial: http://www.mapper-project.eu/web/guest/mad-mame-ew
