You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Conda environment name change (since v2.2.0 or 6/13/2022)
7
7
8
-
9
-
10
-
## Download new Caper>=2.1
11
-
12
-
New Caper is out. You need to update your Caper to work with the latest ENCODE ATAC-seq pipeline.
13
-
```bash
14
-
$ pip install caper --upgrade
15
-
```
16
-
17
-
## Local/HPC users and new Caper>=2.1
18
-
19
-
There are tons of changes for local/HPC backends: `local`, `slurm`, `sge`, `pbs` and `lsf`(added). Make a backup of your current Caper configuration file `~/.caper/default.conf` and run `caper init`. Local/HPC users need to reset/initialize Caper's configuration file according to your chosen backend. Edit the configuration file and follow instructions in there.
20
-
```bash
21
-
$ cd~/.caper
22
-
$ cp default.conf default.conf.bak
23
-
$ caper init [YOUR_BACKEND]
8
+
Pipeline's Conda environment's names have been shortened to work around the following error:
24
9
```
25
-
26
-
In order to run a pipeline, you need to add one of the following flags to specify the environment to run each task within. i.e. `--conda`, `--singularity` and `--docker`. These flags are not required for cloud backend users (`aws` and `gcp`).
27
-
```bash
28
-
# for example
29
-
$ caper run ... --singularity
10
+
PaddingError: Placeholder of length '80' too short in package /XXXXXXXXXXX/miniconda3/envs/
30
11
```
31
12
32
-
For Conda users, **RE-INSTALL PIPELINE'S CONDA ENVIRONMENT AND DO NOT ACTIVATE CONDA ENVIRONMENT BEFORE RUNNING PIPELINES**. Caper will internally call `conda run -n ENV_NAME CROMWELL_JOB_SCRIPT`. Just make sure that pipeline's new Conda environments are correctly installed.
13
+
You need to reinstall pipeline's Conda environment. It's recommended to do this for every version update.
33
14
```bash
34
-
$ scripts/uninstall_conda_env.sh
35
-
$ scripts/install_conda_env.sh
15
+
$ bash scripts/uninstall_conda_env.sh
16
+
$ bash scripts/install_conda_env.sh
36
17
```
37
18
38
19
## Introduction
@@ -51,31 +32,44 @@ The ATAC-seq pipeline protocol specification is [here](https://docs.google.com/d
51
32
52
33
1) Make sure that you have Python>=3.6. Caper does not work with Python2. Install Caper and check its version >=2.0.
53
34
```bash
54
-
$ python --version
55
35
$ pip install caper
36
+
37
+
# use caper version >= 2.3.0 for a new HPC feature (caper hpc submit/list/abort).
38
+
$ caper -v
56
39
```
57
-
2)Make a backup of your Caper configuration file `~/.caper/default.conf` if you are upgrading from old Caper(<2.0.0). Reset/initialize Caper's configuration file. Read Caper's [README](https://github.com/ENCODE-DCC/caper/blob/master/README.md) carefully to choose a backend for your system. Follow the instruction in the configuration file.
40
+
2) Read Caper's [README](https://github.com/ENCODE-DCC/caper/blob/master/README.md) carefully to choose a backend for your system. Follow the instruction in the configuration file.
58
41
```bash
59
-
# make a backup of ~/.caper/default.conf if you already have it
42
+
# this will overwrite the existing conf file ~/.caper/default.conf
43
+
# make a backup of it first if needed
60
44
$ caper init [YOUR_BACKEND]
61
45
62
-
# then edit ~/.caper/default.conf
46
+
# edit the conf file
63
47
$ vi ~/.caper/default.conf
64
48
```
65
49
66
50
3) Git clone this pipeline.
67
-
> **IMPORTANT**: use `~/atac-seq-pipeline/atac.wdl` as `[WDL]` in Caper's documentation.
4) (Optional for Conda users) Install pipeline's Conda environments if you don't have Singularity or Docker installed on your system. We recommend to use Singularity instead of Conda. If you don't have Conda on your system, install [Miniconda3](https://docs.conda.io/en/latest/miniconda.html).
56
+
4) (Optional for Conda) **DO NOT USE A SHARED CONDA. INSTALL YOUR OWN [MINICONDA3](https://docs.conda.io/en/latest/miniconda.html) AND USE IT.**Install pipeline's Conda environments if you don't have Singularity or Docker installed on your system. We recommend to use Singularity instead of Conda.
75
57
```bash
58
+
# check if you have Singularity on your system, if so then it's not recommended to use Conda
59
+
$ singularity --version
60
+
61
+
# check if you are not using a shared conda, if so then delete it or remove it from your PATH
62
+
$ which conda
63
+
64
+
# change directory to pipeline's git repo
76
65
$ cd atac-seq-pipeline
77
-
# uninstall old environments (<2.0.0)
66
+
67
+
# uninstall old environments
78
68
$ bash scripts/uninstall_conda_env.sh
69
+
70
+
# install new envs, you need to run this for every pipeline version update.
71
+
# it may be killed if you run this command line on a login node.
72
+
# it's recommended to make an interactive node and run it there.
79
73
$ bash scripts/install_conda_env.sh
80
74
```
81
75
@@ -96,22 +90,23 @@ You can use URIs(`s3://`, `gs://` and `http(s)://`) in Caper's command lines and
96
90
97
91
According to your chosen platform of Caper, run Caper or submit Caper command line to the cluster. You can choose other environments like `--singularity` or `--docker` instead of `--conda`. But you must define one of the environments.
98
92
99
-
The followings are just examples. Please read [Caper's README](https://github.com/ENCODE-DCC/caper) very carefully to find an actual working command line for your chosen platform.
93
+
PLEASE READ [CAPER'S README](https://github.com/ENCODE-DCC/caper) VERY CAREFULLY BEFORE RUNNING ANY PIPELINES. YOU WILL NEED TO CORRECTLY CONFIGURE CAPER FIRST. These are just example command lines.
94
+
100
95
```bash
101
-
# Run it locally with Conda (You don't need to activate it, make sure to install Conda envs first)
96
+
# Run it locally with Conda (DO NOT ACTIVATE PIPELINE'S CONDA ENVIRONEMT)
102
97
$ caper run atac.wdl -i https://storage.googleapis.com/encode-pipeline-test-samples/encode-atac-seq-pipeline/ENCSR356KRQ_subsampled.json --conda
103
98
104
-
# Or submit it as a leader job (with long/enough resources) to SLURM (Stanford Sherlock) with Singularity
105
-
# It will fail if you directly run the leader job on login nodes
Copy file name to clipboardExpand all lines: docs/build_genome_database.md
+2-6Lines changed: 2 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,11 +8,7 @@
8
8
9
9
# How to build genome database
10
10
11
-
1. [Install Conda](https://conda.io/miniconda.html). Skip this if you already have equivalent Conda alternatives (Anaconda Python). Download and run the [installer](https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh). Agree to the license term by typing `yes`. It will ask you about the installation location. On Stanford clusters (Sherlock and SCG4), we recommend to install it outside of your `$HOME` directory since its filesystem is slow and has very limited space. At the end of the installation, choose `yes` to add Miniconda's binary to `$PATH` in your BASH startup script.
3. Choose `GENOME` from `hg19`, `hg38`, `mm9` and `mm10` and specify a destination directory. This will take several hours. We recommend not to run this installer on a login node of your cluster. It will take >8GB memory and >2h time.
0 commit comments