Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitad01c94

Browse files
authored
Merge pull request#235 from bcgsc/release/v2.2.9
Release/v2.2.9
2 parents74cc132 +e7127e7 commitad01c94

File tree

16 files changed

+305
-282
lines changed

16 files changed

+305
-282
lines changed

‎README.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -14,11 +14,11 @@
1414
The general[MAVIS](http://mavis.bcgsc.ca) pipeline consists of six main stages
1515

1616
- convert
17-
-[cluster](http://mavis.bcgsc.ca/docs/latest/mavis.cluster.html#mavis-cluster)
18-
-[validate](http://mavis.bcgsc.ca/docs/latest/mavis.validate.html#mavis-validate)
19-
-[annotate](http://mavis.bcgsc.ca/docs/latest/mavis.annotate.html#mavis-annotate)
20-
-[pairing](http://mavis.bcgsc.ca/docs/latest/mavis.pairing.html#mavis-pairing)
21-
-[summary](http://mavis.bcgsc.ca/docs/latest/mavis.summary.html#mavis-summary)
17+
-[cluster](https://mavis.readthedocs.io/en/latest/package/mavis/cluster)
18+
-[validate](https://mavis.readthedocs.io/en/latest/package/mavis/validate)
19+
-[annotate](https://mavis.readthedocs.io/en/latest/package/mavis/annotate)
20+
-[pairing](https://mavis.readthedocs.io/en/latest/package/mavis/pairing)
21+
-[summary](https://mavis.readthedocs.io/en/latest/package/mavis/summary)
2222

2323
##Getting Help
2424

@@ -41,12 +41,12 @@ a github issue to our [github page](https://github.com/bcgsc/mavis/issues) or co
4141

4242
##Install Instructions
4343

44-
There are 3 major steps to setting up and installing[MAVIS](http://mavis.bcgsc.ca). If you are a developer contributing to mavis, please see the[instructions for developers page](http://mavis.bcgsc.ca/docs/latest/development.html) instead
44+
There are 3 major steps to setting up and installing[MAVIS](http://mavis.bcgsc.ca). If you are a developer contributing to mavis, please see the[instructions for developers page](https://mavis.readthedocs.io/en/latest/development) instead
4545

4646
###1. Install Aligner
4747

4848
In addition to the python package dependencies,[MAVIS](http://mavis.bcgsc.ca) also requires an aligner to be installed.
49-
Currently the only aligners supported are[blat](http://mavis.bcgsc.ca/docs/latest/glossary.html#term-blat) and[bwa mem](http://mavis.bcgsc.ca/docs/latest/glossary.html#term-bwa).
49+
Currently the only aligners supported are[blat](https://mavis.readthedocs.io/en/latest/glossary/#blat) and[bwa mem](https://mavis.readthedocs.io/en/latest/glossary/#bwa).
5050
For MAVIS to run successfully the aligner must be installed and accessible on the path.
5151
If you have a non-standard install you may find it useful to edit the PATH environment variable. For example
5252

@@ -55,7 +55,7 @@ export PATH=/path/to/directory/containing/blat/binary:$PATH
5555
```
5656

5757
[blat](http://mavis.bcgsc.ca/docs/latest/glossary.html#term-blat) is the default aligner. To configure MAVIS to use[bwa mem](http://mavis.bcgsc.ca/docs/latest/glossary.html#term-bwa) as a default instead, use the
58-
[MAVIS environment variables](http://mavis.bcgsc.ca/configuration.html#environment-variables). Make sure to specify BOTH of the variables below to change the default aligner.
58+
[MAVIS environment variables](https://mavis.readthedocs.io/en/latest/configuration/settings/). Make sure to specify BOTH of the variables below to change the default aligner.
5959

6060
```bash
6161
export MAVIS_ALIGNER='bwa mem'
@@ -108,7 +108,7 @@ This will install mavis and its python dependencies into eggs inside the cloned
108108

109109
###3. Build or Download Reference Files
110110

111-
After[MAVIS](http://mavis.bcgsc.ca) is installed the[reference files](http://mavis.bcgsc.ca/docs/latest/mavis_input.html#reference-input-files) must be generated (or downloaded) before it can be run. A simple bash script to download the hg19 reference files and generate a MAVIS environment file is provided under mavis/tools for convenience.
111+
After[MAVIS](http://mavis.bcgsc.ca) is installed the[reference files](https://mavis.readthedocs.io/en/latest/inputs/reference) must be generated (or downloaded) before it can be run. A simple bash script to download the hg19 reference files and generate a MAVIS environment file is provided under mavis/tools for convenience.
112112

113113
```bash
114114
cd /path/to/where/you/want/to/put/the/files
@@ -118,7 +118,7 @@ source reference_inputs/hg19_env.sh
118118
```
119119

120120
Once the above 3 steps are complete[MAVIS](http://mavis.bcgsc.ca) is ready to be run.
121-
See the MAVIS[tutorial](http://mavis.bcgsc.ca/docs/latest/pipeline.html#mavis-mini-tutorial) to learn about running MAVIS.
121+
See the MAVIS[tutorial](https://mavis.readthedocs.io/en/latest/tutorials/mini) to learn about running MAVIS.
122122

123123

124124
##Citation

‎docs/background/theory.md

Lines changed: 22 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ which are adjacent in the mutant genome
2525
There are many ways that single reads or paired-end reads can act as
2626
support for an SV call.
2727

28-
![](../../images/read_evidence.svg)
28+
![](../images/read_evidence.svg)
2929

3030
In the figure above the red rectangle represents a deletion structural
3131
variant. The arrows are types of single or paired-end reads supporting
@@ -58,7 +58,7 @@ For a deletion, we expect the flanking reads to be in the normal
5858
orientation but that the fragment size should be abnormal (for large
5959
deletions).
6060

61-
![](../../images/read_pairs_deletion.svg)
61+
![](../images/read_pairs_deletion.svg)
6262

6363
Flanking read pair evidence for a deletion event. the read pairs will
6464
have a larger than expected fragment size when mapped to the reference
@@ -74,7 +74,7 @@ strand.
7474

7575
####Insertion
7676

77-
![](../../images/read_pairs_insertion.svg)
77+
![](../images/read_pairs_insertion.svg)
7878

7979
Flanking read pair evidence for an insertion event. The read pairs
8080
will have a smaller than expected fragment size when mapped to the
@@ -90,7 +90,7 @@ strand.
9090

9191
####Duplication
9292

93-
![](../../images/read_pairs_duplication.svg)
93+
![](../images/read_pairs_duplication.svg)
9494

9595
Flanking read pair evidence for a tandem duplication event. The read
9696
pairs will have an abnormal orientation but still the same strands as
@@ -102,29 +102,29 @@ orientation.
102102

103103
####Inversion
104104

105-
![](../../images/read_pairs_inversion_LL.svg)
105+
![](../images/read_pairs_inversion_LL.svg)
106106

107107
Flanking read pair evidence for an inversion. Both breakpoints have
108108
left orientation.
109109

110110

111-
![](../../images/read_pairs_inversion_RR.svg)
111+
![](../images/read_pairs_inversion_RR.svg)
112112

113113
Flanking read pair evidence for an inversion. Both breakpoints have
114114
right orientation.
115115

116116

117117
####Translocation
118118

119-
![](../../images/read_pairs_translocation_LR.svg)
119+
![](../images/read_pairs_translocation_LR.svg)
120120

121121
Flanking read pair evidence for a translocation. (B1) the first
122122
breakpoint with a left orientation. (B2) the second breakpoint with a
123123
right
124124
orientation.
125125

126126

127-
![](../../images/read_pairs_translocation_RL.svg)
127+
![](../images/read_pairs_translocation_RL.svg)
128128

129129
Flanking read pair evidence for a translocation. (B1) the first
130130
breakpoint with a right orientation. (B2) the second breakpoint with a
@@ -134,14 +134,14 @@ orientation.
134134

135135
####Inverted Translocation
136136

137-
![](../../images/read_pairs_translocated_inversion_LL.svg)
137+
![](../images/read_pairs_translocated_inversion_LL.svg)
138138

139139
Flanking read pair evidence for an inverted translocation. Both
140140
breakpoints have left
141141
orientation.
142142

143143

144-
![](../../images/read_pairs_translocated_inversion_RR.svg)
144+
![](../images/read_pairs_translocated_inversion_RR.svg)
145145

146146
Flanking read pair evidence for an inverted translocation. Both
147147
breakpoints have right
@@ -158,7 +158,7 @@ be used as compatible flanking evidence for an insertion (in the same
158158
region) and similarly flanking pairs which support an insertion may be
159159
compatible flanking evidence for a duplication
160160

161-
![](../../images/compatible_flanking_pairs.svg)
161+
![](../images/compatible_flanking_pairs.svg)
162162

163163
The event depicted above may be called as either a duplication or an
164164
insertion (depending on the input call). If the even were called as a
@@ -172,7 +172,7 @@ apply.
172172

173173
###Calculating the Evidence Window
174174

175-
![](../../images/read_pair_definitions.svg)
175+
![](../images/read_pair_definitions.svg)
176176

177177
Basic Terms used in describing read pairs are shown above: fragment
178178
size: the distance between the pair; read length: the length of the
@@ -217,7 +217,7 @@ stdev = math.sqrt(sum(X) / len(X))
217217
This gives us an idea of when to judge an fragment size as abnormal and
218218
where we expect our normal read pairs fragment sizes to fall.
219219

220-
![](../../images/fragment_sizes_histogram.svg)
220+
![](../images/fragment_sizes_histogram.svg)
221221

222222
Distribution of fragment sizes (absolute values) of proper read pairs.
223223
The black curve representings the fit for a normal distribution using
@@ -265,7 +265,7 @@ evidence window. We use the
265265
limit of how large the range can be. This is further refined taking into
266266
account the range spanned by the[flanking read pair](../../glossary/#flanking-read-pair) evidence and the position of the opposing breakpoint.
267267

268-
![call by flanking reads](../../images/call_breakpoint_by_flanking_reads.svg)
268+
![call by flanking reads](../images/call_breakpoint_by_flanking_reads.svg)
269269

270270
Calculation of the left-oriented breakpoint by flanking reads. Reads
271271
mapped to the breakpoint are shown in grey. The read on the right (black
@@ -277,7 +277,7 @@ interval.
277277

278278
###Determining Flanking support
279279

280-
![flanking support](../../images/flanking_pairs_fragment_sizes_deletion.svg)
280+
![flanking support](../images/flanking_pairs_fragment_sizes_deletion.svg)
281281

282282
After a breakpoint has been called we can narrow the interval of
283283
expected fragment sizes using the size of the event. (Left) The colored
@@ -297,7 +297,7 @@ The following decision tree is used in classifying events based on their
297297
breakpoints. Only valid combinations have been shown. see
298298
`mavis.breakpoint.BreakpointPair.classify`
299299

300-
![classifying](../../images/classification_tree.svg)
300+
![classifying](../images/classification_tree.svg)
301301

302302
Classification Decision Tree. The above diagram details the decsion
303303
logic for classifying events based on the orientation, strand and
@@ -344,7 +344,7 @@ breakpoint (useful in the case of a potential promoter swap); what genes
344344
encompassed between the breakpoints (for example in a deletion event the
345345
genes that would be deleted).
346346

347-
![gene annotations](../../images/annotations_summary.svg)
347+
![gene annotations](../images/annotations_summary.svg)
348348

349349
Gene level annotations at each breakpoint. Note: genes which fall
350350
between a breakpoint pair, encompassed genes, will not be present for
@@ -368,7 +368,7 @@ a splice-site, it is not clear what the processed fusion transcript may
368368
be. MAVIS will calculate all possibilities according to the following
369369
model.
370370

371-
![splicing pattern](../../images/splicing_pattern_default.svg)
371+
![splicing pattern](../images/splicing_pattern_default.svg)
372372

373373
The default splicing pattern is a list of pairs of donor and acceptor
374374
splice sites
@@ -377,14 +377,14 @@ For a given list of non-abrogated splice sites (listed 5' to 3' on the
377377
strand of the transcript) donor splice sites are paired with all
378378
following as seen below
379379

380-
![multiple donors](../../images/splicing_pattern_multiple_donors.svg)
380+
![multiple donors](../images/splicing_pattern_multiple_donors.svg)
381381

382382
Multiple abrogated acceptors sites. As one can see above this
383383
situation will result in 3 different splicing patterns depending on
384384
which donor is paired with the 2nd acceptor
385385
site
386386

387-
![multiple acceptors](../../images/splicing_pattern_multiple_acceptors.svg)
387+
![multiple acceptors](../images/splicing_pattern_multiple_acceptors.svg)
388388

389389
Multiple abrogated donor sites. As one can see above this situation
390390
will result in 3 different splicing patterns depending on which acceptor
@@ -410,7 +410,7 @@ different splicing patterns:
410410
(`mavis.constants.SPLICE_TYPE.COMPLEX`{.interpreted-text
411411
role="attr"})
412412

413-
![Splicing scenarios](../../images/splicing_model.svg)
413+
![Splicing scenarios](../images/splicing_model.svg)
414414

415415

416416

@@ -431,7 +431,7 @@ rise to the following basic cases.
431431
the breakpoint.
432432

433433

434-
![exonic splicing](../../images/breakpoint_prediction_exonic.svg)
434+
![exonic splicing](../images/breakpoint_prediction_exonic.svg)
435435

436436
(A-D) The breakpoint lands in an exon and the five prime portion of
437437
the transcript is retained. (A) The original splicing pattern showing

‎docs/configuration/performance.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ cpu requirements depending on what the user is trying to analyze. See
1212

1313
##Validation Resources
1414

15-
![](../../images/colo829_tumour_validation_resource_req.png)
15+
![](../images/colo829_tumour_validation_resource_req.png)
1616

1717
Resource Requirements (MAVIS 1.8.0) for each validation job of the
1818
COLO829 tumour genome. The BAM file for the tumour genome is 127GB.
@@ -29,7 +29,7 @@ regards to time elapsed. However the memory requirements remained more
2929
constant which is expected since, unlike validation, anntotation does
3030
not read more data in for more events.
3131

32-
![](../../images/colo829_tumour_annotation_resource_req.png)
32+
![](../images/colo829_tumour_annotation_resource_req.png)
3333

3434
Resource Requirements (MAVIS 1.8.0) for each annotation job of the
3535
COLO829 tumour genome. The events which passed validation (see above)

‎docs/configuration/pipeline.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ The setup step of MAVIS is set up to use a job scheduler on a
66
compute cluster. will generate submission scripts and a wrapper bash
77
script for the user to execute on their cluster head node.
88

9-
![](../../images/pipeline_options.svg)
9+
![](../images/pipeline_options.svg)
1010

1111
The MAVIS pipeline is highly configurable. Some pipeline steps
1212
(cluster, validate) are optional and can be automatically skipped. The
@@ -36,7 +36,7 @@ mavis schedule -o /path/to/output_dir --submit
3636

3737
This will submit a series of jobs with dependencies.
3838

39-
![](../../images/pipeline_dependency_graph.svg)
39+
![](../images/pipeline_dependency_graph.svg)
4040

4141
Dependency graph of MAVIS jobs for the standard pipeline setup. The
4242
notation on the arrows indicates the SLURM setting on the job to add the

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp