Many computations like physics or biologists simulations these days run on accelerated hardware like CUDA GPUs or Intel Xeon Phi, which are itself distributed in a big compute cluster communicating over MPI. The goal of ISAAC is to visualize this data without the need to download it to the host while using the high computation speed of the accelerator.

ISAAC insists of two parts: The server and the insitu library. Furthermore there needs to be a client, which is able to show the transfered stream and meta data. An example HTML5 client is provided, but needs to be adapted to specific simulations and is not part of ISAAC itself.

Simulation code has just to add some calls and settings to the insitu template library. After that the server will notice when a simulation is running and give the user some options to observe the computations on the fly. It is also possible to send meta data back to the simulation, e.g. to restart it with improved settings.

Please see in INSTALL.md for installing, building and using ISAAC. If you need to install ISAAC on a server not accessible from the outside you need to tunnel the connections of the clients.

• If streaming over twitch or another rtmp compatible service is used, but the rtmp port (1935) ist blocked or a wrong url passed, the server will crash because of the underlying gStreamer rtmp implementation.

ISAAC is licensed under the LGPLv3.