Galaxy is not optimized for this kind of use case, I like to think of
it as sort of "file" centric - but it is clear more and more people
are using it to process data in this fashion. Hopefully someone chimes
in with better advice than I have :).
The way I would probably implement this is create a
Hi all,
We are working on a galaxy tool suite for data analysis.
We use a sqlite db to keep result data centralised between the different tools.
At one point the tool configuration options of a tool should be dependent on
the rows within a table of the sqlite db that is the output of the previo
Hi all,
We are working on a galaxy tool suite for data analysis.
We use a sqlite db to keep result data centralised between the different tools.
At one point the tool configuration options of a tool should be dependent on
the rows within a table of the sqlite db that is the output of the previo
ay already be in the works to support ToolShed. Imho, the JIT approach
is inherently cooler, even if potentially more challenging to get right.
Best of luck, and let us know it goes :)
Best,
Eric
From: galaxy-dev-boun...@lists.bx.psu.edu [galaxy-dev-boun...@lists.
Greetings,
I'm looking to add a tool that works with a custom datatype that would
dynamically generate input parameter options based on the dataset metadata.
For example,
A dataset of type foo contains metadata as follows:
descfields = ['label','description']
quantfields = ['qualityscore','oth
