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

mismatch in --check in v3.2 #65

Open
turkiAlturaifi opened this issue Mar 9, 2023 · 2 comments
Open

mismatch in --check in v3.2 #65

turkiAlturaifi opened this issue Mar 9, 2023 · 2 comments

Comments

@turkiAlturaifi
Copy link

There seems to be an issue with the --check in v3.2. It gives the following output:
x Caution! Potential differences found between frequency and single-point geometries

The geometries are the same and using --check in v3.0.2 doesn't give this warning. Thanks!

@npe1011
Copy link

npe1011 commented Jan 22, 2024

I have encountered the same issues. It seems that, with the current version, the geometry of the first strcuture is read instead of the last structure. So in case opt+freq is run, the structure mismatch may occur.
The file io part seems to have been much charnged from ver 3.02.

Probably the follwing part.

getoutData class in io.py

# Assuming that the output file doesn't contain a geometry
# optimization at the beginning, we take the first set of atomic
# coordinates rather than the last, in the even that a finite
# difference frequency calculation was performed and the displaced
# geometries are printed.
self.cartesians = data.atomcoords[0].tolist()

@npe1011
Copy link

npe1011 commented Feb 7, 2024

This issue is also affecting --xyz option. The first structures, often unoptimized, are saved.

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