-
Notifications
You must be signed in to change notification settings - Fork 3
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
poly.type not recognized by the wwPDB servers #19
Comments
If you mean the lack of TER in mmCIF, it's fine, only PDB files have TER records. The software used on the PDB servers discards and regenerates some information; it may easily happen that correct annotation is replaced with incorrect one. To investigate it, we'd need an example file that demonstrates the problem. |
How can I send you the file if I don't want to post it here? Maybe I could remove the coordinate columns... |
You could use send it by email ([email protected]). |
Please also send it to me, or let Marcin share it with me. Did the PDB staff explain what was wrong? |
Ok, I will send you the problematic file. I will also ask the wwPDB staff to describe the problem in detail. |
Now I have tried uploading different modified versions of the mmcif file to the deposition and validation servers, including running the files through the PDB extract server, and I cannot figure out exactly what is causing the problem. For the time being, I cannot waste more time on this issue, but everything points at it being the PDB servers reading the poly.type records incorrectly or mapping to the chains incorrectly. My workaround is to delete the section entirely before uploading to a fresh deposition session. |
Wouldn't it be easier to just send us the file? |
It seems to be a bug in maxit. I compiled v11.200 and reduced 7k00 to ~500 lines input.mmcif.gz to reproduce it. The input file has:
Running:
produces output.cif with:
All looks fine apart from:
If I change the order of lines in the input to:
then in the output I get:
If |
Good that you found the culprit. For the time being, I will just delete the poly.type section before I upload files to wwPDB. |
Just noticed maxit-v11.300 has been released https://sw-tools.rcsb.org/apps/MAXIT/source.html and it worked properly. Also tested https://validate-rcsb-1.wwpdb.org/, which seemed to still use an older maxit version. |
I have a problem that the wwPDB deposition server and also the wwPDB validation server misidentifies my polymer chains as polyribonucleotide instead of polypeptide(L) when I upload the refined.mmcif file from refine_spa_norefmac. The poly.type is set correctly in the header, but the wwPDB staff says it is wrong on their side.
Example:
This is a ribosome structure with both ribonucleic acids and many proteins. Strangely, only protein chains up til a specific point are identified as polyribonucleotide, which indicate to me that there is some corruption in the file. Could the lack of TER records cause this problem? In an earlier deposition, which used an older version of refine_spa, the polymer type records were not there.
The text was updated successfully, but these errors were encountered: