Hello everyone,
I need some advice on how to represent the output of all the different tools inside a workflow in an external application. I am looking into using galaxy as a digital evidence processing tool. It is very important that i can access the intermediate sets of data created by every tool's output. Some have suggested the actual tools should populate a database and that the secondary(viewer) application should just retrieve the applicable data form there.
Any suggestions? Any input would be greatly appreciated.
Regards Fred
Fred,
I can probably offer some advice if you can clarify a little bit on how you want this to work. Do you want to run a workflow inside galaxy and then display all of the resultant data in an external viewer, initiated from galaxy? Or would all of the interaction happen outside of galaxy in this external application?
In either case, you're probably going to want to take a look into the Galaxy API. When you do, note that there are a few additions that will be available shortly for browsing histories.
-Dannon
On May 9, 2011, at 9:05 AM, Frederick van Staden wrote:
Hello everyone,
I need some advice on how to represent the output of all the different tools inside a workflow in an external application. I am looking into using galaxy as a digital evidence processing tool. It is very important that i can access the intermediate sets of data created by every tool's output. Some have suggested the actual tools should populate a database and that the secondary(viewer) application should just retrieve the applicable data form there.
Any suggestions? Any input would be greatly appreciated.
Regards Fred ___________________________________________________________ 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:
galaxy-dev@lists.galaxyproject.org