Are you asking about compatibility staying on the same Galaxy
instance, or the harder problem of compatibility sharing workflows
between Galaxy servers?
Taking data from input Galaxy datasets should be fine, anything else
may not be portable. Even the relatively simple case of using
datafiles referenced via an example.loc file (e.g. BLAST databases)
would require the entries in the example.loc file be synchronised
between Galaxy instances, and the associated data files too.
On Fri, Aug 26, 2016 at 1:27 PM, Katherine Beaulieu
Would anyone be able to tell me the conditions which would make a tool
non-workflow compatible? I have a tool that imports files from a third party
application and auto-detects the file format. There is also the option to
upload multiple files at once so the tool always uploads at least two files.
From what I have described can anyone see why this tool would not be able to
send one of its files to the next tool in the chain, ex. a text manipulation
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:
To search Galaxy mailing lists use the unified search at: