-
Notifications
You must be signed in to change notification settings - Fork 138
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
Nexus: Adding support for ghost atoms #1653
Conversation
Can one of the maintainers verify this patch? |
okay to test |
This looks like it should work, though permanently adding atom X to the periodic table is unusual. Does the following work?
|
This does work. I could use this since I'm guessing ghost atoms aren't very commonly used. |
I think having a way of supporting ghost atoms is a good idea. One possibility is to add a function like this to physical_system.py
and use it outside
or move its use into QmcpackAnalyzer instead
If having an atom X permanently available is more convenient, then I'm fine if you want to add this line
after |
That makes more sense, and this way ghost atoms don't have to be named "X". I'll update this PR. |
@jtkrogel How does this look? I didn't love having to pop from kwargs since it is mutating the object, but it was necessary otherwise the |
Just one small requested change, then good to go. |
Fixed! |
Looks good. Thanks. |
Allows nexus to understand ghost atoms.
Why this is necessary:
The converters from quantum chemistry codes (e.g. gaussian/gamess) don't currently know about ghost atoms either, but they will parse the correct basis functions/MO coefficients. These just get assigned to atoms of type "". Replacing these with something reasonable like "X" and trying to uses nexus post calculation for analysis results in
This fixes the above error so now QmcpackAnalyzer can be used on systems with ghost atoms.