BrainVISA 5.0 user use cases

[sapetnioc]

This issue is connected to #20 . Its goal is to define precisely the minimum set of features that we expect to be functional in BrainVISA 5.0. We should list here the various user environments we choose to support. For instance a single user with a single computer, an installation shared by several users on a read-only directory, etc.

[ylep]

Summary of today's visio call:

• Support Singularity and VirtualBox (leave Docker aside)

• Support Linux installation by an admin on a network (e.g. /neurospin/local) -> read-only for end users

• Support installation on a Linux cluster (e.g. alambic)

• Support one-machine Linux installation by a end user who has root access

• Support one-machine Windows installation by a end user who has admin access

  • With decent OpenGL performance

• Support one-machine Mac installation by a end user who has root access

• The release is not modular

• The user must be able to work with their data

• Support external software (SPM, FSL, MATLAB, FreeSurfer...) and document how to configure them for all environments

• Naive users need a GUI to configure their mount points. The GUI should run inside of the container, have a view on host filesystem (/ -> /host bind-mount for Singularity), and edit the relevant casa_distro.json.

• If possible: support Windows installation by an admin on a network (e.g. in MIRCen) [probably not possible with VirtualBox]