Giter Site home page Giter Site logo

lightdock / lightdock Goto Github PK

View Code? Open in Web Editor NEW
278.0 12.0 35.0 95.23 MB

Protein-protein, protein-peptide and protein-DNA docking framework based on the GSO algorithm

Home Page: https://lightdock.org/

License: GNU General Public License v3.0

Python 92.63% Shell 0.27% C 5.74% C++ 0.21% Roff 0.08% Cython 1.07%
protein protein-structure protein-protein-interaction protein-docking swarm-intelligence glowworm-swarm-optimization protein-dna-interactions peptides dna docking

lightdock's Introduction

License: GPL v3 PyPi version PyPi Downloads Supported versions Downloads

1. Synopsis

LightDock is a protein-protein, protein-peptide and protein-DNA docking framework based on the Glowworm Swarm Optimization (GSO) algorithm.

The LightDock framework is highly versatile, with many options that can be further developed and optimized by the users: it can accept any user-defined scoring function, can use local gradient-free minimization, the simulation can be restrained from the beginning to focus on user-assigned interacting regions, it supports residue restraints in both receptor and ligand partners.

2. Reference

LightDock protocol and the updates to make use of residue restraints have been published in Oxford Bioinformatics journal. Please cite these references if you use LightDock in your research:

LightDock: a new multi-scale approach to protein–protein docking
Brian Jiménez-García, Jorge Roel-Touris, Miguel Romero-Durana, Miquel Vidal, Daniel Jiménez-González and Juan Fernández-Recio
Bioinformatics, Volume 34, Issue 1, 1 January 2018, Pages 49–55, https://doi.org/10.1093/bioinformatics/btx555

LightDock goes information-driven
Jorge Roel-Touris, Alexandre M.J.J. Bonvin, Brian Jiménez-García
Bioinformatics, btz642; doi: https://doi.org/10.1093/bioinformatics/btz642

Integrative Modeling of Membrane-associated Protein Assemblies
Jorge Roel-Touris, Brian Jiménez-García & Alexandre M.J.J. Bonvin
Nat Commun 11, 6210 (2020); doi: https://doi.org/10.1038/s41467-020-20076-5

3. Installation

Lightdock software is compatible and it has been tested with the followings OS:

  • macOS: El Capitan, Sierra, High Sierra, Mojave, Catalina.
  • GNU/Linux: Ubuntu 16+, Debian Stretch+, Scientific Linux 6+, CentOS 6+.
  • 100% compatible with Google Colab platform

Microsoft Windows is not officially supported, despite many parts of the protocol might be able to run. Please use it at your own risk. If you wish to contribute testing and developing LightDock for Windows, please contact us.

3.1. Dependencies

LightDock has the following dependencies:

Optional dependencies are:

3.2. Install LightDock

The fastest way to install LightDock is to use pip:

pip install lightdock

4. Development

For development and extension of the LightDock code, please follow these instructions:

4.1. Clone

Clone this repository:

git clone https://github.com/lightdock/lightdock.git

4.2. Compile Python C and Cython extensions

Please make sure dependencies are already installed (via pip, package manager, etc.):

  • numpy>=1.17.1
  • scipy>=1.3.1
  • cython>=0.29.13
  • prody>=1.10.11
  • freesasa>=2.0.3

It is recommended to create a virtual environment and install it:

virtualenv venv
source venv/bin/activate
cd lightdock
pip install -e .

If not using pip or setuptools for development, there is as bash script to compile all the extensions:

cd lightdock
./setup.sh

4.3. Add Lightdock to your path

Add the following lines to your ~/.bashrc file, don't forget to change /path/to/lightdock:

# LightDock
export LIGHTDOCK_HOME="/path/to/lightdock"
export PATH=$PATH:$LIGHTDOCK_HOME/bin
export PYTHONPATH=$PYTHONPATH:$LIGHTDOCK_HOME

Don't forget to apply the changes:

source ~/.bashrc

4.4. Testing

You can run LightDock tests:

cd lightdock
nosetests

5. Documentation

The complete documentation about how to run the LightDock protocol and several tutorials and use cases can be found at https://lightdock.org/tutorials.

6. Get Help

LightDock is being actively developed and some issues may arise or you may need extra help to run LightDock. In those cases, there are two main ways to get help:

  1. Read the FAQ in case your problem was already reported
  2. Open a new issue in this repository
  3. Or write an email to [email protected] (we will do our best to answer your questions as soon as possible)

7. LICENSE

LightDock is available under GPLv3 License. See LICENSE document for more details.

lightdock's People

Contributors

alchemistcai avatar brianjimenez avatar jorgeroel avatar mvidalpinol avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

lightdock's Issues

[lgd_cluster_bsas.py] Clustering has failed.

Describe the bug
Clustering with lgd_cluster_bsas.py fails with the following error message:

[lgd_cluster_bsas] ERROR: Clustering has failed. Please see error:
[lgd_cluster_bsas] ERROR: reference and target arrays must have the same number of atoms

I am mostly trying to understand the error to see how I can approach it, however, I have not seen anyone else come across this.

To Reproduce
Fresh install of LightDock.
lightdock3_setup.py --noh --noxt rec.pdb lig.pdb -r restraints_file, restraint files for 5 residues on the receptor only (all active).
Using lightdock3.py setup.json 10, 100 swarms generated, 200 glowworms per swarm, 10 steps.
For each swarm:
lgd_generate_conformations.py ../rec.pdb ../lig.pdb gso_10.out 200
Structures generate successfully. Then, for each swarm:
cd swarm_*
lgd_cluster_bsas.py gso_10.out
Which results in the output pasted all the way down below.

The one thing I differ from in the tutorial is I have two sh scripts to execute lgd_generate_conformations and lgd_cluster_bsas automatically on each swarm folder. Model generation works perfectly. Clustering fails even when executing manually on a swarm folder. Those scripts look like this:

Model Gen (edited to reflect correct file names):

#!/usr/bin/env sh

CORES=8
s=`ls -d ./swarm_* | wc -l`
swarms=$((s-1))

### Create files ###
for i in $(seq 0 $swarms)
  do
      cd swarm_${i}
      lgd_generate_conformations.py ../rec.pdb ../lig.pdb gso_10.out 200
      cd ..
  done

Clustering:

#!/usr/bin/env sh

CORES=8
s=`ls -d ./swarm_* | wc -l`
swarms=$((s-1))

### Create files ###
for i in $(seq 0 $swarms)
  do
      cd swarm_${i}
      lgd_cluster_bsas.py gso_10.out
      cd ..
  done

Expected behavior
Generation of a cluster.repr file with successful clustering of the structures.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: Windows 11 WSL2 Ubuntu
  • LightDock installed with pip inside a conda environment with Python 3.10.9

Additional context
Full output of command:

(LDock) myUser@COMP:~/Projects/LightDock/swarm_99$ lgd_cluster_bsas.py gso_10.out
@> ProDy is configured: verbosity='info'
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_10.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_68.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_193.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_60.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_137.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_117.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_51.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_91.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_25.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_138.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_18.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_52.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_58.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_87.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_163.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_103.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_173.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_1.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_155.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_61.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_100.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_37.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_70.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_124.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_166.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_114.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_48.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_84.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_59.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_57.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_147.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_141.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_197.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_150.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_187.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_47.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_95.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_11.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_73.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_118.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_23.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_72.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_153.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_82.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_5.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_75.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_104.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_176.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_107.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_40.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_13.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_39.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_76.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_199.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_41.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_121.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_86.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_134.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_26.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_30.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_158.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_63.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_14.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_189.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_135.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_31.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_169.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_110.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_53.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_3.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_125.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_190.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_186.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_106.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_133.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_109.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_168.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_161.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_43.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_20.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_80.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_171.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_154.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_16.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_191.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_113.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_195.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_85.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_93.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_194.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_156.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_49.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_179.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_127.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_152.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_102.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_56.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_105.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_36.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_34.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_139.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_89.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_148.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_198.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_69.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_8.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_19.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_64.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_6.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_112.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_24.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_32.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_99.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_54.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_21.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_196.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_120.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_98.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_9.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_66.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_71.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_50.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_101.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_159.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_22.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_115.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_79.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_140.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_175.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_97.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_132.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_88.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_67.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_143.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_7.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_2.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_92.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_27.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_28.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_142.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_122.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_35.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_145.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_174.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_94.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_165.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_119.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_192.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_144.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_136.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_129.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_149.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_184.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_164.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_90.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_178.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_15.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_81.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_167.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_123.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_29.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_83.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_170.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_157.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_146.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_42.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_160.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_111.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_151.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_108.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_62.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_128.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_38.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_33.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_126.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_45.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_182.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_172.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_185.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_12.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_77.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_131.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_130.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_65.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_116.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_177.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_96.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_78.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_4.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_44.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_188.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_55.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_181.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_46.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_17.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_74.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_183.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_0.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_162.pdb
[lgd_cluster_bsas] INFO: Reading CA from /home/myUser/Projects/LightDock/swarm_99/lightdock_180.pdb
[lgd_cluster_bsas] INFO: Glowworm 68 with pdb lightdock_68.pdb
[lgd_cluster_bsas] INFO: RMSD between 10 and 68 is 1.919
[lgd_cluster_bsas] INFO: Glowworm 68 goes into cluster 0
[lgd_cluster_bsas] INFO: Glowworm 193 with pdb lightdock_193.pdb
[lgd_cluster_bsas] INFO: RMSD between 10 and 193 is 5.427
[lgd_cluster_bsas] INFO: New cluster 1
[lgd_cluster_bsas] INFO: Glowworm 60 with pdb lightdock_60.pdb
[lgd_cluster_bsas] INFO: RMSD between 10 and 60 is 2.399
[lgd_cluster_bsas] INFO: Glowworm 60 goes into cluster 0
[lgd_cluster_bsas] INFO: Glowworm 137 with pdb lightdock_137.pdb
[lgd_cluster_bsas] INFO: RMSD between 10 and 137 is 1.613
[lgd_cluster_bsas] INFO: Glowworm 137 goes into cluster 0
[lgd_cluster_bsas] INFO: Glowworm 117 with pdb lightdock_117.pdb
[lgd_cluster_bsas] INFO: RMSD between 10 and 117 is 2.342
[lgd_cluster_bsas] INFO: Glowworm 117 goes into cluster 0
[lgd_cluster_bsas] INFO: Glowworm 51 with pdb lightdock_51.pdb
[lgd_cluster_bsas] INFO: RMSD between 10 and 51 is 5.774
[lgd_cluster_bsas] INFO: RMSD between 193 and 51 is 0.377
[lgd_cluster_bsas] INFO: Glowworm 51 goes into cluster 1
[lgd_cluster_bsas] INFO: Glowworm 91 with pdb lightdock_91.pdb
[lgd_cluster_bsas] INFO: RMSD between 10 and 91 is 5.425
[lgd_cluster_bsas] INFO: RMSD between 193 and 91 is 0.197
[lgd_cluster_bsas] INFO: Glowworm 91 goes into cluster 1
[lgd_cluster_bsas] INFO: Glowworm 25 with pdb lightdock_25.pdb
[lgd_cluster_bsas] INFO: RMSD between 10 and 25 is 10.461
[lgd_cluster_bsas] INFO: RMSD between 193 and 25 is 7.457
[lgd_cluster_bsas] INFO: New cluster 2
[lgd_cluster_bsas] INFO: Glowworm 138 with pdb lightdock_138.pdb
[lgd_cluster_bsas] INFO: RMSD between 10 and 138 is 6.267
[lgd_cluster_bsas] INFO: RMSD between 193 and 138 is 1.047
[lgd_cluster_bsas] INFO: Glowworm 138 goes into cluster 1
[lgd_cluster_bsas] INFO: Glowworm 18 with pdb lightdock_18.pdb
[lgd_cluster_bsas] INFO: RMSD between 10 and 18 is 7.771
[lgd_cluster_bsas] INFO: RMSD between 193 and 18 is 3.519
[lgd_cluster_bsas] INFO: Glowworm 18 goes into cluster 1
[lgd_cluster_bsas] INFO: Glowworm 52 with pdb lightdock_52.pdb
[lgd_cluster_bsas] INFO: RMSD between 10 and 52 is 5.846
[lgd_cluster_bsas] INFO: RMSD between 193 and 52 is 0.606
[lgd_cluster_bsas] INFO: Glowworm 52 goes into cluster 1
[lgd_cluster_bsas] INFO: Glowworm 58 with pdb lightdock_58.pdb
[lgd_cluster_bsas] INFO: RMSD between 10 and 58 is 6.431
[lgd_cluster_bsas] INFO: RMSD between 193 and 58 is 3.341
[lgd_cluster_bsas] INFO: Glowworm 58 goes into cluster 1
[lgd_cluster_bsas] INFO: Glowworm 87 with pdb lightdock_87.pdb
[lgd_cluster_bsas] INFO: RMSD between 10 and 87 is 7.998
[lgd_cluster_bsas] INFO: RMSD between 193 and 87 is 4.261
[lgd_cluster_bsas] INFO: RMSD between 25 and 87 is 8.824
[lgd_cluster_bsas] INFO: New cluster 3
[lgd_cluster_bsas] INFO: Glowworm 163 with pdb lightdock_163.pdb
[lgd_cluster_bsas] INFO: RMSD between 10 and 163 is 8.978
[lgd_cluster_bsas] INFO: RMSD between 193 and 163 is 6.438
[lgd_cluster_bsas] INFO: RMSD between 25 and 163 is 2.519
[lgd_cluster_bsas] INFO: Glowworm 163 goes into cluster 2
[lgd_cluster_bsas] INFO: Glowworm 103 with pdb lightdock_103.pdb
[lgd_cluster_bsas] INFO: RMSD between 10 and 103 is 13.501
[lgd_cluster_bsas] INFO: RMSD between 193 and 103 is 13.156
[lgd_cluster_bsas] INFO: RMSD between 25 and 103 is 15.028
[lgd_cluster_bsas] INFO: RMSD between 87 and 103 is 12.604
[lgd_cluster_bsas] INFO: New cluster 4
[lgd_cluster_bsas] INFO: Glowworm 173 with pdb lightdock_173.pdb
[lgd_cluster_bsas] INFO: RMSD between 10 and 173 is 9.111
[lgd_cluster_bsas] INFO: RMSD between 193 and 173 is 5.037
[lgd_cluster_bsas] INFO: RMSD between 25 and 173 is 5.727
[lgd_cluster_bsas] INFO: RMSD between 87 and 173 is 4.409
[lgd_cluster_bsas] INFO: RMSD between 103 and 173 is 12.357
[lgd_cluster_bsas] INFO: New cluster 5
[lgd_cluster_bsas] INFO: Glowworm 1 with pdb lightdock_1.pdb
[lgd_cluster_bsas] ERROR: Clustering has failed. Please see error:
[lgd_cluster_bsas] ERROR: reference and target arrays must have the same number of atoms

error: run lightdock3_setup.py DDB1-CRBN.pdb brd4.pdb --noxt --noh --now -anm

[lightdock3_setup] INFO: Ignoring OXT atoms
[lightdock3_setup] INFO: Ignoring Hydrogen atoms
[lightdock3_setup] INFO: Ignoring water
[lightdock3_setup] INFO: Reading structure from DDB1-CRBN.pdb PDB file...
[lightdock3_setup] ERROR: LightDock setup failed. Please see:
[lightdock3_setup] ERROR: [AtomError] Not recognized element 'Z' for atom ZN.

Protein-RNA docking

Hi, I am trying to verify the interaction of a circular RNA (in a circular form, not linear form) with a protein by Lightdock3. All steps were performed properly until the setup step. In this step, I faced this error:

TypeError: can't multiply sequence by non-int of type 'Forward'

Screenshot from 2024-03-09 15-02-22

I will appreciate if you help me to solve this problem.

a mistake during lightdock

Dear Brian Jimenez,
I used modeller homology modeling to get an antibody structure, and then I encountered an error when docking the antibody with a structure-known antigen using lightdock, I wanted to know what was wrong? Whether the antibody or antigen structure files need to be processed?
I used the default settings in the 2UUY example.
Fig

lightdock.zip

ERROR: [NormalModesCalculationError] when using --anm with --membrane

I am trying to run the membrane-associated protein docking tutorial but also including ligand flexibility (specifying --anm flag).

I get the following error during setup

lightdock3_setup.py receptor_membrane_P.pdb 2hdi_unbound_B.pdb --noxt --noh --membrane --anm

[lightdock3_setup] INFO: Ignoring OXT atoms
[lightdock3_setup] INFO: Ignoring Hydrogen atoms
[lightdock3_setup] INFO: Reading structure from receptor_membrane_P.pdb PDB file...
[pdb] WARNING: Possible problem: [SideChainError] Incomplete sidechain for residue ARG.111
[pdb] WARNING: Possible problem: [SideChainError] Incomplete sidechain for residue LYS.212
[pdb] WARNING: Possible problem: [SideChainError] Incomplete sidechain for residue ARG.643
[pdb] WARNING: Possible problem: [SideChainError] Incomplete sidechain for residue ASN.649
[lightdock3_setup] INFO: 5155 atoms, 1056 residues read.
[lightdock3_setup] INFO: Ignoring OXT atoms
[lightdock3_setup] INFO: Ignoring Hydrogen atoms
[lightdock3_setup] INFO: Reading structure from 2hdi_unbound_B.pdb PDB file...
[lightdock3_setup] INFO: 810 atoms, 103 residues read.
[lightdock3_setup] INFO: Calculating reference points for receptor receptor_membrane_P.pdb...
[lightdock3_setup] INFO: Reference points for receptor found, skipping
[lightdock3_setup] INFO: Done.
[lightdock3_setup] INFO: Calculating reference points for ligand 2hdi_unbound_B.pdb...
[lightdock3_setup] INFO: Reference points for ligand found, skipping
[lightdock3_setup] INFO: Done.
[lightdock3_setup] INFO: Saving processed structure to PDB file...
[lightdock3_setup] INFO: Done.
[lightdock3_setup] INFO: Saving processed structure to PDB file...
[lightdock3_setup] INFO: Done.
[lightdock3_setup] INFO: Calculating ANM for receptor molecule...
[ANM] INFO: Number of atoms of the ANM model: 4697
[ANM] INFO: Number of nodes in the model: (14091, 10)
[lightdock3_setup] ERROR: LightDock setup failed. Please see:
[lightdock3_setup] ERROR: [NormalModesCalculationError] Number of atoms and ANM model differ. Please, check there are no missing nucleotides nor residues.

I may be wrong here but I think the dummy atoms acting as the membrane CG beads are also being considered during the normal mode calculations while I was expecting light dock to automatically ignore the membrane beads when --anm is used with --membrane flag.

Is there a workaround to do a flexible docking calculation with membranes? Setting the number of receptor modes to zero (-ar 0 ) seems to work but I would like the receptor to also be flexible. Can you please help me with this?

I am running lightdock-0.9.0 on Ubuntu within WSL2

Please let me know if you need additional information to help me.

Thank you so much for your great contribution!

Srilok

Reference count error encountered in sipper.c

This is an error that is particularly difficult to reproduce but there nonetheless. I will explain the error here and demonstrate the solution that solved the issue for my setup. This is a bug in version 0.9.1

The error pertains to the following line in sipper.c and its use of the PyArray_AsCArray function.

