[Biopython] What is our thinking about RCSB BCIF format?
"Moth, Christopher W" <[email protected]> Wed, 21 Feb 2024 17:26:32 +0000
| Newsgroups | gmane.comp.python.bio.general |
|---|---|
| Message-ID | <LV3PR08MB90254BFB79528C997D3F59A0EA572@LV3PR08MB9025.namprd08.prod.outlook.com> |
--===============4152587644422487560== Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_LV3PR08MB90254BFB79528C997D3F59A0EA572LV3PR08MB9025namp_" --_000_LV3PR08MB90254BFB79528C997D3F59A0EA572LV3PR08MB9025namp_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I apologize if this question is already under discussion elsewhere and I am= missing it. Redirection welcome. After clinging to python2 for ages, the RCSB seems to finally released its = own python_3_ based BCIF parser.... https://www.rcsb.org/news/feature/65a1af31c76ca3abcc925d0c .... and I would [email protected] that there would be demand fr= om the Bipython community for a faster cif parser in the current age of hug= e Cryo-EM structures.... Is there any initiative to bolt-on the RCSB parser to biopython (bolt on ou= r mmcif dictionary or so)? .. or perhaps write our own binary parser in pure python? ... or perhaps ignore "binary format" as fundamentally utterly non-pythonic= ? Thanks for sharing news of directions or wisdom. --_000_LV3PR08MB90254BFB79528C997D3F59A0EA572LV3PR08MB9025namp_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-= 1"> <style type=3D"text/css" style=3D"display:none;"> P {margin-top:0;margin-bo= ttom:0;} </style> </head> <body dir=3D"ltr"> <div class=3D"elementToProof"><span style=3D"font-family: Aptos, Aptos_Embe= ddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 1= 2pt; color: rgb(0, 0, 0);">I apologize if this question is already under di= scussion elsewhere and I am missing it. Redirection welcome.<br> <br> After clinging to python2 for ages, the RCSB seems to finally released its = own python_3_ based BCIF parser....<br> <br> </span></div> <div class=3D"elementToProof"><span style=3D"font-family: Aptos, Aptos_Embe= ddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 1= 2pt; color: rgb(0, 0, 0);"><a href=3D"https://www.rcsb.org/news/feature/65a= 1af31c76ca3abcc925d0c" id=3D"LPlnk801610">https://www.rcsb.org/news/feature= /65a1af31c76ca3abcc925d0c</a></span></div> <div class=3D"elementToProof"><br> </div> <div class=3D"elementToProof"><span style=3D"font-family: Aptos, Aptos_Embe= ddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 1= 6px; color: rgb(0, 0, 0); background-color: rgb(255, 255, 255);">.... and I= would [email protected] that there would be demand from the Bipython community for a faster cif parser = in the current age of huge Cryo-EM structures....</span></div> <div class=3D"elementToProof"><br> </div> <div class=3D"elementToProof"><span style=3D"font-family: Aptos, Aptos_Embe= ddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 1= 2pt; color: rgb(0, 0, 0);">Is there any initiative to bolt-on the RCSB pars= er to biopython (bolt on our mmcif dictionary or so)? <br> .. or perhaps write our own binary parser in pure python? <br> ... or perhaps ignore "binary format" as fundamentally utterly no= n-pythonic?</span></div> <div class=3D"elementToProof"><br> Thanks for sharing news of directions or wisdom.</div> <div class=3D"elementToProof"><br> </div> </body> </html> --_000_LV3PR08MB90254BFB79528C997D3F59A0EA572LV3PR08MB9025namp_-- --===============4152587644422487560== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Biopython mailing list - [email protected] https://mailman.open-bio.org/mailman/listinfo/biopython --===============4152587644422487560==--