Pydna Hackathon - Thursday 3rd of October

[manulera]

We discussed to do a Hackathon this month. The idea is to commit a chunk of time (at least 1-2 hours) to work on pydna issues. To make the most of the day, we should agree in advance about what we are going to work on during the day.

1. Date: Thursday 3rd of October
2. Mention things that could be worked on by mentioning them in this discussion. Also include an estimate of the time they would take to implement a first version. The idea is that at least a first version of the feature can be completed within the day, so should not be a massive implementation.
3. Create an assign issues tagged with the label Hackathon-2024.

Once they are added to the discussion, I will include them in a list in this post, so that we can keep track on what's on the menu for the day. In the meantime, check the issues tagged with hackathon.

On the day, we can keep a zoom room open where people can jump in, introduce themselves, ask questions, etc.

[manulera]

improve assembly fragments

@hiyama341 you mentioned an improvement to assembly_fragments here. If this is something you would be interested in doing, you can create an issue and self-assign.

[manulera]

typing

There is an existing issue #176.

I think this is a good one because it's a bit boring so you would not do it on a normal day, but it's quite useful and everyone can chip in no matter how much time they have.

I will probably work on this myself during the hackathon

[manulera]

Contributing to pydna hackathon?

Hi, sorry for the spammy comment but I am tagging everyone who has contributed / created an issue in case they are interested in participating in the hackathon directly, or in proposing issues to work on for the participants.

@mountainpenguin
@JamesBagley
@kcorreia
@JacobHayes
@bruno2git
@benweinberg89
@ngamarra
@santirdnd
@glebkuznetsov
@photocyte
@marcus-r-kelly
@LuisaFJimenez
@timovwb
@JeffXiePL
@louisabraham
@andrewdavis3
@cbrueffer
@FinweNoldoran
@jefe-jeff
@shenker
@manulera
@hgbrian
@amijalis
@jlerman44
@zslastman
@grassoste
@jxu10
@osthomas
@mohamedmoez1983
@hsiaut
@TCoulth
@ghost
@AubinF
@harijay
@dependabot[bot]
@nick-chavez23
@surgebiswas
@hiyama341
@jan-glx
@willsharpless
@klprint
@hristog
@dgruano
@picousse
@BjornFJohansson
@codacy-badger
@ITS-Account
@mcrone

[manulera]

Hello @louisabraham @harijay @mdbetterton we have set the 3rd of October as the date, according to availability from when2meet.

I will probably join from 8:00 to 18:00 UK time, and then re-join at 20:00 until bedtime if someone from a different timezone is still around. Feel free to write what times work for you at some point if you want to join on Zoom!

[manulera]

guided struggle

The hackathon can also be an occasion for people to try the library for the first time knowing that we are going to be around to answer questions, so if there is interest from people, we could also propose to do that. They can use the day to try the library on their own and jump on the call if they get stuck with something.

If you are interested on participating on this, please reply to this comment!

[mdbetterton]

I would be interested in trying the library for the first time, if that winds up being part of the event.

[manulera]

Hi @mdbetterton yes, definitely!

[harijay]

I am interested in participating . Thanks for sending out the request Hari

…

On Wed, Sep 4, 2024 at 11:33 AM Manuel Lera-Ramirez < ***@***.***> wrote: guided struggle The hackathon can also be an occasion for people to try the library for the first time knowing that we are going to be around to answer questions, so if there is interest from people, we could also propose to do that. They can use the day to try the library on their own and jump on the call if they get stuck with something. — Reply to this email directly, view it on GitHub <#258 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAACWWXRAODZ7WPFOILP3ZTZU4R37AVCNFSM6AAAAABNUPR7ZCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTANJUG43TKMQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[manulera]

Thanks Hari, very appreciated, feel free to give your availability in the when2meet link in the top comment and to share some things you would like to see fixed / improved. You can keep an eye on the issues tagged with hackathon and assign to either of them.

[louisabraham]

I would love to implement some algorithms or make existing implementations faster. Any ideas?

[manulera]

@BjornFJohansson any ideas for this? I have not thought much about performance

[BjornFJohansson]

Hi, Louis
I never did a formal profiling of the code. The test suite always spent more time finding shared substrings, now that is much faster thanks to pydivsufsort. Some of the init for Dseq and Dseqrecord are slow since they are quite flexible (though there are quicker alternative versions). Perhaps the graph algorithms for finding paths in the homologous recombination function could be an interesting target. The current implementation is pure python via NetworkX, bu there are several faster libraries.

[dgruano]

I have some scripts that I used to design synonimous gene sequences with (1) mutated PAMs and (2) the addition or removal of restriction sites. I found them super helpful. If you think these could be integrated within pydna, I'm happy to give it a shot!