PyArray_AsCArray((PyObject **)&tmp1, (void **)&lig_array, dims, 2, descr);

In this call, we use the descr object to specify the type. However, in the source of the numpy API it is mentioned that PyArray_AsCArray steals the reference to the descr object (see the source code here). This means that the same descr object should not be used in both calls to PyArray_AsCArray.

Otherwise I understandably get the following error.

*** Reference count error detected: an attempt was made to deallocate the dtype 12 (d) ***

This does not actually halt the computation of the fitness and is in practise more of a warning. But a particularly annoying warning considering the number of fitness calculations performed.

The fix for this is simply to create another reference to the descr object to make the code effectively as follows

        // descr = PyArray_DescrFromType(NPY_DOUBLE);

        tmp0 = PyObject_GetAttrString(receptor_coordinates, "coordinates");
        tmp1 = PyObject_GetAttrString(ligand_coordinates, "coordinates");

        rec_len = PySequence_Size(tmp0);
        lig_len = PySequence_Size(tmp1);

        dims[1] = 3;
        dims[0] = rec_len;
        descr = PyArray_DescrFromType(NPY_DOUBLE);
        PyArray_AsCArray((PyObject **)&tmp0, (void **)&rec_array, dims, 2, descr);

        dims[0] = lig_len;
        descr = PyArray_DescrFromType(NPY_DOUBLE);  // ref gets stolen by PyArray_AsCArray
        PyArray_AsCArray((PyObject **)&tmp1, (void **)&lig_array, dims, 2, descr);

Results and replication Protein–Protein Docking Benchmark 5.0

Are results from "Protein–Protein Docking Benchmark 5.0" (https://zlab.umassmed.edu/benchmark/) available for LightDock? This benchmark is mentioned in your original paper https://academic.oup.com/bioinformatics/article/34/1/49/4103399?

Or is there any replication scenario/protocol which I could run by myself?

I'm facing not conclusive docking scores using default LightDock parameters and examples from mentioned benchmark.

My setup:

  • lightdock==0.9.2
  • pdb files were taken from Benchmark 5.5
    • receptor names were from {name}_r_u.pdb.gz files
    • ligand names were from {name}_l_u.pdb.gz files
  • executed commands were:
    • lightdock3_setup.py receptor.pdb ligand.pdb --noxt --noh --now
    • lightdock3.py setup.json 100
    • for fetching results: lgd_rank.py `ls -d ./swarm_* | wc -l` 100 and then first score from rank_by_scoring.list

Scores I got for few examples:

1CLV	26.133
1FLE	27.331
1GL1	24.781
1OC0	25.235
1PPE	23.721
1R0R	24.928
2ABZ	29.969
3SGQ	24.173
4CPA	25.791
1FCC	37.313
1XU1	26.460
1CGI	25.396

Then for exact same receptors I had used ligand from 1GL1 to check what would results be, if I choose "random", non binding example. Scores were:

1CLV	27.660
1FLE	25.199

1OC0	22.970
1PPE	25.460
1R0R	22.275
2ABZ	22.084
3SGQ	22.410
4CPA	23.180
1FCC	32.067
1XU1	22.515
1CGI	26.573

As you can see scores for non binding examples are very similar as for real ones.

Was I just out of luck and had chosen only examples, which LightDock is unable to check for binding? Can you provide complex names from benchmark with high LightDock score?
What should be threshold score for cutoff with default LightDock setup? Is it always something around 50? In tutorial https://lightdock.org/tutorials/0.9.2/restraints I got best score around 56-57.

Thank you for your great work

Why not support docking a ligand?

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
Allow to dock lead-like or drug-like molecules.

Describe alternatives you've considered
Not use lightdock?

Additional context
N/A

Use MPI for simulation

Hello, the '-mpi' flag was used when executing the lightdock3.py file. However, during the run, when executing comm.Barrier(), and num_workers = comm.size, the variable num_workers is assigned the value of 1. This results in an error in the file "lightdock-master/lightdock/simulation/docking_mpi.py", specifically at line 226 in the run_simulation function:starting_points_files[id_swarm],The error message is "IndexError: list index out of range." Is this due to a possible incorrect installation of mpi4py?
error

ERROR: [NotSupportedInScoringError] Residue A.SER.1 or atom HT1 not supported. DFIRE only supports standard aminoacids without hydrogens.

wenyanbo @ WendeMacBook-Pro in ~/Schrodinger/test4 [14:58:33]

$ lightdock3_setup.py 6LU7_prep.pdb EM.pdb -s 20 -g 40
[lightdock3_setup] INFO: Reading structure from 6LU7_prep.pdb PDB file...
[pdb] WARNING: Possible problem: [BackboneError] Incomplete backbone for residue GLN.306
[pdb] WARNING: Possible problem: [ResidueNonStandardError] Can not check non-standard residue 02J.1
[pdb] WARNING: Possible problem: [ResidueNonStandardError] Can not check non-standard residue PJE.5
[pdb] WARNING: Possible problem: [ResidueNonStandardError] Can not check non-standard residue 010.6
[lightdock3_setup] INFO: 4779 atoms, 312 residues read.
[lightdock3_setup] INFO: Reading structure from EM.pdb PDB file...
[pdb] WARNING: Possible problem: [ResidueNonStandardError] Can not check non-standard residue UNK.1
[lightdock3_setup] INFO: 172 atoms, 1 residues read.
[lightdock3_setup] INFO: Calculating reference points for receptor 6LU7_prep.pdb...
[lightdock3_setup] INFO: Reference points for receptor found, skipping
[lightdock3_setup] INFO: Done.
[lightdock3_setup] INFO: Calculating reference points for ligand EM.pdb...
[lightdock3_setup] INFO: Reference points for ligand found, skipping
[lightdock3_setup] INFO: Done.
[lightdock3_setup] INFO: Saving processed structure to PDB file...
[lightdock3_setup] INFO: Done.
[lightdock3_setup] INFO: Saving processed structure to PDB file...
[lightdock3_setup] INFO: Done.
[lightdock3_setup] INFO: Calculating starting positions...
[lightdock3_setup] INFO: Generated 20 positions files
[lightdock3_setup] INFO: Done.
[lightdock3_setup] INFO: Preparing environment
[lightdock3_setup] INFO: Done.
[lightdock3_setup] INFO: LightDock setup OK

$ lightdock3.py setup.json 10

[lightdock] INFO: simulation parameters saved to lightdock.info.1
[lightdock3_setup] INFO: Reading structure from lightdock_6LU7_prep.pdb PDB file...
[pdb] WARNING: Possible problem: [BackboneError] Incomplete backbone for residue GLN.306
[pdb] WARNING: Possible problem: [ResidueNonStandardError] Can not check non-standard residue 02J.1
[pdb] WARNING: Possible problem: [ResidueNonStandardError] Can not check non-standard residue PJE.5
[pdb] WARNING: Possible problem: [ResidueNonStandardError] Can not check non-standard residue 010.6
[lightdock3_setup] INFO: 4779 atoms, 312 residues read.
[lightdock3_setup] INFO: Reading structure from lightdock_EM.pdb PDB file...
[pdb] WARNING: Possible problem: [ResidueNonStandardError] Can not check non-standard residue UNK.1
[lightdock3_setup] INFO: 172 atoms, 1 residues read.
[lightdock] INFO: Loading scoring function...
[lightdock] INFO: Using DFIRE scoring function
[lightdock] ERROR: Error found in selected scoring function:
[lightdock] ERROR: [NotSupportedInScoringError] Residue A.SER.1 or atom HT1 not supported. DFIRE only supports standard aminoacids without hydrogens.

No swarms generated when only restraints in ligand provided

Describe the bug
During setup and if only ligand restraints are provided, setup finishes generating 0 swarms.

To Reproduce
In restraints.list file, only provide ligand restraints for a given complex.

Expected behavior
Setup should generate swarms independently of ligand restraints provided.

`setup.py` depends on `numpy` but you may not have `numpy` preinstalled.

Describe the bug
The setup.py file uses numpy but is also where lightdock defines it depends on numpy.

To Reproduce
Simply run pip install lightdock on a fresh environment (i.e. without numpy installed).

Expected behavior
Should install numpy and run the related code after?

Desktop (please complete the following information):

  • OS: Ubuntu
  • Version 20.04.2 LTS

Error encountered with DNA scoring function in lightdock3.py for DNA-DNA docking

When using the DNA scoring function in lightdock3.py, an error occurs related to unsupported residues or atoms.
Steps to reproduce the behavior: Run the command !lightdock3.py setup.json 100 -c 1 -s dna -l 60. Observe the error message and traceback.
Expected behavior. I expected the DNA scoring function to handle the residues and atoms properly and perform the docking simulation without errors.
Screenshots
!lightdock3.py setup.json 100 -c 1 -sdfire -l 60
[lightdock] INFO: simulation parameters saved to lightdock.info.3
[lightdock3_setup] INFO: Ignoring OXT atoms
[lightdock3_setup] INFO: Ignoring Hydrogen atoms
[lightdock3_setup] INFO: Reading structure from lightdock_AptN1V3_4C100_20_Own.pdb PDB file...
[pdb] WARNING: Possible problem: [ResidueNonStandardError] Can not check non-standard residue T.2
[lightdock3_setup] INFO: 525 atoms, 24 residues read.
[lightdock3_setup] INFO: Ignoring OXT atoms
[lightdock3_setup] INFO: Ignoring Hydrogen atoms
[lightdock3_setup] INFO: Reading structure from lightdock_Argus_target.pdb PDB file...
[pdb] WARNING: Possible problem: [ResidueNonStandardError] Can not check non-standard residue T.6
[pdb] WARNING: Possible problem: [ResidueNonStandardError] Can not check non-standard residue T.8
[pdb] WARNING: Possible problem: [ResidueNonStandardError] Can not check non-standard residue T.13
[pdb] WARNING: Possible problem: [ResidueNonStandardError] Can not check non-standard residue T.14
[pdb] WARNING: Possible problem: [ResidueNonStandardError] Can not check non-standard residue T.17
[pdb] WARNING: Possible problem: [ResidueNonStandardError] Can not check non-standard residue T.19
[pdb] WARNING: Possible problem: [ResidueNonStandardError] Can not check non-standard residue T.20
[pdb] WARNING: Possible problem: [ResidueNonStandardError] Can not check non-standard residue T.21
[lightdock3_setup] INFO: 517 atoms, 24 residues read.
[lightdock] INFO: Loading scoring function...
[lightdock] INFO: Using DNA scoring function
[lightdock] ERROR: Error found in selected scoring function:
[lightdock] ERROR: [NotSupportedInScoringError] Residue A.C.1 or atom O5* not supported. DNA scoring only supports AMBER94 types.

Desktop:
OS: Windows 10
Python version: Python 3.8.5
lightdock3.py version: I'm using Google Colab

Additional context
I'm running the lightdock3.py script with the following command: !lightdock3.py setup.json 100 -c 1 -s dna -l 60 on a Linux machine (Ubuntu 20.04) with Python 3.10.0. The input PDB files used are lightdock_AptN1V3_4C100_20_Own.pdb and lightdock_Argus_target.pdb. These PDB files contain DNA structures.

The error message I encounter is as follows:
[lightdock] INFO: Loading scoring function...
[lightdock] INFO: Using DNA scoring function
[lightdock] ERROR: Error found in selected scoring function:
[lightdock] ERROR: [NotSupportedInScoringError] Residue A.C.1 or atom O5' not supported. DNA scoring only supports AMBER94 types.
It seems that the error is related to the residue named "A.C.1" and the atom "O5'" in the DNA structures. The error suggests that the DNA scoring function only supports AMBER94 types. The PDB files seem to be properly formatted and contain valid DNA structures. However, it appears that the DNA scoring function used by lightdock3.py is

e1
e2
not compatible with these specific residues or atoms.
I would appreciate any assistance in resolving this issue or any suggestions for alternative approaches to perform DNA-DNA docking using the LightDock software.
Feel free to add any additional information or details that you think might be relevant in helping to address the issue.

dna.pdb file empty after running `reduce_to_amber.py` and subsequent error during simulation

Dear all

I have constructed a predicted protein structure and generated a dna structure from Pymol based on a sequence of interest, and was following the tutorial for protein-DNA prediction.

After using reduce to clear and add hydrogens, my reduce_to_amber.py resulted in an empty output file.

Nonetheless, following setting up lightdock using the lightdock3_setup.py command, I tried to use the hydrogen-filled original dna structure .pdb file to run the simulation. I was given the following error:

[lightdock] ERROR: [NotSupportedInScoringError] Residue A.HIS.282 or atom HE2 not supported. DNA scoring only supports AMBER94 types.

It appears that it is in fact the protein structure that is giving me a problem. How should I go about fixing this?

Thank you very much

Marc

Ligands are not placed in designated swarm centers

Perhaps I am missing something so might not be a bug.
I am manually deciding at which swarm centers (obtained from swarm_centers.pdb file) i want to dock my ligand. Except for swarm 0 and sometimes 1, none of the ligands are placed in the right swarm_center coordinates. for example (see below), I want my ligand (cyan color) to be placed in the swarm_2 - as the number start from 0 (represented as gray sphere) but as you can see the ligands are placed in completely different place. I am using your example protein-ligand i.e. 2UUY as an example.

image

Issues when docking

Hello, I am docking a Gastrin protein to the Cholecystokinin receptor. When I do this, I get the following error:

[NormalModesCalculationError] Atoms differ: CB 99.255 109.616 129.421 - Atom N (index 3890)

How do I fix this?

Do you need the proteins' .pdb files?

test_dna and test_pydock failed.

Describe the bug

I tried to add brackets after residues' is_* methods in the lightdock.structure.complex.Complex.get_atoms function's defination as they are not properties,but lightdock.test.bin.test_dna.Test* and lightdock.test.bin.test_pydock.Test* tests failed.

These tests didn't pass atom sanity checks in the lightdock.structure.nm.calculate_nmodes function because of the different atom indice.

To Reproduce

I tried to change the codes as below:

# in lightdock.structure.complex.Complex.get_atoms
    def get_atoms(
        self, protein: bool = True, nucleic: bool = True, dummy: bool = False
    ):
        """Selects atoms on structure depending on their nature"""
        atoms: "list[Atom]" = []
        for residue in self.residues:

#  original 
            if residue.is_standard and protein:
                atoms.extend(residue.atoms)
            elif residue.is_nucleic and nucleic:
                atoms.extend(residue.atoms)
            elif residue.is_dummy and dummy:
                atoms.extend(residue.atoms)
        return atoms

# new 
            if residue.is_standard() and protein:
                atoms.extend(residue.atoms)
            elif residue.is_nucleic() and nucleic:
                atoms.extend(residue.atoms)
            elif residue.is_dummy() and dummy:
                atoms.extend(residue.atoms)
        return atoms

Nose tests outputs are as below:

lightdock.test.bin.test_dna.TestRegressionDNARestraints.test_lightdock_1diz_30_steps_50_glowworms ... usage: lightdock3 [-h] [-f configuration_file] [-s SCORING_FUNCTION]
                  [-sg GSO_SEED] [-t TRANSLATION_STEP] [-r ROTATION_STEP] [-V]
                  [-c CORES] [--profile] [-mpi] [-ns NMODES_STEP] [-min]
                  [--listscoring] [-l SWARM_LIST [SWARM_LIST ...]]
                  setup_file steps
lightdock3: error: argument setup_file: The file does not exist
ERROR
lightdock.test.bin.test_dna.TestRegressionDNAShort.test_lightdock_1diz_10_steps_20_glowworms ... usage: lightdock3 [-h] [-f configuration_file] [-s SCORING_FUNCTION]
                  [-sg GSO_SEED] [-t TRANSLATION_STEP] [-r ROTATION_STEP] [-V]
                  [-c CORES] [--profile] [-mpi] [-ns NMODES_STEP] [-min]
                  [--listscoring] [-l SWARM_LIST [SWARM_LIST ...]]
                  setup_file steps
lightdock3: error: argument setup_file: The file does not exist
ERROR

lightdock.test.bin.test_pydock.TestRegressionPyDockRestraints.test_lightdock_2uuy_20_steps_25_glowworms_rst ... usage: lightdock3 [-h] [-f configuration_file] [-s SCORING_FUNCTION]
                  [-sg GSO_SEED] [-t TRANSLATION_STEP] [-r ROTATION_STEP] [-V]
                  [-c CORES] [--profile] [-mpi] [-ns NMODES_STEP] [-min]
                  [--listscoring] [-l SWARM_LIST [SWARM_LIST ...]]
                  setup_file steps
lightdock3: error: argument setup_file: The file does not exist
ERROR

======================================================================
ERROR: lightdock.test.bin.test_dna.TestRegressionDNARestraints.test_lightdock_1diz_30_steps_50_glowworms
----------------------------------------------------------------------

Traceback (most recent call last):
  File "/home/regen/ana/envs/p8/lib/python3.8/site-packages/nose/case.py", line 197, in runTest
    self.test(*self.arg)
  File "/home/regen/git_develop/lightdock/lightdock/test/bin/test_dna.py", line 81, in test_lightdock_1diz_30_steps_50_glowworms
    assert filecmp.cmp(
  File "/home/regen/ana/envs/p8/lib/python3.8/filecmp.py", line 52, in cmp
    s2 = _sig(os.stat(f2))
FileNotFoundError: [Errno 2] No such file or directory: '/home/regen/git_develop/lightdock/lightdock/test/bin/scratch_dna_restraints/swarm_0/gso_0.out'

======================================================================
ERROR: lightdock.test.bin.test_dna.TestRegressionDNAShort.test_lightdock_1diz_10_steps_20_glowworms
----------------------------------------------------------------------

Traceback (most recent call last):
  File "/home/regen/ana/envs/p8/lib/python3.8/site-packages/nose/case.py", line 197, in runTest
    self.test(*self.arg)
  File "/home/regen/git_develop/lightdock/lightdock/test/bin/test_dna.py", line 41, in test_lightdock_1diz_10_steps_20_glowworms
    assert filecmp.cmp(
  File "/home/regen/ana/envs/p8/lib/python3.8/filecmp.py", line 52, in cmp
    s2 = _sig(os.stat(f2))
FileNotFoundError: [Errno 2] No such file or directory: '/home/regen/git_develop/lightdock/lightdock/test/bin/scratch_dna_short/swarm_0/gso_0.out'

======================================================================
ERROR: lightdock.test.bin.test_pydock.TestRegressionPyDockRestraints.test_lightdock_2uuy_20_steps_25_glowworms_rst
----------------------------------------------------------------------

Traceback (most recent call last):
  File "/home/regen/ana/envs/p8/lib/python3.8/site-packages/nose/case.py", line 197, in runTest
    self.test(*self.arg)
  File "/home/regen/git_develop/lightdock/lightdock/test/bin/test_pydock.py", line 40, in test_lightdock_2uuy_20_steps_25_glowworms_rst
    assert filecmp.cmp(
  File "/home/regen/ana/envs/p8/lib/python3.8/filecmp.py", line 52, in cmp
    s2 = _sig(os.stat(f2))
FileNotFoundError: [Errno 2] No such file or directory: '/home/regen/git_develop/lightdock/lightdock/test/bin/scratch_pydock_restraints/swarm_0/gso_0.out'

I turned lightdock.structure.nm.calculate_nmodes's raise statement to a print statement,the different atoms are:

# 1DIZ_rec
# ... above are same
ARG,56,HB2 ,874 - Atom HB2 (index 874)
ARG,56,HB3 ,875 - Atom HB3 (index 875)
THR,58,N   ,893 - Atom N (index 876)
THR,58,CA  ,894 - Atom CA (index 877)
THR,58,C   ,895 - Atom C (index 878)
THR,58,O   ,896 - Atom O (index 879)
THR,58,CB  ,897 - Atom CB (index 880)
----------
THR,58,OG1 ,898 - Atom CG (index 881)
THR,58,CG2 ,899 - Atom ND1 (index 882)
THR,58,HG21,900 - Atom CD2 (index 883)
THR,58,HG22,901 - Atom CE1 (index 884)
THR,58,HG23,902 - Atom NE2 (index 885)
THR,58,H   ,903 - Atom HE1 (index 886)
THR,58,HG1 ,904 - Atom HD1 (index 887)
THR,58,HB  ,905 - Atom H (index 888)
THR,58,HA  ,906 - Atom HD2 (index 889)
LEU,59,N   ,907 - Atom HA (index 890)
LEU,59,CA  ,908 - Atom HB2 (index 891)
LEU,59,C   ,909 - Atom HB3 (index 892)
LEU,59,O   ,910 - Atom N (index 893)
LEU,59,CB  ,911 - Atom CA (index 894)
LEU,59,CG  ,912 - Atom C (index 895)
LEU,59,CD1 ,913 - Atom O (index 896)
LEU,59,CD2 ,914 - Atom CB (index 897)
LEU,59,HD21,915 - Atom OG1 (index 898)
LEU,59,HD22,916 - Atom CG2 (index 899)
LEU,59,HD23,917 - Atom HG21 (index 900)
LEU,59,H   ,918 - Atom HG22 (index 901)
LEU,59,HD11,919 - Atom HG23 (index 902)
LEU,59,HD12,920 - Atom H (index 903)
LEU,59,HD13,921 - Atom HG1 (index 904)
LEU,59,HA  ,922 - Atom HB (index 905)
LEU,59,HG  ,923 - Atom HA (index 906)
LEU,59,HB2 ,924 - Atom N (index 907)
LEU,59,HB3 ,925 - Atom CA (index 908)
ILE,61,N   ,943 - Atom C (index 909)
ILE,61,CA  ,944 - Atom O (index 910)
ILE,61,C   ,945 - Atom CB (index 911)
...

If I

  1. disable lightdock.structure.nm.calculate_nmodes's raise statement,or
  2. delete the added brackets in lightdock.structure.complex.Complex.get_atoms

all tests passed,but they don't solve the actual problem either.

As I'm not familar with prody's behavior,I'm not sure what's the cause of this bug.

Expected behavior

After adding brackets in lightdock.structure.complex.Complex.get_atoms defination,all tests should pass.

Screenshots

bug

Desktop (please complete the following information):

  • OS: manjaro
  • python 3.8

Scoring functions supporting ANM

To avoid confusion, raising a warning to the user when a scoring function incompatible with ANM is used with the -anm flag would be necessary.

Support for multiple chains in lgd_filter_restraints.py

Describe the bug
lgd_filter_restraints.py is not managing multiple chains for receptor or ligand

To Reproduce
Using multiple chains instead of a single chain:

lgd_filter_restraints.py --cutoff 5.0 --fnat 0.4 rank_by_scoring.list restraints.list H,L A,B

Expected behavior
Selecting in ProDy multiple chains for this script to work OK.

Lightdock prody dependency Issue

Attempting to install Lightdock using pip, automatically installs the prody dependency. However, the newest version of prody (2.0.2) causes issues with Lightdock, specifically the generation of swarm starting positions.

using pip to install prody (2.0.1) resolves this issue.

Ubuntu 20.04

Tutorials for lightdock 0.9.3 is needed.

Hello there!

Lightdock has updated to 0.9.3 and added the new -spr parameter and rewrited the implementation of creating swarms.

However,the tutorials have not updated to 0.9.3 and the different result may confuse beginners.

Also,using restraints now makes starting_points.py ignoring the -s flag,while the help information of lightdock3_setup didn't say that,which may confuse beginners too.

Selection does not work on Mac

Describe the bug
All sorts of selection aren't shown on the 3D view screen on Mac. Neither v1.3, nor the daily build. However, works fine on linux

To Reproduce
Open a pdb. Menu "Select" "Chain" "...".

Expected behavior
similar to linux - the selected resedues shown on 3D image.

Screenshots

Desktop (please complete the following information):

  • Mac OS 12.1 (Intel)

Additional context

Try to dock AMP (adenosine monophosphate) to a ssDNA

Hello!

Describe the bug
I was trying to dock a small molecule (adenosine monophosphate, ie, AMP) to a ssDNA molecule using LightDock/0.9.0 but I could not get any "gso_{}.out" or "lightdock_{}.pdb" files in each "swarm_{}" folder, as shown in the screenshot. Therefore no final docked structure.

In each cluster_lightdock.list file, it says:

[lgd_cluster_bsas] ERROR: Clustering has failed. Please see error:
[lgd_cluster_bsas] ERROR: [Errno 2] No such file or directory: 'gso_500.out'

Screenshots
image

Desktop (please complete the following information):

  • OS: Linux
  • Version: Rocky Linux 8.5 (Green Obsidian)

Additional context
Please see the PDB files for ssDNA and AMP in the attached .zip file below.

Thank you very much!

DNA_AMP.zip

lightdock pdb file visualises incorrectly in pymol

Describe the bug
I ran lightdock on two proteins following the simple docking tutorial (https://lightdock.org/tutorials/0.9.3/simple_docking. All the steps ran successfully, but when I open de best scoring PDB file (or any for that matter) it does not show like a molecule (see screenshots below).

Expected behavior
I expect a docked visualization of the two proteins, like in the tutorial

Screenshots
example

Desktop (please complete the following information):

  • OS: ubuntu 20.04.5 LTS
  • lightdock version 0.9.3

Test files missing

Describe the bug
I am running nose tests for lightdock v0.9.2. A lot of tests fail with No such file or directory, citing various nonexistent directories under lightdock/test/bin/, for example, scratch_dfire_short or scratch_dfire2_restraints.

To Reproduce

cd lightdock && nosetests3

Expected behavior
Tests pass.

Desktop:

  • OS: Debian
  • Version: Unstable

PDB parser fails when two residues with same name but different insertion code

Describe the bug
When two residues within the same chain have identical name and number, but different insertion code, only one residue is recognized.

To Reproduce
Test with the following PDB data:

SER.100     N  63.697  18.858   8.922
SER.100    CA  64.214  18.347  10.208
SER.100     C  63.994  19.186  11.496
SER.100     O  64.967  19.342  12.281
SER.100    CB  65.719  18.133  10.098
SER.100    OG  66.067  17.615   8.834
SER.100A     N  62.784  19.704  11.756
SER.100A    CA  62.610  20.562  12.938
SER.100A     C  61.241  20.555  13.618
SER.100A     O  60.255  20.108  13.053
SER.100A    CB  62.988  21.989  12.597
SER.100A    OG  62.111  22.508  11.612

Expected behavior
Two different residues should be recognized.

Much larger number of swarms in restraints tutorial than shown in docs

Problem

I was following your restraints tutorial and ran the lightdock3_setup.py command with the same flags as the tutorial. In the tutorial it says 'the default number of swarms (400) has been reduced to 55'. When I look at the output from the setup command, I see that the number of swarms is much larger than this (400 it seems).

It would be good if I could get the number of swarms down to 55 as the memory requirements of 400 swarms is overwhelming my machine!

Many thanks!

Example output

$ lightdock3_setup.py 4G6M_rec.pdb 4G6M_lig.pdb --noxt --noh --now -anm -rst restraints.list
[lightdock3_setup] INFO: Ignoring OXT atoms
[lightdock3_setup] INFO: Ignoring Hydrogen atoms
[lightdock3_setup] INFO: Ignoring water
[lightdock3_setup] INFO: Reading structure from 4G6M_rec.pdb PDB file...
[lightdock3_setup] INFO: 1782 atoms, 230 residues read.
[lightdock3_setup] INFO: Ignoring OXT atoms
[lightdock3_setup] INFO: Ignoring Hydrogen atoms
[lightdock3_setup] INFO: Ignoring water
[lightdock3_setup] INFO: Reading structure from 4G6M_lig.pdb PDB file...
[lightdock3_setup] INFO: 1194 atoms, 149 residues read.
[lightdock3_setup] INFO: Calculating reference points for receptor 4G6M_rec.pdb...
[lightdock3_setup] INFO: Reference points for receptor found, skipping
[lightdock3_setup] INFO: Done.
[lightdock3_setup] INFO: Calculating reference points for ligand 4G6M_lig.pdb...
[lightdock3_setup] INFO: Reference points for ligand found, skipping
[lightdock3_setup] INFO: Done.
[lightdock3_setup] INFO: Saving processed structure to PDB file...
[lightdock3_setup] INFO: Done.
[lightdock3_setup] INFO: Saving processed structure to PDB file...
[lightdock3_setup] INFO: Done.
[lightdock3_setup] INFO: Calculating ANM for receptor molecule...
[lightdock3_setup] INFO: 10 normal modes calculated
[lightdock3_setup] INFO: Calculating ANM for ligand molecule...
[lightdock3_setup] INFO: 10 normal modes calculated
[lightdock3_setup] INFO: Reading restraints from restraints.list
[lightdock3_setup] INFO: Number of receptor restraints is: 20 (active), 0 (passive)
[lightdock3_setup] INFO: Number of ligand restraints is: 21 (active), 0 (passive)
[lightdock3_setup] INFO: Calculating starting positions...
[lightdock3_setup] INFO:   * Surface density: TotalSASA/50.00
[lightdock3_setup] INFO:   * Swarm radius: 10.00 Å
[lightdock3_setup] INFO:   * 180° flip of 50% of starting poses: False
[lightdock3_setup] INFO:   * Ligand Max Diameter: 45.86 Å
[lightdock3_setup] INFO:   * Surface distance: 11.47 Å
[lightdock3_setup] INFO: Swarms after incompatible filter: 592
[lightdock3_setup] INFO: Swarms after interior points filter: 507
[lightdock3_setup] INFO: Swarms after occlusion filter: 467
[lightdock3_setup] INFO: Generated 400 positions files
[lightdock3_setup] INFO: Done.
[lightdock3_setup] INFO: Number of calculated swarms is 400
[lightdock3_setup] INFO: Preparing environment
[lightdock3_setup] INFO: Done.
[lightdock3_setup] INFO: LightDock setup OK

I am using Lightdock 0.9.4 (python version not rust)

Environment

anyio==4.2.0
argon2-cffi==23.1.0
argon2-cffi-bindings==21.2.0
arrow==1.3.0
asttokens==2.4.1
async-lru==2.0.4
attrs==23.2.0
Babel==2.14.0
beautifulsoup4==4.12.2
biopython==1.79
bleach==6.1.0
certifi==2023.11.17
cffi==1.16.0
charset-normalizer==3.3.2
comm==0.2.1
Cython==3.0.8
debugpy==1.8.0
decorator==5.1.1
defusedxml==0.7.1
exceptiongroup==1.2.0
executing==2.0.1
fastjsonschema==2.19.1
fqdn==1.5.1
freesasa==2.2.1
idna==3.6
ipykernel==6.28.0
ipython==8.20.0
isoduration==20.11.0
jedi==0.19.1
Jinja2==3.1.3
json5==0.9.14
jsonpointer==2.4
jsonschema==4.20.0
jsonschema-specifications==2023.12.1
jupyter-events==0.9.0
jupyter-lsp==2.2.1
jupyter_client==8.6.0
jupyter_core==5.7.1
jupyter_server==2.12.4
jupyter_server_terminals==0.5.1
jupyterlab==4.0.10
jupyterlab_pygments==0.3.0
jupyterlab_server==2.25.2
lightdock==0.9.4
MarkupSafe==2.1.3
matplotlib-inline==0.1.6
mistune==3.0.2
nbclient==0.9.0
nbconvert==7.14.1
nbformat==5.9.2
nest-asyncio==1.5.8
notebook_shim==0.2.3
numpy==1.23.5
overrides==7.4.0
packaging==23.2
pandocfilters==1.5.0
parso==0.8.3
pdb-tools==2.5.0
pexpect==4.9.0
platformdirs==4.1.0
ProDy==2.4.1
prometheus-client==0.19.0
prompt-toolkit==3.0.43
psutil==5.9.7
ptyprocess==0.7.0
pure-eval==0.2.2
py3Dmol==2.0.4
pycparser==2.21
Pygments==2.17.2
pyparsing==3.1.1
python-dateutil==2.8.2
python-json-logger==2.0.7
PyYAML==6.0.1
pyzmq==25.1.2
referencing==0.32.1
requests==2.31.0
rfc3339-validator==0.1.4
rfc3986-validator==0.1.1
rpds-py==0.16.2
scipy==1.11.4
Send2Trash==1.8.2
six==1.16.0
sniffio==1.3.0
soupsieve==2.5
stack-data==0.6.3
terminado==0.18.0
tinycss2==1.2.1
tomli==2.0.1
tornado==6.4
traitlets==5.14.1
types-python-dateutil==2.8.19.20240106
typing_extensions==4.9.0
uri-template==1.3.0
urllib3==2.1.0
wcwidth==0.2.13
webcolors==1.13
webencodings==0.5.1
websocket-client==1.7.0

Freezes after a while

My protein-DNA docking analyses freeze/timeout after just under 400 swarms every time. I am following the protein-DNA docking tutorial.

LightDock setup failure - Found wrong coefficient on calculating poses with restraints

Greetings,

I've been running LightDock successfully with my files but there is a ligand that fails to work whenever I define restraints. I did not change anything else but the ligand PDB file and the restraints file content, yet i get the following errors at the end of lightdock3_setup.py:

INFO: Calculating starting positions...
ERROR: LightDock setup failed. Please see:
ERROR: [LightDockWarning] Found wrong coefficient on calculating poses with restraints

I fail to detect the problem and I tried everything from shortening the PDB ligand structure, redoing the restraints file, running less swarms or steps, deactivating flexibility... Only removing the restraints fixes it, obviously.

Here I provide a zip file with the receptor (HER2noH) and ligand (EM1noH) PDB files with H removed, the restraints file, and the .sh script I call using "bash". I am working using Ubuntu in WSL2 environment from Windows 10. As I said, I have been successful in using restraints with other ligands and receptors using the same environment and script.

Could you help shed some light onto this issue? Maybe some specific way to figure out where the error appears exactly? Many thanks.

Best,
Eloi Parladé.

support.zip

TOBI scoring function fails to replicate results with CCharPPI server

Hi LightDock devs! I have been trying out some of the LightDock scoring function implementation throught the lgd_calculate_scoring.py script. I focused mainly on the PISA and TOBI scoring functions. To test them, I haver used the following benchmark set for Ab-Ag docking/binding, from Ref. Structure 29, 606–621, 2021. I compared values obtained from lgd_calculate_scoring.py and the CCharPPI webserver (https://life.bsc.es/pid/ccharppi), comparing

  • PISA (LightDock) vs AP_PISA (CCharPPI)
  • TOBI (LightDock) vs AP_T2 (CCharPPI)

Here are the results
Screenshot 2023-05-08 at 09 22 39
Screenshot 2023-05-08 at 09 22 47

It seems that PISA values are well reproduced, but not TOBI. I have not done the test for the other scoring functions, but it may be relevant to check them together with the authors of CCharPPI. Thank you very much!

Performance for protein-DNA docking

Has there been done research into the accuracy of Lightdock for protein-DNA docking compared to ie. HADDOCK, RosETTAFold2NA, etc.? I have found comparisons regarding protein-protein docking, but not protein-DNA. Also, what are the pros and cons of the Lightdock alghorithm compared to other softwares?

Lightdock in google colab

Dear collaborators,
I have installed the lightdock in google colab. It is working fine, excluding the cluster analysis.
In the cluster analysis, I add the command:

!lgd_cluster_bsas.py swarm_37/gso_10.out

The swarm 37 was the one with the lowest interaction energy. And, I have generated 10 conformations that are located in the directory /swarm_37/
Unfortunately, after running the cluster analysis with the above command, the error message is:

/usr/local/lib/python3.6/dist-packages/Bio/SubsMat/init.py:131: BiopythonDeprecationWarning: Bio.SubsMat has been deprecated, and we intend to remove it in a future release of Biopython. As an alternative, please consider using Bio.Align.substitution_matrices as a replacement, and contact the Biopython developers if you still need the Bio.SubsMat module.
BiopythonDeprecationWarning,
[lgd_cluster_bsas] INFO: Reading CA from lightdock_17.pdb
[lgd_cluster_bsas] ERROR: Error found reading a structure: lightdock_17.pdb is not a valid filename or a valid PDB identifier.
[lgd_cluster_bsas] ERROR: Did you generate the LightDock structures corresponding to this output file?

I do not understand why lightdock is trying to find the file lightdock_17.pdb because I only generate 10 conformations.

Does anyone suggest any action to solve this issue?

Thanks in advance.
Andre Pimentel

Is it possible to dock protein-ligand complexes?

Hello,

We are quite interested in this repo as we are looking for alternatives for Rosetta protein-protein docking module. Here are two issues that we are most concerned about after using Lightdock:
(1) Is it possible for us to dock protein-ligand complexes together? As our tasks are related to PROTAC modeling, it would be better for us to dock the complexes than just the 'apo' structures. However, it seems currently Lightdock only allows standard residue names, so we could only use the constraint file to make the docking surface close to what we wanted, but there were still many models in which the anchor atoms faced the opposite position.
(2) We wonder which parameters might help reduce the clashes of the protein-protein surface. We could see a lot of severe clashes between the receptor protein and the ligand protein from the results. Are there related parameters during the steps that might help to fix them?

Thanks a lot

Missing import and incorrect function call signature in `lightdock/simulation/docking_mpi.py`

Describe the bug

The lightdock/simulation/docking_mpi.py module is:

  • Missing the DEFAULT_LIGHTDOCK_PREFIX import, causing NameError issues in lines 111 and 114;
    from lightdock.constants import DEFAULT_SCORING_FUNCTION, DEFAULT_SWARM_FOLDER, \
    DEFAULT_REC_NM_FILE, DEFAULT_LIG_NM_FILE, NUMPY_FILE_SAVE_EXTENSION, \
    DEFAULT_NMODES_REC, DEFAULT_NMODES_LIG

    # Read input structures (use parsed ones)
    parsed_lightdock_receptor = os.path.join(os.path.dirname(args.receptor_pdb),
    DEFAULT_LIGHTDOCK_PREFIX % os.path.basename(args.receptor_pdb))
    receptor = read_input_structure(parsed_lightdock_receptor, args.noxt, args.noh, args.verbose_parser)
    parsed_lightdock_ligand = os.path.join(os.path.dirname(args.ligand_pdb),
    DEFAULT_LIGHTDOCK_PREFIX % os.path.basename(args.ligand_pdb))
  • Missing the final anm_rec and anm_lig arguments to pass to gso = builder.create_from_file, causing TypeError issues.
    gso = builder.create_from_file(number_of_glowworms, random_number_generator, gso_parameters,
    adapters, scoring_functions, bounding_box, initial_positions,
    step_translation, step_rotation, nmodes_step, local_minimization)

    def create_from_file(self, number_of_glowworms, random_number_generator, gso_parameters,
    adapters, scoring_functions, bounding_box, initial_population_file,
    step_translation, step_rotation, step_nmodes, local_minimization,
    anm_rec, anm_lig):

Expected behavior

Changing this script to look like lightdock/simulation/docking_multiprocessing.py works:

from lightdock.constants import DEFAULT_SCORING_FUNCTION, DEFAULT_SWARM_FOLDER, \
DEFAULT_REC_NM_FILE, DEFAULT_LIG_NM_FILE, NUMPY_FILE_SAVE_EXTENSION, \
DEFAULT_NMODES_REC, DEFAULT_NMODES_LIG, DEFAULT_LIGHTDOCK_PREFIX

gso = builder.create_from_file(number_of_glowworms, random_number_generator, gso_parameters,
adapters, scoring_functions, bounding_box, initial_positions,
step_translation, step_rotation, nmodes_step, local_minimization,
anm_rec, anm_lig)

Support for non standard amino acids

Hello.
Thanks for this awesome work.

I am wondering if there is a way to use non-standard amino acids with lightdock.
I am looking at methylated side chains right now, but I am trying to understand if there is a standard way to add support for more radical modifications.
I would be really grateful for any suggestions.

Best,
Amin,

Improve error messages on not supported type

When a scoring function does not support a given atom or residue type, scoring function usually fails with a cryptic message. This could be improved capturing non supported types.

help with multiple scorings

Dear @brianjimenez ,
On the simulation step, im trying to combine 2 scoring functions, using a scoring.conf file as follow:
sipper 0.8
fastdfire 0.5

The problem is im getting the following errors:
Captura de pantalla 2019-12-17 a las 18 42 49

edit: I found it also happens using sipper alone.

Script for creating a CG membrane from structure and residue

It would be desirable to have a script in LightDock to build fake coarse-grained membranes using as an input a PDB structure and a residue from which the fake membrane would be built.

Result might look like this:

membrane

These generated membranes would be compatible with the membrane protocol already in place and an alternative for structures where there is no simulation available in MemProtMD.

Question about the treatment of protein-ligand docking.

Hi,
it is possible to use lightdock for ligand-receptor docking when in the active site
or docking box are present metal bivalent ions such as MGs or CAs?

In the case of my interest I have two Mgs ions in the active site.

Thanks.

Saverio

¿ Se puede utilizar LightDock para "protein - ligand docking" ?

Buenas, señor Jiménez.

Yo intentaba unas simulaciones de "docking" entre proteins y ligands. Ejemplos de "Tutorials" (https://lightdock.org/tutorials/0.9.2/index.html) los pude hacer más o menos bien.

Sin embargo, al intentar unas simulaciónes, no las pude.

Por esta página japonesa (https://qiita.com/kuro3210/items/a78cf96605f8ddd954f7) , intenté "docking simulation" de entre 2gz7 sin d3f (ligand) y d3f con LightDock.

  1. descargué 2gz7.pdb de PDB
  2. Por PyMol "remove solven" , elegí d3f , "remove sel" , y guardé file como "2gz7_sin_lig.pdb"
  3. Otro, d3f.pdb lo también guardé
    4a. Por LightDock , "lightdock3_setup.py 2gz7_sin_lig.pdb d3f.pdb --noxt --noh --now -anm"
    Y , LightDock me dijo "Error selecting backbone atoms (protein or nucleic)"

Así que

4b. "lightdock3_setup.py -s 200 2gz7_sin_lig.pdb d3f.pdb --noxt --noh --now"
5a. "lightdock3.py setup.json 100"
Y, LightDock me dijo
"[pdb] WARNING: Possible problem: [ResidueNonStandardError] Can not check non-standard residue D3F.307"
y
"Residue A.D3F.307 or atom CL1 not supported. DFIRE only supports standard aminoacids without hydrogens.".

Así que
5b. "lightdock3.py -s mj3h setup.json 100"
6. Por este página japonesa (https://hira-labo.com/archives/348) , modifiqué "analysis.sh" como
../4G6M_rec.pdb ../4G6M_lig.pdb => ../2gz7_sin_lig.pdb ../d3f.pdb
-c 8 => lo borré
y

Filtering models by >40% of satisfied restraints

lgd_filter_restraints.py --cutoff 5.0 --fnat 0.4 rank_by_scoring.list restraints.list A B > /dev/null 2> /dev/null;
=> lo borré

  1. ./analysis.sh

Sin embargo, después de calculacíon, en "rank_by_*.list" todo "scoring"s son 0.000.
También, al hacer simulación en "7bf6.pdb" y su ligand "u08.pdb" , scorings son 0.000.

¿ LightDock , no lo puedo utilizar para "protein - ligand (que se hice de solo única molécula) docking" ?

Y otros unos.
Intentaba similar proceso en "pyDock web" y "LightDock server" , pero ellos me dijeron "No atoms found. Please check it is a correct PDB file" , "No protein found in PDB " ...

¿ Yo intento hacer unos locuros ?

Si me responda, estoy contento.

Un saludo

Unexpected keyword argument 'seed'

unexpected keyword argument 'seed'
While running lightdock3_setup.py, the process stops with following error:
.../Bio/pairwise2.py:278: BiopythonDeprecationWarning: Bio.pairwise2 has been deprecated, and we intend to remove it in a future release of Biopython. As an alternative, please consider using Bio.Align.PairwiseAligner as a replacement, and contact the Biopython developers if you still need the Bio.pairwise2 module. warnings.warn( [lightdock3_setup] INFO: Ignoring OXT atoms [lightdock3_setup] INFO: Ignoring Hydrogen atoms [lightdock3_setup] INFO: Ignoring water [lightdock3_setup] INFO: Reading structure from 2UUY_rec.pdb PDB file... [lightdock3_setup] INFO: 1628 atoms, 223 residues read. [lightdock3_setup] INFO: Ignoring OXT atoms [lightdock3_setup] INFO: Ignoring Hydrogen atoms [lightdock3_setup] INFO: Ignoring water [lightdock3_setup] INFO: Reading structure from 2UUY_lig.pdb PDB file... [lightdock3_setup] INFO: 415 atoms, 55 residues read. [lightdock3_setup] INFO: Calculating reference points for receptor 2UUY_rec.pdb... [lightdock3_setup] INFO: Reference points for receptor found, skipping [lightdock3_setup] INFO: Done. [lightdock3_setup] INFO: Calculating reference points for ligand 2UUY_lig.pdb... [lightdock3_setup] INFO: Reference points for ligand found, skipping [lightdock3_setup] INFO: Done. [lightdock3_setup] INFO: Saving processed structure to PDB file... [lightdock3_setup] INFO: Done. [lightdock3_setup] INFO: Saving processed structure to PDB file... [lightdock3_setup] INFO: Done. [lightdock3_setup] INFO: Calculating ANM for receptor molecule... [lightdock3_setup] INFO: 10 normal modes calculated [lightdock3_setup] INFO: Calculating ANM for ligand molecule... [lightdock3_setup] INFO: 10 normal modes calculated [lightdock3_setup] INFO: Calculating starting positions... [lightdock3_setup] INFO: * Surface density: TotalSASA/50.00 [lightdock3_setup] INFO: * Swarm radius: 10.00 Å [lightdock3_setup] INFO: * 180° flip of 50% of starting poses: False [lightdock3_setup] INFO: * Ligand Max Diameter: 39.05 Å [lightdock3_setup] INFO: * Surface distance: 9.76 Å Traceback (most recent call last): File "/home/randd/.local/bin/lightdock3_setup.py", line 142, in <module> starting_points_files = calculate_starting_positions( File ".../lightdock/prep/simulation.py", line 191, in calculate_starting_positions starting_points_files = calculate_initial_poses( File ".../lightdock/prep/poses.py", line 492, in calculate_initial_poses swarm_centers, receptor_diameter, ligand_diameter = calculate_surface_points( File ".../lightdock/prep/starting_points.py", line 156, in calculate_surface_points surface_clusters = kmeans2(data=coords, k=num_points, minit="points", seed=seed, iter=100) TypeError: kmeans2() got an unexpected keyword argument 'seed'

Upon clearing that error by changing the variable seed name at line number 70 to spseed on file ".../lightdock/prep/starting_points.py" , I got another error given below:

Traceback (most recent call last): File ".../.local/bin/lightdock3_setup.py", line 142, in <module> starting_points_files = calculate_starting_positions( File ".../.local/lib/python3.8/site-packages/lightdock/prep/simulation.py", line 191, in calculate_starting_positions starting_points_files = calculate_initial_poses( File ".../lightdock/prep/poses.py", line 492, in calculate_initial_poses swarm_centers, receptor_diameter, ligand_diameter = calculate_surface_points( TypeError: calculate_surface_points() got an unexpected keyword argument 'seed'

I fixed it by commented the line 500 on the ".../lightdock/prep/poses.py"

But stillI got the previous error, in file ".../lightdock/prep/starting_points.py", upon which I removed the amends i Made, and commented or removed the seed parameter which is being passed to kmeans2() function on wherever it is called ( lines : 156, 251 ), And now it generates all files perfectly, and completes the setup.

To Reproduce
Hmm.. Nothing to reproduce, I have explained it above.

Expected behavior
I made it work as expected. Here is the expected behaviour:

`randd  …/ProteinSynth/Protprotdocki/test  ♥ 10:51  lightdock3_setup.py 2UUY_rec.pdb 2UUY_lig.pdb --noxt -noh --now -anm/home/randd/.local/lib/python3.8/site-packages/Bio/pairwise2.py:278: BiopythonDeprecationWarning: Bio.pairwise2 has been deprecated, and we intend to remove it in a future release of Biopython. As an alternative, please consider using Bio.Align.PairwiseAligner as a replacement, and contact the Biopython developers if you still need the Bio.pairwise2 module.
warnings.warn(
[lightdock3_setup] INFO: Ignoring OXT atoms
[lightdock3_setup] INFO: Ignoring Hydrogen atoms
[lightdock3_setup] INFO: Ignoring water
[lightdock3_setup] INFO: Reading structure from 2UUY_rec.pdb PDB file...
[lightdock3_setup] INFO: 1628 atoms, 223 residues read.
[lightdock3_setup] INFO: Ignoring OXT atoms
[lightdock3_setup] INFO: Ignoring Hydrogen atoms
[lightdock3_setup] INFO: Ignoring water
[lightdock3_setup] INFO: Reading structure from 2UUY_lig.pdb PDB file...
[lightdock3_setup] INFO: 415 atoms, 55 residues read.
[lightdock3_setup] INFO: Calculating reference points for receptor 2UUY_rec.pdb...
[lightdock3_setup] INFO: Reference points for receptor found, skipping
[lightdock3_setup] INFO: Done.
[lightdock3_setup] INFO: Calculating reference points for ligand 2UUY_lig.pdb...
[lightdock3_setup] INFO: Reference points for ligand found, skipping
[lightdock3_setup] INFO: Done.
[lightdock3_setup] INFO: Saving processed structure to PDB file...
[lightdock3_setup] INFO: Done.
[lightdock3_setup] INFO: Saving processed structure to PDB file...
[lightdock3_setup] INFO: Done.
[lightdock3_setup] INFO: Calculating ANM for receptor molecule...
[lightdock3_setup] INFO: 10 normal modes calculated
[lightdock3_setup] INFO: Calculating ANM for ligand molecule...
[lightdock3_setup] INFO: 10 normal modes calculated
[lightdock3_setup] INFO: Calculating starting positions...
[lightdock3_setup] INFO: * Surface density: TotalSASA/50.00
[lightdock3_setup] INFO: * Swarm radius: 10.00 Å
[lightdock3_setup] INFO: * 180° flip of 50% of starting poses: False
[lightdock3_setup] INFO: * Ligand Max Diameter: 39.05 Å
[lightdock3_setup] INFO: * Surface distance: 9.76 Å
[lightdock3_setup] INFO: Swarms after incompatible filter: 911
[lightdock3_setup] INFO: Swarms after interior points filter: 911
[lightdock3_setup] INFO: Generated 182 positions files
[lightdock3_setup] INFO: Done.
[lightdock3_setup] INFO: Number of calculated swarms is 182
[lightdock3_setup] INFO: Preparing environment
[lightdock3_setup] INFO: Done.
[lightdock3_setup] INFO: LightDock setup OK

randd  …/ProteinSynth/Protprotdocki/test  ♥ 10:51  ls
2UUY_lig.pdb swarm_1 swarm_109 swarm_119 swarm_129 swarm_139 swarm_149 swarm_159 swarm_169 swarm_179 swarm_25 swarm_35 swarm_45 swarm_55 swarm_65 swarm_75 swarm_85 swarm_95
2UUY_rec.pdb swarm_10 swarm_11 swarm_12 swarm_13 swarm_14 swarm_15 swarm_16 swarm_17 swarm_18 swarm_26 swarm_36 swarm_46 swarm_56 swarm_66 swarm_76 swarm_86 swarm_96
init swarm_100 swarm_110 swarm_120 swarm_130 swarm_140 swarm_150 swarm_160 swarm_170 swarm_180 swarm_27 swarm_37 swarm_47 swarm_57 swarm_67 swarm_77 swarm_87 swarm_97
lightdock_2UUY_lig_mask.npy swarm_101 swarm_111 swarm_121 swarm_131 swarm_141 swarm_151 swarm_161 swarm_171 swarm_181 swarm_28 swarm_38 swarm_48 swarm_58 swarm_68 swarm_78 swarm_88 swarm_98
lightdock_2UUY_lig.pdb swarm_102 swarm_112 swarm_122 swarm_132 swarm_142 swarm_152 swarm_162 swarm_172 swarm_19 swarm_29 swarm_39 swarm_49 swarm_59 swarm_69 swarm_79 swarm_89 swarm_99
lightdock_2UUY_rec_mask.npy swarm_103 swarm_113 swarm_123 swarm_133 swarm_143 swarm_153 swarm_163 swarm_173 swarm_2 swarm_3 swarm_4 swarm_5 swarm_6 swarm_7 swarm_8 swarm_9
lightdock_2UUY_rec.pdb swarm_104 swarm_114 swarm_124 swarm_134 swarm_144 swarm_154 swarm_164 swarm_174 swarm_20 swarm_30 swarm_40 swarm_50 swarm_60 swarm_70 swarm_80 swarm_90
lightdock_lig.nm.npy swarm_105 swarm_115 swarm_125 swarm_135 swarm_145 swarm_155 swarm_165 swarm_175 swarm_21 swarm_31 swarm_41 swarm_51 swarm_61 swarm_71 swarm_81 swarm_91
lightdock_rec.nm.npy swarm_106 swarm_116 swarm_126 swarm_136 swarm_146 swarm_156 swarm_166 swarm_176 swarm_22 swarm_32 swarm_42 swarm_52 swarm_62 swarm_72 swarm_82 swarm_92
setup.json swarm_107 swarm_117 swarm_127 swarm_137 swarm_147 swarm_157 swarm_167 swarm_177 swarm_23 swarm_33 swarm_43 swarm_53 swarm_63 swarm_73 swarm_83 swarm_93
swarm_0 swarm_108 swarm_118 swarm_128 swarm_138 swarm_148 swarm_158 swarm_168 swarm_178 swarm_24 swarm_34 swarm_44 swarm_54 swarm_64 swarm_74 swarm_84 swarm_94

randd  …/ProteinSynth/Protprotdocki/test  ♥ 10:51  lightdock3.py setup.json 100 -c 1 -l 0/home/randd/.local/lib/python3.8/site-packages/Bio/pairwise2.py:278: BiopythonDeprecationWarning: Bio.pairwise2 has been deprecated, and we intend to remove it in a future release of Biopython. As an alternative, please consider using Bio.Align.PairwiseAligner as a replacement, and contact the Biopython developers if you still need the Bio.pairwise2 module.
warnings.warn(
[lightdock] INFO: simulation parameters saved to lightdock.info
[lightdock3_setup] INFO: Ignoring OXT atoms
[lightdock3_setup] INFO: Ignoring Hydrogen atoms
[lightdock3_setup] INFO: Ignoring water
[lightdock3_setup] INFO: Reading structure from lightdock_2UUY_rec.pdb PDB file...
[lightdock3_setup] INFO: 1628 atoms, 223 residues read.
[lightdock3_setup] INFO: Ignoring OXT atoms
[lightdock3_setup] INFO: Ignoring Hydrogen atoms
[lightdock3_setup] INFO: Ignoring water
[lightdock3_setup] INFO: Reading structure from lightdock_2UUY_lig.pdb PDB file...
[lightdock3_setup] INFO: 415 atoms, 55 residues read.
[lightdock] INFO: Loading scoring function...
[lightdock] INFO: Using DFIRE scoring function
[lightdock] INFO: Done.
[kraken] INFO: Kraken has 1 tentacles (cpu cores)
[kraken] INFO: Tentacle ready with 1 tasks
[kraken] INFO: 1 ships ready to be smashed
[lightdock] INFO: Monster spotted
[kraken] INFO: Release the Kraken!
[0] step 1
[0] step 2
[0] step 3
[0] step 4
[0] step 5
[0] step 6
[0] step 7
[0] step 8
[0] step 9
[0] step 10
[0] step 11
[0] step 12
[0] step 13
[0] step 14
[0] step 15
[0] step 16
[0] step 17
[0] step 18
[0] step 19
[0] step 20
[0] step 21
[0] step 22
[0] step 23
[0] step 24
[0] step 25
[0] step 26
[0] step 27
[0] step 28
[0] step 29
[0] step 30
[0] step 31
[0] step 32
[0] step 33
[0] step 34
[0] step 35
[0] step 36
[0] step 37
[0] step 38
[0] step 39
[0] step 40
[0] step 41
[0] step 42
[0] step 43
[0] step 44
[0] step 45
[0] step 46
[0] step 47
[0] step 48
[0] step 49
[0] step 50
[0] step 51
[0] step 52
[0] step 53
[0] step 54
[0] step 55
[0] step 56
[0] step 57
[0] step 58
[0] step 59
[0] step 60
[0] step 61
[0] step 62
[0] step 63
[0] step 64
[0] step 65
[0] step 66
[0] step 67
[0] step 68
[0] step 69
[0] step 70
[0] step 71
[0] step 72
[0] step 73
[0] step 74
[0] step 75
[0] step 76
[0] step 77
[0] step 78
[0] step 79
[0] step 80
[0] step 81
[0] step 82
[0] step 83
[0] step 84
[0] step 85
[0] step 86
[0] step 87
[0] step 88
[0] step 89
[0] step 90
[0] step 91
[0] step 92
[0] step 93
[0] step 94
[0] step 95
[0] step 96
[0] step 97
[0] step 98
[0] step 99
[0] step 100
[kraken] INFO: folding tentacle Tentacle-1
[kraken] INFO: 1 ships destroyed
[lightdock] INFO: Finished.`

Screenshots
I don't have time to add screenshot now. just came to inform the community about this.

Desktop :

  • OS: Ubuntu
  • Version 20.04.1

Additional context
Nothing

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.