-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrapping up the GCC2016 Datathon #54
Comments
We have working ChIP-seq and RNA-seq pipelines for mammalian system. The plan is to describe pros/cons of elements of these pipes and alternative solutions. |
Trackster exporter is functional. On Wed, Jun 29, 2016 at 12:16 PM, test567 [email protected] wrote:
|
I think we should consider a drafting a manuscript (or some resource) where we highlight these RNA-seq and chIP-seq workflows with benefits and drawbacks of the various alternative options, as Krzys suggested. In doing so, we would introduce the Galaxy workflow environment where the alternative (tool) options can be implemented to the base workflows. It would be excellent if we could make an Interactive Tour to show this. I can't emphasize enough that this would be targeting novice, end-users who are not familiar with NGS analysis. Interested in feedback |
Hi everyone. +1 for the @MoHeydarian proposal! My Datathon summary:
From #29: Waiting that Stacks related tools will be reinstall after enabling conda based Galaxy tools dependencies to be install on the cloud instance. If this can be made before the end og GCC, I will create workflows for RADseq data analysis using STACKS toolsuite. Galaxy-tour:
|
Summary: |
@ssander5 this is great! |
Hi fellow Datathoneers,
Thank you very much for taking part in the second GCC Datathon. We hope you had a good experience. In order to get an overview on current and potential future Datathon activities, we would love to hear from you what you did during the Datathon. Comments and criticism are also welcome. If you could briefly summarise things you did during the Datathon (or just link the github tickets you were working on if they are already summarised) and whether you are planning to continue working on it and post this as a reply to this ticket that would be great and help us a lot.
All the best,
@frederikcoppens , @jennaj , @cschu
The text was updated successfully, but these errors were encountered: