ApPredict
containers¶
Note
Docker containers cardiacmodelling/appredict-chaste-libs
, cardiacmodelling/appredict-no-emulators
and cardiacmodelling/appredict-with-emulators
are derived from
source code in https://github.com/CardiacModelling/appredict-docker (or via the appredict-docker
submodule of
https://github.com/CardiacModelling/ap-nimbus).
See also
ApPredict containers for visual representation.
appredict-chaste-libs¶
cardiacmodelling/appredict-chaste-libs
is a container which contains all of ApPredict
’s library dependencies.
- Conventionally
cardiacmodelling/appredict-chaste-libs
isn’t “installed” as it’s just a Debian Docker image with all ofApPredict
’s dependency packages installed, and as such just the foundation forcardiacmodelling/appredict-no-emulators
to build on.- Historically (before
cardiacmodelling/appredict-chaste-libs:0.0.5
) this container’s contents were mostly built from source packages of dependent libraries.- There’s no “running” of
cardiacmodelling/appredict-chaste-libs
.
appredict-no-emulators¶
cardiacmodelling/appredict-no-emulators
is a container which has cardiacmodelling/appredict-chaste-libs
as its
foundation, and it is the minimum necessary to run ApPredict
simulations via
CLI.
appredict-with-emulators¶
cardiacmodelling/appredict-with-emulators
is a container which has cardiacmodelling/appredict-no-emulators
as its
foundation, with all the Lookup Tables (https://cardiac.nottingham.ac.uk/lookup_tables/appredict_lookup_table_manifest.txt)
available at build time pre-installed to avoid the need to dynamically download them.