4. Usage modes

The REDAC system is still in development, and thus are the usage modes. Despite we have a single user mode in mind which solely goes via a single entrypoint, which does scheduling, load balancing and the like, we still support a number of different usage modes in the moment. A graphical overview in a block schema diagram is provided in Fig. 4.1 and subsequentialy discussed.

schema drawing

Fig. 4.1 The different user access variants for REDAC

4.1. Queue access

This is the final goal in software

4.2. Direct access via VPN

This is an intermediate state for developing and for experienced users in special situations. Basically, it allows to access directly the Supercontroller or the MCUs directly, depending on what is needed. Usage works via the pybrid python package.

4.3. JupyterHub/Browser access

This is basically a hybrid mode which allows all kind of uses. It combines a number of advantages:

  • User does not need to install any software/development environment locally. He finds the open source scientific programming environment jupyter readily available in browser, comparable to Matlab.

  • Regular queue access is possible

  • However, also direct access is possible since the instance is running within the REDAC internal network.