BIGNASim is composed of a rather large and complex set of software units, including two NoSQL database platforms and two web servers. The installation of local copy of the server is not generally recommended. However, in cases where data is sensitive, and must be kept private, or for testing purposes, an installable reduced version of the software is available. Local stand-alone installations will not be connected with the main BIGNASim databases, unless specific agreement.
Downloadable software is tuned to avoid the need of an external database system, although the full functionality of the analysis portal is provided. This would obviously limit the amount of data to be handled, but offers a system capable enough to fulfil the needs of a simulations group to a certain extent. The installable package is being prepared in prepacked Docker images.
BNSLite could be installed in any modern Linux system (it has been tested on Ubuntu, and openSuSE). Note that the installation procedure may require reasonable skills in system administration, and also root privileges due to the use of Docker engine. The downloadable system is designed to run in a single computer or inside a virtual machine.
1.To run BNSLite Docker images, a Docker engine is required. Instructions to install Docker can be found at Docker web site (https://www.docker.com). Note that Docker requires root privileges to be installed. Docker images can be run as part of a virtualized system, refer to Docker instructions to choose the appropriate configuration.
2.Download the installation package.The provided installation script will gather the necessary information about your system and create the configuration file. Docker images will be downloaded automatically in the first run, but they can be installed also beforehand. This is recommended for slow networks.
3.Several data directories should be created: raw trajectory data, analysis results, and database files. These directories could be accessible locally or NFS mounted. If directories do not exist, they will be created by the installation script. Raw trajectory data could be removed after trajectories are loaded and the analysis is performed, but analysis results and databases should be a permanent storage. Data in analysis and database directories is managed by the application. Do not erase or modify any files. A test directory containing the necessary files is provided as example of the needed input files.
Terminal example of the installation process: (From [03:00] to [121:05] the user unassisted analysis is performed)