-
Notifications
You must be signed in to change notification settings - Fork 11
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
Timeline #2
Comments
Good, but I think that:
need to be much higher (like week 6) since:
Otherwise, it might be very easy to get distracted implementing features that sound nice but might not have a clear and immediate benefit to people. Also, the web/electron GUI is an ambitious project in itself, and so we shouldn't dedicate time to it until we have a solid and useful CLI solution, which probably won't happen before the end of GSoC since we only have 8 weeks left. I believe @yannickwurm shares a similar view on this. |
Edited the timeline. If you guys can pick out a few papers that have good methods that we can reproduce with waterwheel, that would be great. Having a workflow goal to implement really helps determine a goal and discover edge/use cases. I'm thinking something that takes a stream of SRA accessions (and can then distribute those emitted values over SGE/cluster). I'd like to play with RNAseq a bit too, maybe use Kallisto. |
Some of this can be recycled for next GSoC, but I'm closing it since the 2016 one is over. |
A tentative plan for the way forward. I think once the core API is stable, time would be best spent reimplementing real world workflows that can be most improved with Streams. The primary concerns are
After that work can begin on DSL, Docker, admin panel app, nbind etc.
If you think there is not enough time partitioned to plans as their should be, or if some should be swapped, triaged for others, etc, don't hesitate to let me know. I'd like us all to agree upon realistic plans for these next 8 weeks that are exciting and fully satisfy the original overarching goal.
Week 5
shellPipe
taking an arraySummary
task
object now a stream that can wrap streams/non-streamsnew File
to vannila JS obect{file: 'foo'}
- easier to new devs, no peer dependencies - ab782fFor this week, continue improving waterwheel, examples with real world workflows. We already have a basic genomic one, I'd like to try out an RNASeq pipeline, or whatever you guys suggest.- stick to improving genomic workflow with sound reentrancyTask orchestration core codebase largely resolved, parallel/forking/join becomes easy when task returns a regularly compliant stream (i.e. no more custom events). Forking not done yet, but because task is now a steam, can be done with existing modules - e.g. multi-write-stream.
Week 6
--resume
optiontee
stream to filePushed down:
Week summary:
Week 7
[ ] formalize YAML/hackfile based DSLWeek Summary:
params
,input
, andoutput
, and series of tasks are arranged hierarchically using thesetask
is now gradually moving into many smaller reducers which a smaller scopeWeek 8
Week summary:
JSON.stringify(params)
of each taskWeek 9
Week 10
Week 11
Week 12
Extras/Pushed out
The text was updated successfully, but these errors were encountered: