Closed xiki-tempula closed 2 years ago
Yeah this is a problem. But I do not fully agree with your statement: "In theory, the partial charge used during the dihedral fitting should be the charge derived in the QM calculations."
Because the external charges are not necessarily similar to the QM-based charges. So one cannot assume to assign QM-based charges to the fragments and hope that they are similar to final molecule's charges. And if they are not, the dihedral profiles will be off.
I thought about this issue and so far have not found an error-free solution except not allowing external charges.
Perhaps could give the user the option to pick "use external charges for fragments" vs "use QM based charges for fragments".
What do you think?
Because the external charges are not necessarily similar to the QM-based charges. So one cannot assume to assign QM-based charges to the fragments and hope that they are similar to final molecule's charges. And if they are not, the dihedral profiles will be off.
I guess it is more related to why does one need the external charges. The reason that I use external charges is that I use the ESP/RESP charge, which is conformation-dependent for flexible molecules. So I need to supply the external charge as a way of supplying the charge derived at the same theory level but across many conformations. So for me, this is not an issue. This is also kind of my reason for having the option qm_method_charge
for ORCA where the QM charge could be derived at the same level as external charges during the dihedral scan.
But I do agree with the
Perhaps could give the user the option to pick "use external charges for fragments" vs "use QM based charges for fragments".
[scan]
ext_charges = True/False
Completely agree!
Could have ext_charges = False by default (since it is more stable). But throw a NOTE/WARNING that this might be an issue if ext_charges are very different.
This should be implemented in the latest push.
Usage:
[ff]
use_ext_charges_for_frags = no :: bool
@selimsami Excellent, thank you.
@selimsami With regard to this using explict charge during the dihedral scan, I have a question. Given that the explicit charge will be used during the dihedral scan, will the charge recorded in the qforce_fragments be the explicit charge as well? Or the QM charge is recorded? Thanks
Do you mean external by explicit?
charge in qforce_fragments should be a dictionary of QM methods: charges
@selimsami
Do you mean external by explicit?
Yes, sorry.
charge in qforce_fragments should be a dictionary of QM methods: charges
Cool.
In theory, the partial charge used during the dihedral fitting should be the charge derived in the QM calculations. However, in practice, the charge
ext_q
is used instead.This creates a large hysteresis.
start_qforce/fragments/scan_data_CC_H8C8O2_b5abd75e5cfae9c5961bfe983af88435~2.pdf
The fragment which under QM optimisation is The fragment under MD optimisation is
Note that the N being this close to the carboxyl group can be quite problematic.
Note that if one look at
start_qforce/fragments/CC_H8C8O2_b5abd75e5cfae9c5961bfe983af88435~2/step23/start_qforce.itp
The last atom N1 got a charge of -0.66695, which is from the ext_q instead of the QM charge. Such a large charge will cause some problems to the MM potential landscape.