and in the future? Communication ‣ Can others understand what you’ve done at many different levels? ‣ Can others extend your analysis to their own work?
Tools Parameter Settings Input Data Pipelines/Workflows “High level” “Low level” BCOs } BCOs within this ecosystem • BCOs will be consumers of pipeline, tool, data, and parameters technologies • Some technologies will produce BCOs for use/resuse
large biomedical analyses on high- performance computing or the cloud ‣ datasets ‣ tools ‣ workflows ‣ visualizations Operating System Analysis Tools Parameter Settings Pipelines/Workflows
in a way that makes them portable and scalable across a variety of software and hardware environments" https://github.com/common-workflow-language/common-workflow-language Analysis Tools Parameter Settings Pipelines/Workflows
and interoperable sharing of Genomic data” More than just data: workflows, containers, etc. http://ga4gh.org/ Operating System Analysis Tools Parameter Settings Input Data Pipelines/Workflows
containers are available ‣ General: Dockerhub (https://hub.docker.com/) ‣ Bioinformatics: Dockstore (https://dockstore.org/), Biocontainers (https:// github.com/BioContainers) Many tools for creating containers by simplifying software installation ‣ Conda/Bioconda (https://conda.io/docs/): “Package, dependency and environment management for any language: Python, R, Ruby, Lua, Scala, Java, Javascript, C/ C++, FORTRAN” ‣ Install software plus dependencies on many different systems Operating System Analysis Tools
is the best way to ensure that BCOs can be easily used by non-technical users? Should execution platforms enforce intended BCO usage? What about clutter in the BCOs repository? How to search for and provide feedback on BCOs that yield good performance? What incentives can encourage sharing of BCOs?