Documentation (VF 1.0)
VirtualFlow HomepageTutorialsGitHub Repos
  • Introduction
  • General Features
  • Installation
    • Prerequisities
    • VirtualFlow
    • VFTools
    • Uninstallation
  • Background and Principles
    • Directory Structure
    • Input & Output Databases
    • Job Organization
  • Using VirtualFlow
    • VirtualFlow Commands
    • Preparing the Workflow
    • Starting the Workflow
    • Controlling the Workflow
    • Monitoring the Workflow
    • The Completed Workflow
  • Running VirtualFlow in the Cloud
  • Troubleshooting
  • Version History
  • Further Resources
  • VFLP
    • Introduction
    • Features
    • Installation
      • Prerequisities
      • External Packages
    • Background and Principles
      • Directory Structure
      • Input & Output Databases
    • Using VFLP
    • Troubleshooting
    • Version History
  • VFVS
    • Introduction
    • Features
    • Installation
      • External Packages
    • Background and Principles
      • Directory Structure
      • Input & Output Databases
    • Using VFVS
      • Preparing the Workflow
      • Monitoring the Workflow
      • The Completed Workflow
    • Troubleshooting
    • Version History
  • VFTools
    • Introduction
    • Installation
Powered by GitBook
On this page
  1. VFVS
  2. Background and Principles

Directory Structure

PreviousBackground and PrinciplesNextInput & Output Databases

Last updated 6 years ago

The general structure of the output-files folder is described about VirtualFlow in general.

In the case of VFVS, the output-files/incomplete and output-files/complete folders. These folders contain for each docking scenario the following sub-folders:

  • results

  • summaries

  • logfiles

  • ligand-lists

The results folder contains the original docking output files of the docking programs in the VirtualFlow database format as described .

The summaries folder contains summaries of the docking scores for each compound.

The log-files folder contains the logging output files of the docking programs,.

The ligand-lists folder if enabled in the control file via the keep_ligand_summary_logs option contains some workflow-related information for each ligand, in particular which processing steps where successful and how long time each step has taken for each ligand.

here
here