SEQanswers

Go Back   SEQanswers > Bioinformatics > Bioinformatics



Similar Threads
Thread Thread Starter Forum Replies Last Post
How about the learning curve? Yepler Illumina/Solexa 8 08-12-2014 07:56 AM
MBD qPCR - shift in melt curve wanderingneuroscientist Epigenetics 0 04-07-2014 03:32 PM
RT-qPCR: which dilutions in calibration curve? bernardo_bello RNA Sequencing 0 12-04-2013 09:40 AM
feature response curve explanation Kennels Bioinformatics 0 06-05-2013 10:14 PM
New Miseq learning curve creeves Illumina/Solexa 18 08-17-2012 08:44 AM

Reply
 
Thread Tools
Old 02-14-2015, 12:22 AM   #1
mike.t
Member
 
Location: Spain

Join Date: Mar 2010
Posts: 36
Default Galaxy learning curve

Most of the students and postdocs that come to our group have no little or no bioinformatics experience so the first step is usually to teach them some basic command line operations. I just started to check out Galaxy as a tool to get them up and running and doing research more quickly. Given that Galaxy also has a significant learning curve, is it really going to save time and effort? I'm just curious what other people's experiences are.
mike.t is offline   Reply With Quote
Old 02-14-2015, 02:23 AM   #2
rikkomba
Junior Member
 
Location: andorra

Join Date: Oct 2009
Posts: 4
Default

It's not Galaxy that has a significant learning curve, it's Bioinformatics. The idea that using something like Galaxy will help skip months or years of practise is just silly.
By the time you know what tools to use and what parameters to choose, there is little left between using Galaxy and creating your own pipelines.
rikkomba is offline   Reply With Quote
Old 02-14-2015, 03:24 AM   #3
Bukowski
Senior Member
 
Location: Aberdeen, Scotland

Join Date: Jan 2010
Posts: 347
Default

I agree. Galaxy is an abstraction layer over what is essential practice - the art of passing data from one part of a pipeline to the next. They will be far more accomplished with command line basics at their disposal than being point and click experts in Galaxy.

I realise some might think this is something of an outmoded view, but if you hide the command line from people they'll never get to grips with the basic tools that make a bioinformaticians life much simpler. Awk is the perfect example of this.

Galaxy hides the discoveries of parallelism, the realisation that some things are IO bound, some things are CPU limiting. It stops you from thinking about the nature of what you are doing.

The paramaterisation - well that's just as essential in your own tools and in Galaxy. Blind default parameter acceptance is what you need to encourage the newbies out of. I dread to think how many RNA-Seq experiments are blindly pushed through Galaxy installations parameterised for mammalian data where the data is from from plants..

I take on intern (undergraduate) students each year, from a biology background with no previous bioinformatics experience. The first thing they get is a command line tutorial and a book on Perl (sorry, but the place is a historical Perl shop ).

Bash, Perl, Python, R - these are hard to explore in Galaxy. Yes I know there is the Tool Factory, but it just seems like an extra layer of cruft in the way of 'getting things done'.
Bukowski is offline   Reply With Quote
Old 02-14-2015, 08:39 AM   #4
karimse07
Junior Member
 
Location: africa

Join Date: Feb 2015
Posts: 8
Default Bioinformatics

need a Bioinformatics study partner , my skype:karimse07,mail:[email protected]
karimse07 is offline   Reply With Quote
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off




All times are GMT -8. The time now is 01:04 PM.


Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2018, vBulletin Solutions, Inc.
Single Sign On provided by vBSSO