Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New Caper 2.0.0. is out.
There is no significant update for cloud-based backends (
gcp
andaws
).Most updates are for HPC USERS to fix various annoying Singularity/Conda and cluster (SLURM, ...) issues.
For HPC users
HPC users must initialize Caper's configuration file. This will add new important parameters and description/instruction for them. Please make a copy of your original configuration file (
~/.caper/default.conf
) and then initialize it withcaper init
.Follow instruction comments in the configuration file. Most parameters will be the same as those in the original configuration file.
For Conda/Singularity users on HPC
YOU DO NOT NEED TO ACTIVATE CONDA ENVIRONMENT BEFORE RUNNING PIPELINES. Just make sure that pipeline's Conda environment is correctly installed and add
--conda
to the command linecaper run ... --conda
. New Caper 2.0.0 runs each WDL task inside a Conda environment.We strongly recommend to use Singularity for new ENCODE ATAC-seq and ChIP-seq pipelines (both >=v2.0.0).
caper run ... --singularity
if your cluster support Singularity.Added resource parameters for HPC
Added a resource parameter for each HPC backend so that users can customize resource parameters for the job submission command line (
squeue
,qsub
, ...) according to their cluster configuration. It will be appended to the job submission command line. WDL syntax is allowed in${}
notation. Please find details in the configuration file after initialization. See README for details.slurm
backend:slurm-resource-param
sge
backend:sge-resource-param
pbs
backend:pbs-resource-param
lsf
backend:lsf-resource-param