Networking activities. We create and maintain a stable management of the project, with strong internal and external communication and development of realistic plans for uptake and sustainability of MAPPER results during and after the lifetime of the project. We focus on targeted dissemination actions and a foresight study addressed to policy makers on the ICT concepts and technologies that facilitate multi-scale modelling approaches on large e-Infrastructures. We distinguish two layers of services constituting the MAPPER environment. Users and applications communicate with services belonging to the interoperability layer, an abstract layer to grid resources managed by different middleware stacks. The interoperability services are responsible for providing concurrent access to resources controlled by different services synchronizing and orchestrating the execution of applications in the grid. Multi-scale loosely and tightly coupled simulations are controlled by a broker and underlying computing access services developed in the FP6-ICT QosCosGrid project3. The broker is integrated with underlying middleware and its scheduling and co-allocation algorithms are tuned for specific needs of multi-scale applications. Many of the services that we wish to use have been developed individually and do not necessarily interoperate. We ensure that these services do talk to each other where appropriate. We start working on application deployment as early as possible in the project. We therefore adopt a twin track approach in our service development activities. The fast track adapts, integrates and deploys a minimal set of infrastructure components to enable coupling of multi- scale applications. The deep track will do so for the higher level services required to realise the full and integrated MAPPER infrastructure, which will enable the coupling and launching of multi-scale component codes. MAPPER services evolve on the basis of a regular cycle of top- down and bottom- up analysis of existing e-infrastructure, MAPPER building blocks as well as new requirements defined by our multi-scale user communities.
Appears in 3 contracts
Sources: Memorandum of Understanding, Memorandum of Understanding, Memorandum of Understanding