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
Clone and install regtools by running the following:
@@ -26,6 +37,8 @@ Clone and install regtools by running the following:
26
37
make
27
38
```
28
39
40
+
Installation should take 1-5 minutes.
41
+
29
42
For convienience we also maintain a docker image available at [https://hub.docker.com/r/griffithlab/regtools/](https://hub.docker.com/r/griffithlab/regtools/)
30
43
31
44
## Usage:
@@ -34,6 +47,34 @@ For convienience we also maintain a docker image available at [https://hub.docke
34
47
regtools --help
35
48
```
36
49
50
+
If one wishes to test their installation, we include test data under `test_data`.
51
+
52
+
Here's an example command using that data along with the example output. This should run in under a minute.
Copy file name to clipboardExpand all lines: docs/commands/cis-splice-effects-identify.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,9 +13,9 @@ The `cis-splice-effects identify` command is used to identify splicing misregula
13
13
| Input | Description |
14
14
| ------ | ----------- |
15
15
| variants.vcf | Variant call in VCF format from which to look for cis-splice-effects.|
16
-
| alignments.bam | Aligned RNAseq BAM/CRAM produced with a splice aware aligner, that has been indexed for example with `samtools index`. We have tested this command with alignments from TopHat.|
16
+
| alignments.bam | Aligned RNAseq BAM/CRAM produced with a splice aware aligner, that has been indexed for example with `samtools index`. We have tested this command with alignments from HISAT2, TopHat2, STAR, kallisto, and minimap2.|
17
17
| ref.fa | The reference FASTA file. The donor and acceptor sequences used in the "splice-site" column of the annotated junctions are extracted from the FASTA file. |
18
-
| annotations.gtf | The GTF file specifies the transcriptome that is used to annotate the junctions and variants. For examples, the Ensembl GTFs for release78 are [here](ftp://ftp.ensembl.org/pub/release-78/gtf/).|
18
+
| annotations.gtf | The GTF file specifies the transcriptome that is used to annotate the junctions and variants. For examples, the Ensembl GTFs for release 106 are [here](http://ftp.ensembl.org/pub/release-106/gtf/).|
19
19
20
20
**Note** - Please make sure that the version of the annotation GTF that you use corresponds with the version of the assembly build (ref.fa) and that the co-ordinates in the VCF file are also from the same build.
21
21
@@ -26,7 +26,7 @@ The `cis-splice-effects identify` command is used to identify splicing misregula
26
26
| -o STR | Output file containing the aberrant splice junctions with annotations. [STDOUT]|
| -j STR | Output file containing the aberrant junctions in BED12 format. |
29
-
| -s INT | Strand specificity of RNA library preparation, where 0 = unstranded/XS, 1 = first-strand/RF, 2 = second-strand/FR. This option is required. If your alignments contain XS tags, these will be used in the "unstranded" mode. If you are unsure, we have created this [table](https://rnabio.org/module-09-appendix/0009/12/01/StrandSettings/) to help. |
29
+
| -s INT | Strand specificity of RNA library preparation, where the options XS, use XS tags provided by aligner; RF, first-strand; FR, second-strand. This option is required. If your alignments contain XS tags, these will be used in the "unstranded" mode. If you are unsure, we have created this [table](https://rnabio.org/module-09-appendix/0009/12/01/StrandSettings/) to help. |
30
30
| -w INT | Window size in b.p to identify splicing events in. The tool identifies events in variant.start +/- w basepairs. Default behaviour is to look at the window between previous and next exons. |
31
31
| -e INT | Maximum distance from the start/end of an exon to annotate a variant as relevant to splicing, the variant is in exonic space, i.e a coding variant. [3]|
32
32
| -i INT | Maximum distance from the start/end of an exon to annotate a variant as relevant to splicing, the variant is in intronic space. [2]|
Copy file name to clipboardExpand all lines: docs/commands/junctions-annotate.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,7 @@ Gene Annotation databases such as Ensembl/RefSeq/UCSC etc. The goal of the annot
17
17
| ------ | ----------- |
18
18
| junctions.bed | The BED file with the junctions that have be annotated. This file has to be in the BED12 format. One recommended way of obtaining this file is by running `regtools junctions extract`. See [here](junctions-extract.md) for more details.|
19
19
| ref.fa | The reference FASTA file. The donor and acceptor sequences used in the "splice-site" column are extracted from the FASTA file. |
20
-
| annotations.gtf | The GTF file specifies the transcriptome that is used to annotate the junctions. For examples, the Ensembl GTFs for release78 are [here](ftp://ftp.ensembl.org/pub/release-78/gtf/)|
20
+
| annotations.gtf | The GTF file specifies the transcriptome that is used to annotate the junctions. For examples, the Ensembl GTFs for release 106 are [here](http://ftp.ensembl.org/pub/release-106/gtf/).||
Copy file name to clipboardExpand all lines: docs/commands/junctions-extract.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Overview of `junctions extract` command
2
2
3
-
The `junctions extract` command can be used to extract exon-exon junctions from an RNAseq BAM file. The output is a BED file in the BED12 format. We have tested this command with alignments from TopHat and by comparing the exon-exon junctions with the `junctions.bed` file produced from TopHat.
3
+
The `junctions extract` command can be used to extract exon-exon junctions from an RNAseq BAM file. The output is a BED file in the BED12 format. We have tested this command with alignments from HISAT2, TopHat2, STAR, kallisto, and minimap2 and by comparing the exon-exon junctions with the `junctions.bed` file produced from TopHat.
4
4
5
5
6
6
## Usage
@@ -23,7 +23,7 @@ The `junctions extract` command can be used to extract exon-exon junctions from
23
23
| -o | File to write output to. STDOUT by default.|
24
24
| -r | Region to extract junctions in. This is specified in the format "chr:start-end". If not specified, junctions are extracted from the entire BAM file.|
25
25
| -h | Display help message for this command.|
26
-
| -s | Strand specificity of RNA library preparation, where 0 = unstranded/XS, 1 = first-strand/RF, 2 = second-strand/FR. This option is required. If your alignments contain XS tags, these will be used in the "unstranded" mode. If you are unsure, we have created this [table](https://rnabio.org/module-09-appendix/0009/12/01/StrandSettings/) to help.
26
+
| -s | Strand specificity of RNA library preparation, where the options XS, use XS tags provided by aligner; RF, first-strand; FR, second-strand. This option is required. If your alignments contain XS tags, these will be used in the "unstranded" mode. If you are unsure, we have created this [table](https://rnabio.org/module-09-appendix/0009/12/01/StrandSettings/) to help.
0 commit comments