![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Performance bottlenecks in sequence analysis pipelines | DanielChubb | Bioinformatics | 1 | 11-04-2011 08:34 AM |
Softwares/Pipelines for ChIP Seq Analysis | ayushraman | Bioinformatics | 0 | 09-16-2011 05:37 PM |
Bioinformatics pipelines/software for repeat identification | parulk | Bioinformatics | 0 | 07-27-2011 12:36 PM |
Any survey or great intro on pipelines of deep sequencing? | bbzz | Bioinformatics | 0 | 08-02-2010 07:14 PM |
![]() |
|
Thread Tools |
![]() |
#1 |
Junior Member
Location: UK Join Date: Jun 2010
Posts: 3
|
![]()
This is perfect for computational biology work. Good documentation too.
I write all my code into this framework now. ruffus.org.uk You're welcome! |
![]() |
![]() |
![]() |
#2 |
Senior Member
Location: Marburg, Germany Join Date: Oct 2009
Posts: 110
|
![]()
Ruffus is nice, but I never could figure out how to parameterize the generated jobs (for different objects etc...).
I have my own pipeline now based on function-wrapping job objects that I probably should pour into the net one of these days if anyone was interested. It supports multiprocessing, code change detection (on the level of the wrapped functions), resume (d'oh) and of course the usually file time checking, as well as partial fault tolerance (a broken job will only affect itself and the jobs depended on it, no the other jobs). |
![]() |
![]() |
![]() |
#3 |
Junior Member
Location: United Kingdom Join Date: Sep 2010
Posts: 1
|
![]()
Hi. Just found this by Google.
I am the primary developer of Ruffus. Ruffus is designed to be light-weight, flexible and easy to use but the fundamental approach is different enough to normal scripting that some of my users have to work through the whole of the tutorial before "getting it". We are always looking for new ways to present the documentation or even adjust the semantics to make things clearer / easier. Feedback so far has been tremendously useful and driven most of the development of Ruffus. I am here to help people figure things out / hand-hold if necessary. So if anyone wants to send me (on- or off-line) a quick conceptual sketch of what you want to do / what the pipeline is supposed to do, I am happy to write some quick code or point you in the right direction. Of course, if you have rolled your own pipeline code already, you probably have quite different ideas about how things should be done! ![]() |
![]() |
![]() |
![]() |
Tags |
automation, pipeline, python, ruffus, script |
Thread Tools | |
|
|