The PDB's documentation for entity_poly.pdbx_strand_id says it is not required -- https://mmcif.wwpdb.org/dictionaries/mmcif_pdbx_v50.dic/Items/_entity_poly.p.... And the documentation is says it is: "The PDB strand/chain id(s) corresponding to this polymer entity." That seems poorly defined. I'll ask the PDB for clarification. I am surprised that the PDB is requiring entity_poly,pdbx_strand_id, since it should be computable from the rest of the file. And if they computed it, there would be no ambiguities. But even if that is fixed, I suspect that the PDB will still have issues with the fact that ChimeraX outputs all sheet ids as unknown. And that is because ChimeraX currently does not keep track of the sheets, only the strands. To get unique sheet ids, give the "computsedSheets true" option -- "save foobar.cif computedSheets true". Then the mmCIF writer will run the DSSP computation and use that to generate the sheet/strand information. But that overrides any choices that were in the input file. HTH, Greg On 7/11/24 12:52, Vorländer,Matthias Kopano via ChimeraX-users wrote:
Dear ChimeraX team,
Structure files in .cif format that are generated by ChimeraX are unfortunately not suitable for deposition to the PDB. This is due to lack of the column *_entity_poly.pdbx_strand_id *in the header*. *The column is usually found in the header in this table and contains the chain Identifier (i.e ‘A’ for chain A):
loop_
_entity_poly.entity_id
_entity_poly.nstd_monomer
_entity_poly.type
_entity_poly.pdbx_seq_one_letter_code_can
Since ChimeraX does an excellent at converting PDBs to mCIFs otherwise, would it be possible to have ChimeraX include this column in the header of mmCIF files? This would greatly help to facilitate the tiresome process of depositing models to the PDB.
Many thanks in advance,
Best,
Matthias