Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reactive Docking - *.maps.fld is not generated and does not exist #79

Closed
guzh970630 opened this issue Nov 25, 2023 · 6 comments
Closed

Comments

@guzh970630
Copy link

Hello,
I'm a doctoral student. I ran the Auto-gpu, but there was a problem.
"Error: Can't open fld file *.maps.fld.
Error: get_gridinfo failed with fld file specified with parameter at *_config:2."
I found that there is no *.maps.fld in generated files through mk_prepare_rector.py.
Currently, the generated receptor files are: *.reactive_config, *_flex.pdbqt, *_rigid.gpf, *_rigid.gpf.pdb and *_rigid.pdbqt. I want to konw how to generate *.maps.fld.
Thanks

@diogomart
Copy link
Contributor

@guzh970630
Copy link
Author

guzh970630 commented Nov 26, 2023

Hello,
I'm sorry. I still haven't solved my problem.
The article I refer to is "Reactive Docking: A Computational Method for High-Throughput Virtual Screenings of Reactive Species"
I want to perform the “Reactive Docking”.
I have completed the first four steps in Reactive Docking. I've got the files *.reactive_config, *_flex.pdbqt, *_rigid.gpf, *_rigid.gpf.pdb, *rigid.pdbqt and .pdbqt.
I'm going to the "Configure AD-GPU for reactive docking".
Then I followed the prompt on github "ADGPU -I *.reactive_config -L sufex1.pdbqt -N sufex1_docked -F *_flex.pdbqt -C 1"

Found
"Error: Can't open fld file *.maps.fld.
Error: get_gridinfo failed with fld file specified with parameter at *_config:2."

Because there is no file input about ".maps.fld" in the command, and ".maps.fld" is not generated before.
Can you tell me why I get an error when I run Autodock-gpu with this command, and how I should change the command to make Autodock-gpu run successfully?
In addition, I can follow the tutorial you gave me to generate "*.maps.fld", but how to generate "-l .glg" needed to generate ".maps.fld"?

Last, I want to ask you, mk_prepare_receptor.py “--box_center_on_reactive_res” is the reactive residue as the box center, do not need to give additional parameters?

@diogomart
Copy link
Contributor

The .gpf file is the input for autogrid, and the .glg is written by autogrid to log information. The maps, consisting of .map files for each atom type, for electrostatics, and for desolvation, as well as the .fld file, are all written by autogrid. See https://github.com/forlilab/Meeko#3-run-autogrid (I think this is what you are following).

You can get autogrid here: https://autodock.scripps.edu/download-autodock4/

mk_prepare_receptor.py “--box_center_on_reactive_res” is the reactive residue as the box center

yes, this places the box center near the sidechain

@diogomart
Copy link
Contributor

I don't understand.

@guzh970630
Copy link
Author

guzh970630 commented Dec 18, 2023

Thank you very much for your patience. I want to ask a question about the force field of Reactive Docking. In which *.py file is the code for the relevant formulas and parameters of the force field required in the process of Reactive Docking?

@diogomart
Copy link
Contributor

parser.add_argument('--r_eq_12', default=1.8, type=float, help="r_eq for reactive atoms (1-2 interaction)")
parser.add_argument('--eps_12', default=2.5, type=float, help="epsilon for reactive atoms (1-2 interaction)")
parser.add_argument('--r_eq_13_scaling', default=0.5, type=float, help="r_eq scaling for 1-3 interaction across reactive atoms")
parser.add_argument('--r_eq_14_scaling', default=0.5, type=float, help="r_eq scaling for 1-4 interaction across reactive atoms")

Note that v0.6.0-alpha broke reactive docking preparation, v0.5.0 should be used for reactive docking instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants