Although it may not use the exact script on github they almost always reference exactly which published academic papers they model their analysis off of, and will update the analysis with a new model and paper reference as the field progresses. Doing this stuff at the command line is a steep-ish learning curve and everyone expects your questions. And again, you shouldn't feel like you can't turn to your colleagues for help. Provided you understand the convenience afforded by CLC that now isn't going to be available to you - more than just a bunch of buttons to click, CLC is doing a lot behind the scenes to manage the on-disk location of your data at various intermediate steps of processing, which you will now have to do yourself - you should be OK. You can get up to speed on command-line bioinformatics in about an afternoon - start with a tutorial about working in Bash - and while installation of packages is a classic pain point for the new bioinformatician, hopefully the rest of the group can help you get set up. The lab is aware of my lack of coding/script experience, but how fucked am I to get analyses working in this new lab? they wrote their own aligner, they don't just call to bowtie2 which is why CLC works on Windows.) At least last I checked. It's a good suite, don't get me wrong, but CLC runs its own implementations in Java - it's not a GUI over the standard tools in the field (i.e. CLC is basically a user interface wrapper around field standard scripts and tools
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |