<html><head></head><body><div class="ydpeeba308byahoo-style-wrap" style="font-family: Helvetica Neue, Helvetica, Arial, sans-serif; font-size: 10px;"><div></div>
<div dir="ltr" data-setdir="false">For novel functionality (see the first reviewer) you could point to the new pairwise sequence aligner in Biopython. It is as fast as aligners implemented as standalone (C/C++) programs, maybe even faster if you want to align many sequences, but much more flexible. I don't know of any existing programs that offer this speed and flexibility.</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_2873787830" class="yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Sunday, June 7, 2020, 9:16:22 PM GMT+9, Peter Cock <p.j.a.cock@googlemail.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="yiv5886065702"><div dir="ltr">Good news: The abstract was accepted for a lightning talk, and we have the opportunity to improve the abstract (see reviews below).<div><br></div><div>Specifically I think we should add something about the alphabet changes underway on GitHub (which in hindsight I wish we'd drawn more attention to in the NEWS file for Biopython 1.78). Quoting the DEPRECATED file,</div><div><br></div><div>"The design of Bio.Aphabet included a number of historic design choices which, with the benefit of hindsight, were regretable. While the details remain to be agreed, we intend to remove or replace Bio.Alphabet in 2020."</div><div><br></div><div>GMail has just flagged that regrettable was misspelt. Opps.</div><div><br></div><div>The BOSC/BCC 20202 abstract is here:</div><div><br></div><div><a rel="nofollow" target="_blank" href="https://github.com/biopython/talks/tree/master/2020_BOSC/abstract">https://github.com/biopython/talks/tree/master/2020_BOSC/abstract</a><br></div><div><br></div><div>Peter<br><br><div class="yiv5886065702gmail_quote"><div dir="ltr" class="yiv5886065702gmail_attr">---------- Forwarded message ---------<br>From: <strong class="yiv5886065702gmail_sendername">BCC2020 Track Chairs</strong> <span><<a rel="nofollow" ymailto="mailto:bcc2020@easychair.org" target="_blank" href="mailto:bcc2020@easychair.org">bcc2020@easychair.org</a>></span><br>Date: Sun, Jun 7, 2020 at 2:22 AM<br>Subject: Your abstract (11) has been accepted for a short talk at BOSC 2020!<br>To: Peter Cock <<a rel="nofollow" ymailto="mailto:p.j.a.cock@googlemail.com" target="_blank" href="mailto:p.j.a.cock@googlemail.com">p.j.a.cock@googlemail.com</a>><br></div><br><br>Dear Peter Cock,<br>
<br>
Congratulations! An abstract on which you are an author (11, Biopython Project Update 2020) has been chosen for a short talk in the BOSC track of the Bioinformatics Community Conference (BCC2020). Short (lightning) talks are 5 minutes. Long talks are 15 minutes. There will be time allocated at the end of each session for live Q&A with presenters from that session.<br>
<br>
All talks at BCC2020 (except for keynotes) will be presented via pre-recorded videos prepared by the presenters (that means you!) and submitted to us by July 6. We will send you more information about this process soon.<br>
<br>
In order to accept our invitation to present and secure a spot in our packed schedule, please fill out the response form at XXX by June 15. If we don’t hear from you by the end of the day on June 15, we will assume you are declining the invitation to give a talk at BCC2020 and will offer your talk spot to another author. <br>
<br>
All accepted speakers will also be welcome to present their work as a poster/demo. We're still thinking about how posters and demos will work. We will likely hold them as breakout videoconferences where you can share a live or prerecorded short presentation and a PDF and discuss your work with attendees. We’re also open to suggestions on ways to present posters - a giant poster-sized PDF would not be easy to examine on screens! <br>
<br>
If you want to make any changes to the abstract that you submitted, you will have until June 22 to upload a revised abstract at <a rel="nofollow" target="_blank" href="https://easychair.org/conferences/?conf=bcc2020">https://easychair.org/conferences/?conf=bcc2020</a>. <br>
<br>
Sincerely,<br>
Program Committee, BOSC 2020<br>
<br>
P.S. The reviewers' feedback on your abstract is at the end of this message. If you have any questions, please contact the BOSC organizing committee <<a rel="nofollow" ymailto="mailto:bosc@open-bio.org" target="_blank" href="mailto:bosc@open-bio.org">bosc@open-bio.org</a>>.<br>
<br>
SUBMISSION: 11<br>
TITLE: Biopython Project Update 2020<br>
<br>
<br>
----------------------- REVIEW 1 ---------------------<br>
SUBMISSION: 11<br>
TITLE: Biopython Project Update 2020<br>
AUTHORS: Peter Cock<br>
<br>
----------- Relevant -----------<br>
SCORE: 1 (yes)<br>
----------- Available -----------<br>
SCORE: 1 (yes)<br>
----------- Open -----------<br>
SCORE: 1 (yes)<br>
----------- Updated -----------<br>
SCORE: 1 (project was previously presented at BOSC/GCC but abstract describes updates)<br>
----------- Formatted -----------<br>
SCORE: 1 (yes)<br>
----------- Community -----------<br>
SCORE: -1 (no)<br>
----- TEXT:<br>
The project obviously has some impact (with more than 4K followers on twitter), but the abstract does not mention anything specifically. A proxy indicator is the number of code contributors, but its not the same thing.<br>
----------- Novelty -----------<br>
SCORE: -1 (no)<br>
----- TEXT:<br>
Its an update which focuses on black and pep 8 python code formatting guides and unit tests etc - not functionality.<br>
----------- Example -----------<br>
SCORE: -1 (no (and it needs one))<br>
----------- Runnable -----------<br>
SCORE: 1 (yes)<br>
----------- Quality score -----------<br>
SCORE: 1 (ok)<br>
----- TEXT:<br>
Even though this is an update, a sentence or two on that the library actually does and what its good for would have been very helpful. Otherwise it seems like an update on a well-used code base in bioinformatics - although the focus on code formatting, unit tests and CI is not that exciting for users I would think, but maybe for prospective contributors.<br>
----------- Suitability for a long talk -----------<br>
SCORE: 1 (Fine for short talk)<br>
<br>
<br>
<br>
----------------------- REVIEW 2 ---------------------<br>
SUBMISSION: 11<br>
TITLE: Biopython Project Update 2020<br>
AUTHORS: Peter Cock<br>
<br>
----------- Relevant -----------<br>
SCORE: 1 (yes)<br>
----------- Available -----------<br>
SCORE: 1 (yes)<br>
----------- Open -----------<br>
SCORE: 1 (yes)<br>
----------- Updated -----------<br>
SCORE: 1 (project was previously presented at BOSC/GCC but abstract describes updates)<br>
----------- Formatted -----------<br>
SCORE: 1 (yes)<br>
----------- Community -----------<br>
SCORE: 1 (yes)<br>
----------- Novelty -----------<br>
SCORE: 1 (yes)<br>
----------- Example -----------<br>
SCORE: 0 (sort of or not applicable)<br>
----- TEXT:<br>
Not applicable<br>
----------- Runnable -----------<br>
SCORE: 1 (yes)<br>
----------- Quality score -----------<br>
SCORE: 2 (good)<br>
----- TEXT:<br>
Given the importance of Biopython for the community and the continued improvement that the abstract details (3 releases since last year's BOSC), I think an update is valuable.<br>
----------- Suitability for a long talk -----------<br>
SCORE: 2 (Good for short or long talk)<br>
<br>
<br>
<br>
----------------------- REVIEW 3 ---------------------<br>
SUBMISSION: 11<br>
TITLE: Biopython Project Update 2020<br>
AUTHORS: Peter Cock<br>
<br>
----------- Relevant -----------<br>
SCORE: 1 (yes)<br>
----------- Available -----------<br>
SCORE: 1 (yes)<br>
----------- Open -----------<br>
SCORE: 1 (yes)<br>
----------- Updated -----------<br>
SCORE: 1 (project was previously presented at BOSC/GCC but abstract describes updates)<br>
----------- Formatted -----------<br>
SCORE: 1 (yes)<br>
----------- Community -----------<br>
SCORE: 1 (yes)<br>
----------- Novelty -----------<br>
SCORE: 1 (yes)<br>
----------- Example -----------<br>
SCORE: 0 (sort of or not applicable)<br>
----------- Runnable -----------<br>
SCORE: 1 (yes)<br>
----------- Quality score -----------<br>
SCORE: 3 (excellent)<br>
----- TEXT:<br>
BioPython is a well-established project and of very general interest to the bioinformatics community. In many ways it is an example to follow for other smaller and/or younger open source projects, so it will be very interesting to hear the news and updates from last year.<br>
----------- Suitability for a long talk -----------<br>
SCORE: 2 (Good for short or long talk)<br>
----- TEXT:<br>
I believe that most of the audience will already know the BioPython project, so a short talk should be enough to explain news and updates, rather than going into all the details of the library.<br>
<br>
<br>
</div></div></div></div>_______________________________________________<br>Biopython mailing list - <a ymailto="mailto:Biopython@mailman.open-bio.org" href="mailto:Biopython@mailman.open-bio.org">Biopython@mailman.open-bio.org</a><br><a href="https://mailman.open-bio.org/mailman/listinfo/biopython" target="_blank">https://mailman.open-bio.org/mailman/listinfo/biopython</a></div>
</div>
</div></body></html>