Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
B
bioinfo_utils
Manage
Activity
Members
Labels
Plan
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Blaise LI
bioinfo_utils
Commits
b1c06d55
Commit
b1c06d55
authored
5 years ago
by
Blaise Li
Browse files
Options
Downloads
Patches
Plain Diff
Explaning how to build and use the container.
parent
0c337568
No related branches found
No related tags found
No related merge requests found
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
singularity/Makefile
+5
-0
5 additions, 0 deletions
singularity/Makefile
singularity/README_singularity.md
+42
-0
42 additions, 0 deletions
singularity/README_singularity.md
with
47 additions
and
0 deletions
singularity/Makefile
0 → 100644
+
5
−
0
View file @
b1c06d55
all
:
run_pipeline
# Should depend on the rest of the repository.
run_pipeline
:
run_pipeline.def
sudo
singularity build run_pipeline run_pipeline.def
This diff is collapsed.
Click to expand it.
singularity/README_singularity.md
0 → 100644
+
42
−
0
View file @
b1c06d55
Running the pipelines using singularity
=======================================
This folder contains a recipe to build a singularity container for the
workflows and their dependencies.
To build the container run the following command:
sudo singularity build run_pipeline run_pipeline.def
Of course, you need singularity, and administrative rights to do that (that's
part of how singularity works).
This folder also contain a shell script wrapper and aliases that will run one
of the workflows using the container. The built container should be present in
the same directory as the wrapper and aliases.
Each alias will run a specific pipeline, depending on its name.
There may be several aliases for a same pipeline.
Here are the aliases available for each pipeline:
*
sRNA-seq
-
`run_sRNA-seq_pipeline`
-
`run_small_RNA-seq_pipeline`
*
GRO-seq
-
`run_GRO-seq_pipeline`
-
`run_PRO-seq_pipeline`
*
RNA-seq
-
`run_RNA-seq_pipeline`
*
Degradme-seq
-
`run_Degradome-seq_pipeline`
*
Ribo-seq
-
`run_Ribo-seq_pipeline`
*
iCLIP (which has a special "non-seq" name)
-
`run_iCLIP-seq_pipeline`
-
`run_iCLIP_pipeline`
### TODO
The container takes a long time to build. Maybe it should be split into smaller
bits, used by a larger one.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment