You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have attached two output files to this issue. I have the same exact coordinates and input blocks with the only difference being the numerical frequency routine or the analytical routine. The numerical routine finishes with no negative frequencies while the analytical routine comes back with three large negative frequencies. I am unsure if a setting I have is incorrect for the analytical hessian, or if this is a bug.
@jbecca You need xfine grid in the hessian input section and you need to be very strict in the geometry optimization. Have a look at the attached input and output files fufu.nw.txt fufu.output.txt
@edoapra Is the xfine grid something that should always be set for calculating the analytical frequencies? I would have normally assumed that any grid or numerical instability would have shown up first in the finite difference hessian method.
@jbecca No, the analytical frequencies are more likely to be affected by numerical issue, both in first determining the minimum and then in evaluating the hessian
I have attached two output files to this issue. I have the same exact coordinates and input blocks with the only difference being the numerical frequency routine or the analytical routine. The numerical routine finishes with no negative frequencies while the analytical routine comes back with three large negative frequencies. I am unsure if a setting I have is incorrect for the analytical hessian, or if this is a bug.
Thanks for looking into this.
reactant1-geom-num.txt
reactant1-geom.txt
The text was updated successfully, but these errors were encountered: