Welcome to AP-Nimbus’s documentation¶
|Created:||Jul 23, 2020|
This activity represents the next step in the development of the original AP-Portal work – towards a container-based / cloud solution.
- Unlike AP-Portal, this work includes the installation of
ApPredict, the cardiac simulation software.
- Also unlike
AP-Portal, this work, by nature of containerisation, means that
AP-Nimbuswork does not embody a single application, it is instead a collection of containers where each can operate in isolation, e.g. as a standalone
Singularitycontainer, or alternatively, orchestrated in a microservice architecture (e.g.
This documentation predominantly covers
Docker container environments, however
it has been relatively straightforward to create Singularity
singularity build app-manager.img docker://cardiacmodelling/ap-nimbus-app-manager:0.0.10)
and use those .
For the role each of the containers has in the overall
AP-Nimbus activity please
see Activity Overview.
ApPredict is the underlying cardiac simulation engine.
Building or installing
ApPredict is a complex and time-consuming
process and by distributing in container form it’s possible to have it installed
in a fraction of the time .
cardiacmodelling/ap-nimbus-app-manager does not currently handle either of PKPD or
Dynamic CellML operations. These activities can only take place when
using the CLI
The following illustrates a microservice-based solution to potentially running many
It is equally feasible to run as .. :
docker run ..a single
cardiacmodelling/ap-nimbus-app-managercontainer and call it with HTTP
docker run ..either of the
cardiacmodelling/appredict-no-emulatorscontainers directly from a CLI to run their internal
For instructions on how to run containers, see the more detailed section on Running.
|||So long as there’s a container runtime, e.g. |