-
Notifications
You must be signed in to change notification settings - Fork 103
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
Carry through space group information when reading and writing pdb files #689
Comments
In addition the support for the PDB format is relatively rudimentary in Biotite, as the format itself is deprecated, i.e. there are no low-level file editing capabilities. For PDBx (CIF/BinaryCIF) Biotite has such capabilities. You could set the space group e.g. like this: symmetry_category = CIFCategory({"space_group_name_H-M": "P 21 21 21"})
cif_file.block["symmetry"] = symmetry_category If you would like to implement reading/writing the space group for |
Hi @padix-key, thank you for your help! Sorry for the long delay on my response I think a setup like you described would work fine for our purposes. I can throw up a PR sometime soon to implement that I have a question, though (apologies for my ignorance on crystallography): Don't the If the pdb file contains the asymmetric unit, the space group and Again, apologies if either my understanding of crystallography is faulty here or if Biotite is already handling this gracefully |
|
Thank you for the excellent project!
I noticed that, when I read in a pdb-formatted file and then write it back out,
the space group information in the
CRYST1
record gets lost.Looking in the code, it looks like the space group is hardcoded to always be
P1
.And, the
Z
value always gets saved as1
.Is there any reason the space group and Z can't be saved when a file is read in, and properly written when the structure is saved to file?
If there is a way to do this, I'm more than happy to give it a shot and submit a PR.
Thanks!
The text was updated successfully, but these errors were encountered: