Postprocessing the ATG Prescreen

After the ATG Prescreen has been carried out, the results have to be postprocessed, and the input files for the ATG Primary Screen created.

Before postprocessing the results, we need to download two additional files:

  • Enamine_REAL_Space_2022q12.count.csv

  • Enamine_REAL_Space_2022q12.todo.csv

They have to be stored in the home folder, because the processing scripts expect them there. The two files can be downloaded and stored in the home folder by using the commands:

aws s3 cp <your AWS bucket access point ID>/Enamine_REAL_Space_2022q12.count.csv ~/
aws s3 cp <your AWS bucket access point ID>/Enamine_REAL_Space_2022q12.todo.csv ~/

The postprocessing can be done using the command:

./vfvs_postprocess_atg-prescreen.sh 10000

The argument(s) that are passed to the command are the number of ligands (screening size) that should be screened in the ATG Primary Screen. Multiple numbers can be specified, causing the command to create multiple todo files for each of these numbers. We only specified one screening size of 10000, meaning that around 10000 ligands (the most promising 10000) would be screened in the ATG Primary Screen. The 10000 ligands will be the ones corresponding to the tranches that were most active in the ATG Prescreen. The command calculates the activity (average docking score) of each tranche of the library that was screened in the ATG Prescreen.

In more detail, the command does the following, in order:

  1. Docking Score File: Creation of a single file containing all the ligands that were screened in the ATG Prescreen (one per line) together with their final docking score.

  2. Sparse Metrics File: Creation of a file that contains the average docking scores for each tranche. For the preparation of this file, the Docking Score File from step 1 is needed.

The files that the command creates are stored in the folder ../output-files.

Last updated