Hi Piotr,
I guess you need to work a lot with symlinks.
link all your Galaxy inputs to a temp folder, provide the path to the temp folder to KNIME + a path to a second tempfolder with the results and tell Galaxy to collect all files int the result folder.
Cheers, Bjoern
On 11.09.2015 16:26, Piotr Grabowski wrote:
Hello Galaxy Devs and Deployers!
I have a rather basic question about how to handle custom tools in Galaxy (I'm fresh to this framework). I am trying to link my local Galaxy with KNIME workflow that we developed in our group. I am trying to link it via a bash script that is running headless KNIME and it seems almost to work, but...
In order for this workflow to run I have to specify in the command line things like result folder or where a dynamically generated parameter file is located.
This parameter file is generate by the bash script before running KNIME. The paths will be always dynamic, depending on users etc. So I can't simply hard-code the path. Is there a way to make bash aware of where the current Galaxy user's folders and files are upon execution in Galaxy?
Below a simplified scheme of what I am doing:
User uploads txt file -> Clicks RUN -> bash script builds a parameter file (gawk ... >> param.csv) -> /knime run workflow --set the path to the parameter .csv file + set export folder
Any ideas ? Best, Piotr
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: https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/