VirtualFlow
General
Each VirtualFlow module can be installed and used individually. And it needs to be installed for each workflow which is run. Meaning, that if two workflows are to be run in parallel on a cluster, VirtualFlow will be installed in two freely chosable folders, and the workflow will run in each of them separately.
A VirtualFlow module (VFLP or VFVS) can be installed via one of two ways:
Installation Location
Before installing a VirtualFlow module, the filesystem for the installation has to be chosen. For VirtualFlow, the filesystem has to be a shared storage which is available to all compute nodes which are used by VirtualFlow. Usually, there are two types of such filesystems available on a typical cluster:
The home filesystem
The scratch filesystem
For VirtualFlow, the scratch filesystem should in almost all cases be used, because VirtualFlow can be I/O intensive. And the scratch filesystem is usually able to handle higher I/O loads than the home filesystem. In addition, it can be faster as well. Another reason why the home filesystem is normally not suitable is because the filesystem quota per user is often very low, too low for the often large amounts of input/output data used/generated by VirtualFlow.
Tarball Installation
The tar-archive versions of VirtualFlow modules can be downloaded from the VirtualFlow homepage:
The files can also be obtained directly via the wget command, in the case of VFLP:
And in the case of VFVS:
After downloading the tar-archive, it can be simply installed by extracting it on the desired location. In the case of VFLP:
And in the case of VFVS:
Cloning the GitHub Repository
VirtualFlow can also be installed by cloning the GitHub repository. In the case of VFLP:
And in the case of VFVS:
Last updated