Directory Structure

please refer to

General

The root folder of VirtualFlow 2.0 contains the following folders:

  • input-files/

  • output-files/

  • workflow/

  • tools/

  • cfn/

The following image shows the four folders within the VFLP 2.0 root directory and their relationships:

The input-files Folder

The input-files folder contains files that are not part of the VirtualFlow 2.0 code, but are provided by the user as input files. E.g. in the case of VFVS 2.0, it will contain the configuration files for the docking programs.

The only exception is the input ligand database, which can be stored in any location (even outside the VirtualFlow 2.0 root folder) and can be specified in the control file. The reason for this circumstance is that the input ligand database might not only be used for one particular workflow, but multiple instances. Since ligand databases for VirtualFlow 2.0 can be very large, it can be practical to store them only in a single centralized location.

The output-files Folder

The output-files folder is intended for the final output files generated by VirtualFlow during the workflow.

For VFLP 2.0 the output-files folder would contain the prepared ligands. In the case of VFVS 2.0 it would contain the docking results and related output files.

The workflow Folder

The workflow folder contains all the intermediate and runtime files which are needed and generated by VirtualFlow 2.0 itself.

The tools Folder

The tools folder is not used by VirtualFlow 2.0 during the runtime, but it is used by the user. It is used for setting up, starting, controlling, and monitoring the workflow.

The tools folder is also the primary working directory of VirtualFlow 2.0, meaning that all VirtualFlow 2.0 user commands (the commands starting with vflp_ or vfvs_) have to be run from this folder. Also, the batch jobs which are run by VirtualFlow 2.0 use the tools folder as their working directory. All paths specified in the configuration files of VirtualFlow are relative to the tools folder.

Last updated