Skip to content

Commit 7aad8fa

Browse files
authored
Update README.md
1 parent f483fad commit 7aad8fa

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

README.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,23 +9,32 @@ You must have an active user account and access credentials for the Alma server.
99
2. Configure Mamba
1010
The application relies on Mamba to manage environments. Run the following commands to initialize Mamba:
1111
```bash
12+
srun --pty --mem=12GB -c4 -t 15:00:00 -p interactive bash
1213
mamba init
1314
source ~/.bashrc
1415
```
1516

1617
3. Change the Nextflow Assets Directory
17-
By default, Nextflow stores pipeline files in your home directory, which has limited storage on Alma. We strongly recommend redirecting the asset path to your SCRATCH space:
18+
By default, Nextflow stores pipeline files in your home directory, which has limited storage on Alma. We strongly recommend redirecting the asset path to your SCRATCH space. Open ~/.bashrc using vi and write the following command:
1819
```bash
1920
export NXF_ASSETS=/data/scratch/personal/path/<your_username>/.nextflow/assets
21+
```
22+
Reload your .bashrc:
23+
```bash
2024
source ~/.bashrc
2125
```
2226

2327
4. Configure Git Access for ICR Pipelines
2428
If you're using one of our ICR-maintained pipelines (e.g., icr-nanopore-pauses), you'll need to configure Git access for Nextflow to pull them directly from our GitLab instance.
2529

2630
a. Set the SCM (Source Code Management) configuration path:
31+
Open ~/.bashrc using vi and write the following command:
2732
```bash
2833
export NXF_SCM_FILE=/data/scratch/personal/path/<your_username>/.nextflow/scm
34+
```
35+
36+
Reload your .bashrc:
37+
```bash
2938
source ~/.bashrc
3039
```
3140

0 commit comments

Comments
 (0)