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. Documentation
  2. Using VirtualFlow 2.0

The Completed Workflow

Long-Term Storage

For long-term storage, one can create a compressed tar archive of the VirtualFlow 2.0 root folder:

tar -xvzf VF.tar.gz <VirtualFlow root folder>

Alternatively, one might to choose only to store the output ligand databases, which are located in the output-files/completefolder.

PreviousMonitoring the WorkflowNextRunning VirtualFlow 2.0 in the Cloud

Last updated 2 years ago