You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
New update fixes problems with installation and compatibility:
- updated to python 3.10
- updated biopython to >1.8
- added CUDA version dependence for the installation script to choose correct jaxlib version
- merged all package requirement into a single conda command
- updated Readme
- fixed relative paths for running the scripts to enable execution from anywhere
The navigate into your install folder using *cd* and run the installation code. In *pkg_manager* specify whether you are using 'mamba' or 'conda', if left blank it will use 'conda' by default.
13
+
The navigate into your install folder using *cd* and run the installation code. BindCraft requires a CUDA-compatible Nvidia graphics card to run. In the *cuda* setting, please specify the CUDA version compatible with your graphics card, for example '11.8'. If unsure, leave blank but it's possible that the installation might select the wrong version, which will lead to errors. In *pkg_manager* specify whether you are using 'mamba' or 'conda', if left blank it will use 'conda' by default.
<imgsrc="https://colab.research.google.com/assets/colab-badge.svg"alt="Open In Colab"/>
20
20
</a> <br />
21
21
We prepared a convenient google colab notebook to test the bindcraft code functionalities. However, as the pipeline requires significant amount of GPU memory to run for larger target+binder complexes, we highly recommend to run it using a local installation and at least 32 Gb of GPU memory.
22
22
23
+
**Always try to trim the input target PDB to the smallest size possible! It will significantly speed up the binder generation and minimise the GPU memory requirements.**
24
+
25
+
**Be ready to run at least a few hundred trajectories to see some accepted binders, for difficult targets it might even be a few thousand.**
26
+
23
27
24
28
## Running the script locally and explanation of settings
25
-
To run the script locally, first you need to configure your target .json file in the *target_settings* folder. In the json file are the following settings:
29
+
To run the script locally, first you need to configure your target .json file in the *settings_target* folder. In the json file are the following settings:
26
30
27
31
```
28
32
design_path -> path where to save designs and statistics
@@ -35,16 +39,16 @@ number_of_final_designs -> how many designs that pass all filters to aim for,
The *settings* flag should point to your target .json which you set above. The *filters* flag points to the json where the design filters are specified (default is ./filters/default_filters.json). The *advanced* flag points to your advanced settings (default is ./advanced_settings/4stage_multimer.json). If you leave out the filters and advanced settings flags it will automatically point to the defaults.
41
45
42
46
Alternatively, if your machine does not support SLURM, you can run the code directly by activating the environment in conda and running the python code:
**We recommend to generate at least a 100 final designs passing all filters, then order the top 5-20 for experimental characterisation.** If high affinity binders are required, it is better to screen more, as the ipTM metric used for ranking is not a good predictor for affinity, but has been shown to be a good binary predictor of binding.
0 commit comments