2020
DOI: 10.1093/gigascience/giaa121
|View full text |Cite
|
Sign up to set email alerts
|

Unifying package managers, workflow engines, and containers: Computational reproducibility with BioNix

Abstract: Motivation A challenge for computational biologists is to make our analyses reproducible—i.e. to rerun, combine, and share, with the assurance that equivalent runs will generate identical results. Current best practice aims at this using a combination of package managers, workflow engines, and containers. Results We present BioNix, a lightweight library built on the Nix deployment system. BioNix manages software dependencies,… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

2022
2022
2024
2024

Publication Types

Select...
5
1

Relationship

1
5

Authors

Journals

citations
Cited by 7 publications
(6 citation statements)
references
References 26 publications
0
6
0
Order By: Relevance
“…To our opinion, the main difference between the Guix and Nix systems is, for the former a continuity from the high-level declarative configuration to the core which allows to adapt or extend the Guix system, and for the latter, on one hand “Nix expressions” written in a DSL specifically designed to define these “pure functions” (derivation), and on the other hand another language for the core. This difference is slight in practice but emphasized by the data processing workflow engines Guix Workflow Language (GWL) based on Guix and BioNix 22 based on Nix ( https://youtu.be/pwYhPqaUiGg , https://youtu.be/tpLcwfRXL28 ). Last, to our knowledge, the Nix system does not provide yet a mechanism easing the time travel.…”
Section: Resultsmentioning
confidence: 99%
See 1 more Smart Citation
“…To our opinion, the main difference between the Guix and Nix systems is, for the former a continuity from the high-level declarative configuration to the core which allows to adapt or extend the Guix system, and for the latter, on one hand “Nix expressions” written in a DSL specifically designed to define these “pure functions” (derivation), and on the other hand another language for the core. This difference is slight in practice but emphasized by the data processing workflow engines Guix Workflow Language (GWL) based on Guix and BioNix 22 based on Nix ( https://youtu.be/pwYhPqaUiGg , https://youtu.be/tpLcwfRXL28 ). Last, to our knowledge, the Nix system does not provide yet a mechanism easing the time travel.…”
Section: Resultsmentioning
confidence: 99%
“…To be fully reproducible one computational environment must be defined by (i) the source code of the software and libraries used (ii) the various options or configuration are required at build-time or run-time and (iii) the complete graph that fixes all the dependencies. Package manager like Nix 22 and Guix are designed around these three requirements. By using Nix or Guix, scientists are now able to easily share their computational environment.…”
Section: Discussionmentioning
confidence: 99%
“…A bionix (57) pipeline was used to process samples from sequencing data to variant calls. Sequences were aligned to Genome Reference Consortium Human Build 38 (GRCh38) using minimap2 v2.17 (58), and also to Mus Musculus reference GRCm38.…”
Section: Methodsmentioning
confidence: 99%
“…A bionix 47 pipeline was used to process samples from sequencing data to variant calls. Sequences were aligned to Genome Reference Consortium Human Build 38 (GRCh38) using minimap2 v2.17, 48 and also to the Mus Musculus reference GRCm38 for PDX.…”
Section: Genome Sequencing Analysismentioning
confidence: 99%