Home
The main repository contains the source code of openVRE, including the web front-end, which can be easily customizable to your project, and the core code, responsible of managing data, metadata, processing units (analyses and visualizers) and computational resources. This figure shows an overview of one of the possible layouts for a computational infrastructure based on openVRE:
.png)
The different components makes possible to provide the computational environment for an analysis or visualization tool initiated by a user at the VRE web interface. The petition is processed by one of the two schedulers available, PMES or SGE-oneflow. They both end up triggering the tool in the particular virtual machine where the selected tool is encapsulated (see bellow the differences between both enactors). In any case, resources are dynamically assigned based on user demands as the number of dedicated VMs is proportional to the number of job petitions, as long as cloud computational resources allow it. Those VMs have access to a number of data volume where input files are accessible, either private (coming from user's workspace) or public datasets are available, and where output files will be written.
Once job's petition reaches the VM, tool execution starts. In any case. tools are generally wrapped by the mg-tool API, that acts as intermediary agent between the MuGVRE and the tool code itself to uniformelly communicate with it. Thought the API, the application or pipelines is eventually executed.
