LogoLogo
VF HomepageDocumentationGitHub Repos
  • Tutorial Overview
  • Tutorial 1: VFVS 2.0 on AWS
    • Introduction
    • Installation of VFVS
    • Setting up the ATG Prescreen
    • Starting the ATG Prescreen
    • Monitoring the ATG Prescreen
    • Postprocessing the ATG Prescreen
    • Preparing the ATG Primary Screen
    • Running the ATG Primary Screen
    • Postprocessing the ATG Primary Screen
  • Tutorial 2: VFVS 2.0 on Slurm
    • Introduction
    • Installation of VFVS
    • Setting up the ATG Prescreen
    • Starting the ATG Prescreen
    • Monitoring the ATG Prescreen
    • * Postprocessing the ATG Prescreen
    • Preparing the ATG Primary Screen
    • Running the ATG Primary Screen
    • * Postprocessing the ATG Primary Screen
    • The Completed Workflow (Update in Progress for the Python version)
      • Local installation and deployment of HPC-toolkit
      • Installing VirtualFlow2.0
      • Screening the sparse library with VirtualFlow 2.0
      • Extracting and viewing the results
Powered by GitBook
On this page
  1. Tutorial 2: VFVS 2.0 on Slurm

Monitoring the ATG Prescreen

PreviousStarting the ATG PrescreenNext* Postprocessing the ATG Prescreen

Last updated 1 year ago

At present, the only way to monitor progress of jobs will be to check status through the . This will be extended in the future to more natively track progress towards completion. Among the slurm commands for monitoring is the squeue command.

All outputs for successful docking are stored within the ../output-files folder.

For debugging, the slurm errors are contained within the ../workflow/workunits folder.

If a significant number of dockings or jobs failed, then something went wrong, and the problem needs to be resolved and the workflow prepared and run again.

The ATG Prescreen is complete when all workunits/jobs have been successfully completed.

Slurm scheduler commands