-
Notifications
You must be signed in to change notification settings - Fork 8
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
problematic frequency parsing from Gaussian files #229
Comments
Are these Raman calculations? Sorry, I cannot access the information on the link. If so, I would suggest the following, depending on your deadline @schumannj: we will transfer the Gaussian to its own plugin, and then take care of defining a If you need it to be fixed asap, we can take a look on the parser and do a quick patch. @ladinesa what do you think of this? Do you prefer to fix this asap and later transfer Gaussian anyways to a plugin? |
I would also put up a fix in the old schema unless @ndaelman-hu would llike to take over? |
Update: found the reason. Gaussian prints the vibrational section 2x (not sure yet why). Our parser cannot handle the first output format, though the Gaussian schema did distinguish between these 2 headers and sections. I've removed this now |
@schumannj We aren't extracting the (harmonic) force constants nor the IR intensities. Do you need these? |
That would be great, thank you! |
@schumannj have added IR intensities and Harmonic force constants. |
closed with #232 |
Found a small error with the unit conversion that had some Gaussian tests fail (hard to tell from the verbose list with warnings). Will patch this quickly. |
Patched |
I have 2 Gaussian files with frequency calcualtions, but the frequencies are not parsed correctly. in x_gaussian_section_frequncies the x_gaussian_frequency vector lists all frequencies twice and has some empty rows. Can you fix this?
See here for the link to the data. It is shared with @ndaelman-hu and @ladinesa . Let me know if you need something else.
The text was updated successfully, but these errors were encountered: