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
  • General
  • The input-files Folder
  1. VFLP
  2. Background and Principles

Directory Structure

PreviousBackground and PrinciplesNextInput & Output Databases

Last updated 6 years ago

General

The directory structure of VFLP is as the as for for VirtualFlow in general (as described ).

The input-files Folder

What is specific for VFLP is that the input-files folder does not contain anything, except possibly the input ligand collection, which can also be stored at another location (as specifiable in the control file). The reason that the input-files folder does not need to contain anything is that the external programs which are used by VFLP do not need any input files except the ligands.

here