Hi Peter,

After installing the clc testing galaxy wrapper I noticed there are still some static paths in the wrapper.
I'm in favor of expecting binaries in the system path, but maybe that's a matter of taste.

Greets, 

Eric Kuijt



On 30 October 2013 17:03, Peter Cock <p.j.a.cock@googlemail.com> wrote:
Hello all,

This is just to announce I am working on a wrapper for
"CLC Assembly Cell" which is the CLCbio commercial
command line assembly tool suite.
http://www.clcbio.com/products/clc-assembly-cell/

Our institute bought a licence primarily for use on plant
genomes where other assemblers at the time required
too much RAM to complete. This assembler is both fast
and low memory, which can be very useful.

Wrapper development here:
https://github.com/peterjc/pico_galaxy/tree/master/tools/clc_assembly_cell

Prototype releases will be on the Test Tool Shed (soon):
http://testtoolshed.g2.bx.psu.edu/view/peterjc/clc_assembly_cell

Stable Tool Shed releases will be here (later):
http://toolshed.g2.bx.psu.edu/view/peterjc/clc_assembly_cell

I would be interested to hear from anyone else with access to
a licensed copy of the tool interested in using it from Galaxy.
e.g. Is it reasonable to assume the tools are on the $PATH,
or is using a specific environment variable more helpful?

Regards,

Peter
___________________________________________________________
Please keep all replies on the list by using "reply all"
in your mail client.  To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
  http://lists.bx.psu.edu/

To search Galaxy mailing lists use the unified search at:
  http://galaxyproject.org/search/mailinglists/