Hi,
First of all, thank you to the authors and maintainers for making this tool available on the Galaxy ToolShed!
I am reaching out on behalf of the European Biodiversa+ GINAMO project. Within this framework, we are developing standardized Galaxy workflows to facilitate the computation of genetic Essential Biodiversity Variables (EBVs) and genetic diversity indicators.
As part of our pipeline, we are using this tool to estimate pairwise FST using Bayescan. However, we are currently facing a limitation regarding the tool's outputs when integrating it into a Galaxy workflow. At the moment, only the text file containing the run progress information is exposed and available to be passed to subsequent tools in the workflow. The actual data outputs generated by Bayescan are not captured as distinct Galaxy datasets.
To allow full automation and seamless integration into Galaxy workflows, it would be extremely valuable to explicitly define the various Bayescan output files (bayescan_fst, bayescan_Verif, bayescan_AccRte and the sel file call bayescan) within the tool's XML wrapper. This would expose them as proper history items that can be plugged into downstream analysis tools.
Would it be possible to update the wrapper to support these additional outputs? We would be more than happy to help test any updates or provide example datasets if needed.
Thank you very much for your time,
Best regards,
Laura from GINAMO project
Hi,
First of all, thank you to the authors and maintainers for making this tool available on the Galaxy ToolShed!
I am reaching out on behalf of the European Biodiversa+ GINAMO project. Within this framework, we are developing standardized Galaxy workflows to facilitate the computation of genetic Essential Biodiversity Variables (EBVs) and genetic diversity indicators.
As part of our pipeline, we are using this tool to estimate pairwise FST using Bayescan. However, we are currently facing a limitation regarding the tool's outputs when integrating it into a Galaxy workflow. At the moment, only the text file containing the run progress information is exposed and available to be passed to subsequent tools in the workflow. The actual data outputs generated by Bayescan are not captured as distinct Galaxy datasets.
To allow full automation and seamless integration into Galaxy workflows, it would be extremely valuable to explicitly define the various Bayescan output files (bayescan_fst, bayescan_Verif, bayescan_AccRte and the sel file call bayescan) within the tool's XML wrapper. This would expose them as proper history items that can be plugged into downstream analysis tools.
Would it be possible to update the wrapper to support these additional outputs? We would be more than happy to help test any updates or provide example datasets if needed.
Thank you very much for your time,
Best regards,
Laura from GINAMO project