Container Operations

cardiacmodelling/ap-nimbus-app-manager

  1. Docker runs kick_off.sh when the image is run.

  2. kick_off.sh firstly sets off convert.sh watching file creation/modification in a run directory.

    • If a file creation/modification event of interest takes place (as a result of an ApPredict invocation) the changed file is read from the run directory (probably a simulation-specific ApPredict_output/ directory), processed, and written (usually in JSON format) to a simulation-specific res directory.

  3. kick_off.sh secondly sets off server.js listening on whichever host/port (e.g. 0.0.0.0:8080).

  4. app-manager (or rather server.js,) receives a POST request from client-direct to run ApPredict

  5. server.js invokes run_me.sh

  6. run_me.sh starts ApPredict which writes output to the run directory.

  7. convert.sh sees results appearing in the run directory and, on events of interest, processes the content and writes it to the res directory.

  8. server.js will be awaiting polling calls from client-direct requesting the results data and responding with content from files in the res directory if/when available.