<html><head></head><body><div class="ydpe40a1425yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:10px;"><div></div>
<div dir="ltr" data-setdir="false">Very much in favor of overhauling Bio.PDB. This is also a good opportunity to make the code organization more consistent with the rest of Biopython, for example by having "read" and "parse" functions instead of having to create parser objects first.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">I agree with João's idea of working under a new namespace. Since the new module will probably also contain a class named "Structure", I would suggest to give the module a different name, so we don't end up with the Structure class and a Structure module.</div><div dir="ltr" data-setdir="false"><span>To distinguish the two,</span> you could use "structures" for the module, and "Structure" for the class. We did something similar when we overhauled the old Bio.Motif module, creating a new module Bio.motifs, with a class named "Motif" inside.</div><div dir="ltr" data-setdir="false">Btw note that lowercase letters are recommended for module names in Python.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false">Best,</div><div dir="ltr" data-setdir="false">-Michiel<br></div><div><br></div>
</div><div id="yahoo_quoted_2548283019" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Thursday, October 17, 2019, 7:23:21 AM GMT+9, João Rodrigues <j.p.g.l.m.rodrigues@gmail.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="yiv0718986851"><div><div dir="ltr"><div>Hi Joe,</div><div><br clear="none"></div><div>IIRC from BOSC, my proposal was to work under a new namespace 'Bio.Structure' to avoid compatibility issues and, on the long term, deprecate Bio.PDB once all functionality had been rewritten.</div><div><br clear="none"></div><div>It would also be interesting to gauge what would be features people (users and developers) would like to see implemented/changed/fixed/removed.<br clear="none"></div><div><br clear="none"></div><div>The old car analogy is perfect :)</div><div><br clear="none"></div><div>Cheers,</div><div><br clear="none"></div><div>Joao<br clear="none"></div></div><br clear="none"><div class="yiv0718986851gmail_quote"><div class="yiv0718986851gmail_attr" dir="ltr">Joe Greener <<a rel="nofollow" shape="rect" ymailto="mailto:jgreener@hotmail.co.uk" target="_blank" href="mailto:jgreener@hotmail.co.uk">jgreener@hotmail.co.uk</a>> escreveu no dia quarta, 16/10/2019 à(s) 15:08:<br clear="none"></div><blockquote class="yiv0718986851gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;">
<div class="yiv0718986851yqt7325552817" id="yiv0718986851yqt29045"><div>
<p>Hi Patrick,<br clear="none">
<br clear="none">
Some of us spoke about this at CoFest too, inspired by the ideas in Biotite (I don't think you and I spoke at BOSC though). As I recall it was João, Spencer, myself and possibly Peter in the discussions.<br clear="none">
<br clear="none">
We were in favour of the fundamental idea of a large coordinate array that is indexed into. As you point out though it would be no small amount of work to implement. I personally won't have time to do it, though I am happy to discuss and review code.<br clear="none">
<br clear="none">
I view Bio.PDB like a beloved older car that has been patched up over many years. It is probably the most widely used and debugged PDB parsing code around, and any overhaul would have to make sure to maintain the behaviour that many people rely on. That said,
it does have its peculiarities and is rather slow (<a rel="nofollow" shape="rect" target="_blank" href="https://github.com/jgreener64/pdb-benchmarks">https://github.com/jgreener64/pdb-benchmarks</a>). I'm just saying that we should make sure to get consensus before merging
any overhaul PRs. But for sure I am in favour of someone making those PRs.<br clear="none">
<br clear="none">
Best,<br clear="none">
Joe<br clear="none">
</p>
<p><font size="-1">Joe Greener<br clear="none">
Research Associate, UCL<br clear="none">
<a rel="nofollow" shape="rect" target="_blank" href="http://jgreener64.github.io">http://jgreener64.github.io</a></font><br clear="none">
</p>
<p><br clear="none">
</p>
<div>On 16/10/2019 12:37, Patrick Kunzmann wrote:<br clear="none">
</div>
<blockquote type="cite">
Hello Biopythoneers, <br clear="none">
<br clear="none">
at the BOSC this year we talked about overhauling the Bio.PDB module. The problem is that currently the atom coordinates are stored in a separate NumPy array for each atom. This design prevents efficient computation of all kinds of analyses (distances, angles,
superimpositions, etc.). One proposed possible solution to this problem, we talked about, was to put the coordinates of the entire structure in one NumPy array, and let the Atom, Residue, Chain and Structure objects point to positions in this array. The benefit
of this approach is that functions could be directly applied onto the entire array, harnessing the power of vectorization.
<br clear="none">
<br clear="none">
For the analysis we could adapt the vectorized functions from the Python package Biotite, a project I am currently working on (<a rel="nofollow" shape="rect" target="_blank" href="https://www.biotite-python.org/apidoc/biotite.structure.html">https://www.biotite-python.org/apidoc/biotite.structure.html</a>).
Usually, these functions already accept the coordinates as NumPy array, so I think only a few tweaks would be necessary for every function.
<br clear="none">
<br clear="none">
However, we would require one person or a small team who makes the effort to implement the new structure types and adapts the analysis functions. I could offer a pair of helping hands in the adaption of the analysis functions, but I don't have the time for
anything more. <br clear="none">
<br clear="none">
So the question is: Is there anyone out there, who is willing to do this work? Alternatively, I would propose to write a 'bridge' package between Biopython and Biotite, that converts the Biopython structure representation into the representation in Biotite
and vice versa. I think, this solution is less elegant but would also require less effort.
<br clear="none">
<br clear="none">
Best regards <br clear="none">
<br clear="none">
Patrick Kunzmann <br clear="none">
<br clear="none">
_______________________________________________ <br clear="none">
Biopython mailing list - <a rel="nofollow" shape="rect" ymailto="mailto:Biopython@mailman.open-bio.org" target="_blank" href="mailto:Biopython@mailman.open-bio.org">
Biopython@mailman.open-bio.org</a> <br clear="none">
<a rel="nofollow" shape="rect" target="_blank" href="https://mailman.open-bio.org/mailman/listinfo/biopython">https://mailman.open-bio.org/mailman/listinfo/biopython</a>
<br clear="none">
</blockquote>
</div></div>
_______________________________________________<br clear="none">
Biopython mailing list - <a rel="nofollow" shape="rect" ymailto="mailto:Biopython@mailman.open-bio.org" target="_blank" href="mailto:Biopython@mailman.open-bio.org">Biopython@mailman.open-bio.org</a><br clear="none">
<a rel="nofollow" shape="rect" target="_blank" href="https://mailman.open-bio.org/mailman/listinfo/biopython">https://mailman.open-bio.org/mailman/listinfo/biopython</a></blockquote></div></div></div><div class="yqt7325552817" id="yqt40730">_______________________________________________<br clear="none">Biopython mailing list - <a shape="rect" ymailto="mailto:Biopython@mailman.open-bio.org" href="mailto:Biopython@mailman.open-bio.org">Biopython@mailman.open-bio.org</a><br clear="none"><a shape="rect" href="https://mailman.open-bio.org/mailman/listinfo/biopython" target="_blank">https://mailman.open-bio.org/mailman/listinfo/biopython</a></div></div>
</div>
</div></body></html>