34  Browser Playground

Interactive browser playground for exploring IPPL features.

The playground keeps the manual page open while compilation and execution happen in a local Docker container. The first example is deliberately small: edit a Hello IPPL program, compile it, run it with MPI, inspect stdout, and edit again.

34.1 Build the local runner

Build the runner image once from the public IPPL source tree:

git clone --depth 1 --branch ippl-container https://github.com/IPPL-framework/ippl.git
cd ippl
docker build -t ippl-runner:local -f tools/browser-runner/Dockerfile .

34.2 Start the local runner

Start the runner on the local machine:

docker run --rm -p 127.0.0.1:5050:5050 ippl-runner:local

The runner prints a token:

IPPL runner token: ...

Paste that token into the field below. The token prevents unrelated websites from silently sending compile jobs to the local runner.

34.3 Hello IPPL

Runner token

MPI ranks

#include "Ippl.h" int main(int argc, char* argv[]) { ippl::initialize(argc, argv); *ippl::Info << "Hello from rank " << ippl::Comm->rank() << " of " << ippl::Comm->size() << ippl::endl; ippl::finalize(); return 0; }

Start the local runner, paste the token, then compile and run.

Runner URL: http://127.0.0.1:5050

This first playground intentionally avoids arbitrary project structure, external files, and long-running jobs. The local runner accepts one source file, clamps the MPI rank count, applies compile/run timeouts, and returns stdout and stderr.