[galaxy-dev] Share history (or change history ownership) through the Galaxy API?

Hello, Is it possible to share a history with a user (by user name) or change ownership through the Galaxy API? I didn't see any example doing this. Thanks. Cheers, Daniel -- Daniel Sobral, Bioinformatics Unit Instituto Gulbenkian de Ciência

Re: [galaxy-dev] Share history (or change history ownership) through the Galaxy API?

-central.readthedocs.org/en/latest/lib/galaxy.webapps.galaxy.api.html#module-galaxy.webapps.galaxy.api.history_contents Martin, Galaxy Team On Wed, Jan 15, 2014 at 1:36 PM, Daniel Sobral dsob...@igc.gulbenkian.pt mailto:dsob...@igc.gulbenkian.pt wrote: Hello, Is it possible

Re: [galaxy-dev] Uploading gzipped fastq files through the API

. = Daniel Sobral Next Generation Sequencing Data Analyst IGC - Instituto Gulbenkian de Ciencias e-mail dsob...@igc.gulbenkian.pt = -- Daniel Sobral, Bioinformatics Unit Instituto Gulbenkian de Ciência

[galaxy-dev] Restrict tool usage by certain users

Hello, At the moment I don't think there is a way to restrict usage of specific tool(s) to specific user(s). Is anyone thinking on developing this kind of functionality? I guess it might be a bit complicated to implement? I guess an easier alternative is to have different galaxy instances

[galaxy-dev] Fixed Thread number in certain tools

Hello, For certain tools, like bwa or blast, there is a non-configurable number of threads to use inside the tool xml. This is inconvenient for certain cluster configurations, where what we want is division of a job into multiple jobs (I guess this is what is intended by the parallel tag), and

[galaxy-dev] Hard-links and sshfs

Hello, My instance of galaxy is running on an sshfs mount. The problem comes when I set the new_file_path in the universe_wsgi.ini to be a folder within that sshfs. When I upload something, the hard link in the mkstemp_ln function fails because of apparent limitations of sshfs with hard links. It

[galaxy-dev] Local Toolshed misbehaviours?

Hello, I've installed a local toolshed server in http://myserver/toolshed/ (served by Apache) I am able to run it and create a repository with a tool. In my local galaxy server (http://myserver/galaxy/) I am able to see the repositories in that toolshed server, but when I try to install the

Re: [galaxy-dev] Local Toolshed misbehaviours?

paster log say when you get the 404 error trying to install? You can see the paster log by running the following from your Galaxy installation directory when your tool shed is running. tail -f community_webapp.log Greg Von Kuster On Mar 16, 2012, at 4:34 AM, Daniel Sobral wrote: Hello

Re: [galaxy-dev] Variable number of inputs in Workflow (or optional inputs)

to my reply in case they have a simpler way of doing this or other advice. Best, Jen Galaxy team On 3/5/12 7:32 AM, Daniel Sobral wrote: Hi, I wanted to build a workflow where the first step would be a tool that can have a variable number of inputs (e.g. a series). It seems that I need

[galaxy-dev] Running galaxy in a cluster as if it was local

Hi, We're trying to setup a galaxy server, but where we want some of the tools to run on a cluster. This cluster is supporting mosix so at the moment we cannot use any of the drmaa stuff available (or can we?). The way we're setting it up at the moment is to run the command we want to run on the

[galaxy-dev] Tool that outputs html report

the original html structure? One way of cheating is maybe zipping the output and provide the zip file as data? Thanks, Daniel Sobral ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions