Documentation (VF 2.0)
VF HomepageTutorialsGitHub Repos
  • Documentation
    • Introduction
    • General Features
    • Installation
      • Prerequisities
      • VirtualFlow 2.0
      • VFTools 2.0
      • Uninstallation
    • Backgrounds and Principles
      • Directory Structure
      • Input & Output Databases
      • Job Organization
    • Using VirtualFlow 2.0
      • VirtualFlow 2.0 Commands
      • Preparing the Workflow
      • Starting the Workflow
      • Controlling the Workflow
      • Monitoring the Workflow
      • The Completed Workflow
    • Running VirtualFlow 2.0 in the Cloud
    • Troubleshooting
    • Version History
    • Further Resources
  • VFLP 2.0
    • Introduction
    • Features
    • Installation
      • Prerequisities
      • External Packages
    • Background and Principles
      • Directory Structure
      • Input & Output Databases
    • Using VFLP 2.0
    • Troubleshooting
    • Version History
  • VFVS 2.0
    • Introduction
    • Features
    • Installation
      • External Packages
    • Background and Principles
      • Directory Structure
      • Input & Output Databases
    • Supported docking programs and scoring functions
    • Using VFVS 2.0
      • Preparing the Workflow
      • Monitoring the Workflow
      • The Completed Workflow
    • Troubleshooting
    • Version History
  • VFU 2.0
    • 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 2.0
    • Introduction
    • Installation
Powered by GitBook
On this page
  1. VFVS 2.0
  2. Background and Principles

Directory Structure

PreviousBackground and PrinciplesNextInput & Output Databases

Last updated 2 years ago

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

In the case of VFVS 2.0, 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 2.0 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