<div dir="ltr">Hi Tiago,<br><br>The header records are very chaotic... some of them are well documented and populated by programs, e.g. SEQRES, HELIX, SHEET, etc. These would be easy to add to the parser (check the parse_pdb_header functions in Bio.PDB) but they are not there at the moment.<div><br></div><div>Cheers,</div><div><br></div><div>João</div></div><br><div class="gmail_quote">Tiago Antao <<a href="mailto:tra@popgen.net">tra@popgen.net</a>> escreveu no dia Fri Feb 20 2015 at 3:33:33 PM:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I am trying to get around the relationship between Bio.PDB and<br>
Bio.SeqIO.PdbIO, lets see if I got this right:<br>
<br>
1. Bio.PDB is quite limited in terms of what records it can parse. For<br>
example I cannot get to SEQRES or anything related to secondary<br>
structure (SHEET, HELIX)?<br>
<br>
2. PdbIO allows to extract the protein sequences from SEQRES<br>
<br>
<br>
Or, to put it another way, a generic PDB file is not completely<br>
accessible from inside Biopython in the sense that we cannot access<br>
some of the records (SHEET and HELIX being the examples here). Or is<br>
there a way to get to them via Bio.PDB?<br>
<br>
Many thanks for your help,<br>
T<br>
______________________________<u></u>_________________<br>
Biopython mailing list - <a href="mailto:Biopython@mailman.open-bio.org" target="_blank">Biopython@mailman.open-bio.org</a><br>
<a href="http://mailman.open-bio.org/mailman/listinfo/biopython" target="_blank">http://mailman.open-bio.org/<u></u>mailman/listinfo/biopython</a><br>
</blockquote></div>