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
Copy file name to clipboardExpand all lines: README.md
+28-25Lines changed: 28 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,8 +39,9 @@
39
39
40
40
Welcome to the official repository of ROADIES, a novel pipeline for inferring phylogenetic species trees directly from raw genomic assemblies. ROADIES offers a fully automated, scalable, and easy-to-use solution, eliminating manual steps and allowing flexible control over the trade-off between accuracy and runtime.
41
41
42
-
**For a detailed overview of ROADIES' features and configuration options, please visit our [Wiki](https://turakhialab.github.io/ROADIES/).**
42
+
### 🟡 For a detailed overview of ROADIES' features and configuration options, please visit our [Wiki](https://turakhialab.github.io/ROADIES/).
43
43
44
+
### 🟡 If you encounter issues while running the pipeline, please refer to [this page](https://turakhialab.github.io/ROADIES/troubleshooting/) for common errors and troubleshooting tips.
44
45
<br>
45
46
46
47
<divalign="center">
@@ -60,7 +61,7 @@ Please follow any of the options below to install ROADIES in your system.
60
61
61
62
### <aname="conda"></a> Option 1: Install via Bioconda (Recommended)
@@ -111,22 +112,22 @@ You will be able to find the contents of the repository within this ROADIES fold
111
112
112
113
If you would like to install ROADIES using DockerHub, follow these steps:
113
114
114
-
1. Pull the ROADIES image from DockerHub:
115
+
**Step 1:** Pull the ROADIES image from DockerHub:
115
116
116
117
```
117
118
docker pull ang037/roadies:latest
118
119
```
119
-
2. Launch a container:
120
+
**Step 2:** Launch a container:
120
121
121
122
```
122
123
docker run -it ang037/roadies:latest
123
124
```
124
125
125
-
These commands will launch the Docker container in interactive mode, with the roadies_env environment activated and the working directory set to the ROADIES repository containing all necessary files. Once you are able to access the ROADIES repository, refer to the [Quick Start](#start) to run the pipeline.
126
+
These commands will launch the Docker container in interactive mode, with the `roadies_env` environment activated and the working directory set to the ROADIES repository containing all necessary files. Once you are able to access the ROADIES repository, refer to the [Quick Start](#start) to run the pipeline.
126
127
127
128
### <aname="docker"></a> Option 3: Install via Local Docker Build
This will save the datasets on a separate `test/test_data` folder within the repository
202
203
203
-
2. Run the pipeline
204
+
**Step 2:** Run the ROADIES pipeline
204
205
205
206
#### IMPORTANT: ROADIES by default runs multiple iterations for generating highly accurate trees. For quick testing, use `--noconverge` to run a single iteration.
- Final **UNROOTED** newick tree saved as `roadies.nwk` in a separate `output_files` folder.
221
-
- Intermediate files (if `--noconverge` not used) saved in a separate `converge_files` folder.
221
+
**Default mode:**
222
+
Final species tree (in Newick format) for individual iterations (latest one will be the most confident and accurate tree) will be saved in separate `converge_files/iteration_<iteration_number>` folders.
222
223
224
+
**If `--noconverge` is used:**
225
+
Final species tree (in Newick format) will be saved as `roadies.nwk` in a separate `output_files` folder.
223
226
224
227
#### NOTE: ROADIES outputs unrooted trees by default. You can reroot trees on your own or use the provided `reroot.py` script in `workflow/scripts/` (given a reference rooted species tree as input).
If you want to run ROADIES with your own datasets, follow these steps:
231
234
232
-
1. Specify Input Dataset:
235
+
**Step 1:** Specify Input Dataset:
233
236
234
237
- Edit `config.yaml` file (found in the ROADIES directory - `config` folder).
235
238
- Update the `GENOMES` field with paths to your `.fa` or `.fa.gz` genome assemblies. Ensure all input genomic assemblies are in `.fa` or `.fa.gz` format and named according to the species' name (e.g., `Aardvark.fa`).
@@ -240,12 +243,12 @@ If you want to run ROADIES with your own datasets, follow these steps:
240
243
faSplit byname <input_dir> <output_dir>
241
244
```
242
245
243
-
2. Configure Other Parameters:
246
+
**Step 2:** Configure Other Parameters:
244
247
245
248
- Modify other parameters in `config.yaml` as needed.
246
249
- Refer to detailed settings on the [Wiki](https://turakhialab.github.io/ROADIES/).
The output species tree (unrooted) in Newick formatwill be saved as `roadies.nwk` in the `output_files` folder.
270
+
Final unrooted species tree (in Newick format) for individual iterations (latest one will be the most confident and accurate tree) will be saved in separate `ALL_OUT_DIR/iteration_<iteration_number>` folders (`ALL_OUT_DIR` is configured in `config/config.yaml`).
268
271
269
-
### For troubleshooting, contributing, or SLURM cluster usage, refer to [Wiki](https://turakhialab.github.io/ROADIES/)
272
+
### For contributing to the code, or SLURM cluster usage, refer to [Wiki](https://turakhialab.github.io/ROADIES/contribution)
Copy file name to clipboardExpand all lines: docs/troubleshooting.md
+36-23Lines changed: 36 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,38 @@
1
1
# Troubleshooting Steps
2
2
3
-
## 1. Mamba not found in the shell
3
+
## Error 1. Issues with PASTA
4
+
5
+
### Solution
6
+
7
+
When running the pipeline, if you encounter that the pipeline fails by the failure of PASTA, please install PASTA from source by executing the following commands. Please run the following steps from the main ROADIES repository directory (after doing `cd ROADIES`) - within the activated Conda environment:
Also, in the `align.smk` file (inside the `workflow/rules` directory of the ROADIES repository), please replace any instance of `pasta.py` with `python pasta/run_pasta.py`, AND
17
+
`run_seqtools.py` with `python pasta/run_seqtools.py`.
18
+
19
+
After doing this change, please re-run the ROADIES pipeline.
20
+
21
+
## Error 2. Environment conflict
22
+
23
+
### Solution
24
+
25
+
If you encounter the following error message - `"ls: relocation error: /lib64/libacl.so.1: symbol getxattr, version ATTR_1.0 not defined in file libattr.so.1 with link time reference"`, please run the following command to resolve it:
The 'mamba'command is not available in the shell /usr/bin/bash that will be used by Snakemake. You have to ensure that it is in your PATH, e.g., first activating the conda base environment with `conda activate base`.The mamba package manager (https://github.com/mamba-org/mamba) is a fast and robust conda replacement. It is the recommended way of using Snakemake's conda integration. It can be installed with `conda install -n base -c conda-forge mamba`. If you still prefer to use conda, you can enforce that by setting `--conda-frontend conda`.
19
47
```
20
-
21
-
### Cause
22
-
23
-
The `mamba` package manager is missing or not available in the environment.
48
+
This means `mamba` package manager is missing or not available in the environment.
24
49
25
50
### Solution
26
51
@@ -56,42 +81,30 @@ cmd = [
56
81
python run_roadies.py --cores 16
57
82
```
58
83
59
-
## 2. Conda not recognized
60
-
61
-
### Cause
84
+
## Error 4. Conda not recognized
62
85
63
-
Conda is not added to your system's PATH.
86
+
This can happen if conda is not added to your system's PATH.
64
87
65
88
### Solution
66
89
67
-
Ensure conda is added to the PATH by running the following commands:
90
+
To resolve this, please ensure conda is added to the PATH by running the following commands:
68
91
69
92
```bash
70
93
export PATH="$HOME/miniconda3/bin:$PATH"
71
94
source~/.bashrc
72
95
```
73
96
74
-
## 3. Singularity issues
75
-
76
-
### Cause
77
-
78
-
Problems arise when trying to run the pipeline with Singularity.
97
+
## Error 5. Handling dependencies (glibc)
79
98
80
99
### Solution
81
100
82
-
We recommend using Docker instead of Singularity. Ensure Docker is installed and running on your system. We have also provided Bioconda support for users who face issues with Singularity.
83
-
84
-
## 4. Handling dependencies (glibc)
85
-
86
101
Ensure that the glibc version on your system is updated to 2.29 or higher. Update your system libraries if necessary. Otherwise you may encounter this error:
87
102
88
103
```bash
89
104
workflow/scripts/lastz_32: /lib64/libm.so.6: version 'GLIBC_2.29' not found
90
105
```
91
106
92
-
## 5. PASTA fails with insufficient core count
93
-
94
-
### Cause
107
+
## Error 6. PASTA fails with insufficient core count
95
108
96
109
Pasta fails when the number of cores is insufficient for the number of instances.
0 commit comments