Re: [galaxy-dev] GVL/Galaxy ver 18.01 instance error: R_COMM channel basic get exception: [Errno 32] Broken pipe

Hi Leon, list, this issue is now tracked here: https://github.com/galaxyproject/cloudlaunch/issues/140 Martin On Mon, Mar 26, 2018 at 5:14 AM Leon Parker wrote: > We just stood up our first ever Genomics Virtual Lab appliance and used it > to spool up a Galaxy

Re: [galaxy-dev] Best practices for utilising Unique Molecular Indexing (UMI's)

Hi Tony, sounds like you need is the Je-Suite version 2 which we will release soon-ish. In this version, the new “je debarcode” module allows you to define an unlimited number of FASTQ input together with their layout (describing BARCODE, UMI and SAMPLE positions). One can define an

[galaxy-dev] Best practices for utilising Unique Molecular Indexing (UMI's)

Hi We are currently seeing a number of methods that are utilising the power of unique molecular indexing. Unfortunately, there is no consensus on how libraries should be configured, and therefore no consensus for how to deal with them within Galaxy. Often libraries that have the UMI placed

[galaxy-dev] GVL/Galaxy ver 18.01 instance error: R_COMM channel basic get exception: [Errno 32] Broken pipe

We just stood up our first ever Genomics Virtual Lab appliance and used it to spool up a Galaxy Cluster for doing bioinformatics work. We’ve worked a bit with the original “Cloudman” application and the ver 17.05 revision of Galaxy and it has worked fine, but we decided it might be a good time