Sign In

Communications of the ACM

ACM TechNews

Adding MUSCLE to Multiscale Simulations


View as: Print Mobile App Share: Send by email Share on reddit Share on StumbleUpon Share on Hacker News Share on Tweeter Share on Facebook
The layered design of MUSCLE 2, separating implementation, coupling, and execution.

The Multiscale Coupling Library and Environment 2 project was launched recently to implement and execute multiscale models with feedback loops.

Credit: HPC Wire

In 2010, researchers from different disciplines started the European e-Infrastructure MAPPER project to serve as a general multiscale computing platform. Recently, the Multiscale Coupling Library and Environment 2 (MUSCLE 2) project was launched to implement and execute multiscale models with feedback loops, known as cyclic coupling topologies.

MUSCLE is a domain-independent approach and it runs on several supercomputers and clusters in Europe, as well as the Amazon cloud infrastructure. It consists of a library, scripted coupling, and a runtime environment. MUSCLE runs reach submodel in a separate process, giving it an inherently multiscale parallelism. MUSCLE 2 separates the submodel code from the couple code, which enables users to change the coupling topology without recompiling or redeploying code. In addition, the coupling code is independent from the resources that the simulation will eventually run on, enabling users to access more resources and to take advantage of architectures that are optimal for each of the models involved.

MUSCLE 2 has the option of using the MPWide library, a high-performance communication library that can run directly as a supercomputer job with few dependencies.

From HPC Wire
View Full Article

 

Abstracts Copyright © 2013 Information Inc., Bethesda, Maryland, USA


 

No entries found