-
Notifications
You must be signed in to change notification settings - Fork 64
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
Improve CIF parser to accept symmetric MOFs. #5
Comments
Has there been any work on this? This would also fix #1 |
I don't think so - right @peteboyd ? |
This is something that would be quite simple to add, in particular once we have the first basic continuous integration tests in place (which would guard against unintended consequences of the shift) |
@peteboyd It turns out Henglu just stumbled upon this as well. Would you be open to adding a dependency on ASE to get a fully fledged CIF parser? I see that you already thought about this in lammps_interface/lammps_interface/structure_data.py Lines 1579 to 1589 in 9983f29
Is there more to do than make If it's just the above, I think it would be quite straightforward to do. |
The only thing that would require a little attention is when the code reads in bonding information from the CIF file. I'm not sure if that part of the code is still relevant, but it would have to be investigated before proceeding with the ASE implementation. |
Reading the bonding information from CIF is absolutely useful when we have structures generated using one of the topology-based structure generators. |
Thanks - good point about the weird bonding cases that come from crystal building programs. Bonding can be dealt with using symmetry operations, we just have to be careful about it. I recall the notation in the CIF format is a bit strange. |
I think the CIF parser can be improved to accept non-P1 MOFs. ASE Python library has a pretty good CIF parser so that can be used to read MOFs or even other crystals. Moreover, it can read many file formats, allowing other file formats to be accepted. I would be willing to work on this.
The text was updated successfully, but these errors were encountered: