-
Notifications
You must be signed in to change notification settings - Fork 28
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
Problem with Hessian options #12
Comments
ericchansen
added a commit
that referenced
this issue
Jun 16, 2016
Untested, but I think this is all that is needed in calculate to make -ge work with multiple energies. However, there are still issues with reading the archive in general. It appears that our current code is only suited to handle Cartesian coordinates. These changes are in reference to issue #12.
ericchansen
added a commit
that referenced
this issue
Jun 16, 2016
Untested, but these are probably all the changes needed in filetypes. This was a little trickier than I expected because using z-matrix coordinates adds another section (separated by \\) to the archive. Also, I didn't write any code to read z-matrix coordinates. The atoms are simply skipped for now. Now the problem is that we have to account for having HF vs. HF + ZeroPoint energies. Changes to address issue #12.
ericchansen
added a commit
that referenced
this issue
Jun 16, 2016
…ergies In constants, you can now select what type of Gaussian energies to use. Say you want to use only HF, then use: GAUSSIAN_ENERGIES = ['HF'] Say you want to use HF + ZPE, then use: GAUSSIAN_ENERGIES = ['HF', 'ZeroPoint'] The labels inside of the list are simply the labels that show up in the Gaussian archive, so this can be extended to use any type of energy in the archive (or perhaps even other attributes as a sort of hack). Also, if you take a look at the arhive, you will see that these energies look something like: HF=0.2342,0.2342,0.12412 These changes help address issue #12.
ericchansen
added a commit
that referenced
this issue
Jun 16, 2016
For all the changes to -ge to allow for multiple structures and energy types, also added these changes to -gea, -geo and -geao. This should be everything needed to address issue #12.
ericchansen
added a commit
that referenced
this issue
Jun 16, 2016
I initially wrote and tested the modifications for the command ge, which seem to be working well. When I extended this to gea, geo and geao, I more or less copy and pasted the code from ge, and forgot to update the com property of the Datum instances. Corrected in this commit. Also, this is to address issue #12.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using calculate.py, or programs that depend on it, together with options for using the Gaussian log file (-geigz or -mgeig), the program throws an error message about unrecognized options (all on the line), but the command still completes, and seems to do it correctly
The text was updated successfully, but these errors were encountered: