Skip to content

Commit 59d1ca3

Browse files
Update IPR docs
1 parent 45bddfe commit 59d1ca3

File tree

11 files changed

+24
-30
lines changed

11 files changed

+24
-30
lines changed

docs/ipr/core_variants/copy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Copy Variants
22

3-
Copy variants should be passed to the IPR python adapter in the main report content JSON.
3+
Copy variants should be passed to the python adapter in the main report content JSON.
44

55
```json
66
{

docs/ipr/core_variants/expression.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ The kbCategory field is how IPR knows this row/entry should be treated as a vari
1111

1212
Computing the various expression metrics is largely optional and done prior by the user prior to upload/report-creation. These metrics are displayed to the analyst reviewing the case along with the variant status. The standard fields we provide input for are listed below.
1313

14-
As with the other variants, these should be passed to the IPR python adapter in the main report content JSON.
14+
As with the other variants, these should be passed to the python adapter in the main report content JSON.
1515

1616
```json
1717
{
@@ -22,7 +22,7 @@ As with the other variants, these should be passed to the IPR python adapter in
2222
}
2323
```
2424

25-
Each variant is an object which may contain any of the following fields (in addition to the required fields). Examples of how these fields are calculated can be found in the [scripting examples section](../../scripting/RNA_Expression_Metrics).
25+
Each variant is an object which may contain any of the following fields (in addition to the required fields). Examples of how these fields are calculated can be found in the [scripting examples section](../scripting/RNA_Expression_Metrics.ipynb).
2626

2727
{%
2828
include-markdown "../includes/expressionVariants.md"
@@ -80,7 +80,7 @@ The use can optionally include expression density plots to allow the user to vie
8080

8181
!!! Info
8282

83-
These will be passed to the report upload function via the [images section](../../optional_analyses/images) of the JSON input
83+
These will be passed to the report upload function via the [images section](../optional_analyses/images.md) of the JSON input
8484

8585
key: `expDensity\.(\S+)`
8686

docs/ipr/core_variants/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
11
# About
22

3-
The core variant types are: expression variants, copy number variants, structural variants, and small mutations. All of these variants are matched against GraphKB and annotated by the python IPR adapter during upload to IPR.
3+
The core variant types are: expression variants, copy number variants, structural variants, signature variants and small mutations. All of these variants are matched against GraphKB and annotated by the python adapter during upload to IPR.

docs/ipr/core_variants/mutations.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Small Mutations
22

3-
Small mutations are composed of indels and single nucleotide variants. These should be passed to the IPR python adapter in the main report content JSON.
3+
Small mutations are composed of indels and single nucleotide variants. These should be passed to the python adapter in the main report content JSON.
44

55
```json
66
{

docs/ipr/core_variants/structural.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Structural Variants
22

3-
Structural variants should be passed to the IPR python adapter in the main report content JSON.
3+
Structural variants should be passed to the python adapter in the main report content JSON.
44

55
```json
66
{

docs/ipr/index.md

Lines changed: 3 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,7 @@
11
# About IPR
22

3-
Integrated Pipeline Reports (IPR) is the main reporting application of IPR. It is a web application
4-
that is used to review and curate reports which summarize the interpretation of molecular data from
5-
precision oncology patients.
3+
Integrated Pipeline Reports (IPR) is the main reporting application of PORI. It is a web application that is used to review and curate reports which summarize the interpretation of molecular data from precision oncology patients.
64

7-
This project is modularized across three repositories: [web client](https://github.com/bcgsc/pori_ipr_client),
8-
[REST API](https://github.com/bcgsc/pori_ipr_api), and a [python adapter](https://github.com/bcgsc/pori_ipr_python).
9-
The API and web client are servers and are provided as docker containers. The python adapter is
10-
used to build reports and upload them into IPR.
5+
This project is modularized across two repositories: a [web client](https://github.com/bcgsc/pori_ipr_client) and a [REST API](https://github.com/bcgsc/pori_ipr_api); both are servers and are provided as docker containers. It is also relying on the IPR utilities found in the [PORI Python Adapter](https://github.com/bcgsc/pori_python), used to build reports and upload them into IPR.
116

12-
Reports in IPR are divided into a series of sections. These are either: created by the IPR python adaptor (ex. knowledge base matches section); manually curated post-report creation (ex. analyst comments); or generated beforehand and included in the content passed to IPR via the python adaptor (ex. optional analyses).
7+
Reports in IPR are divided into a series of sections. These are either: created by the PORI python adaptor (ex. knowledge base matches section); manually curated post-report creation (ex. analyst comments); or generated beforehand and included in the content passed to IPR via the python adaptor (ex. optional analyses).

docs/ipr/optional_analyses/burden.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ of samples. The "role" determines with comparator these values are calculated in
3232
## Comparators and Roles
3333

3434
The role used by the mutation burden data is linked to the mutation burden images in the report
35-
that is created by the [comparators input](../comparators).
35+
that is created by the [comparators input](comparators.md).
3636

3737
The images use the following key: `mutationBurden\.(barplot|density|legend)_(sv|snv|indel)\.(primary|secondary|tertiary|quaternary)`
3838

docs/ipr/optional_analyses/circos_plots.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ There are a number of fields for including circos plots in the report. Circos pl
44

55
!!! Info
66

7-
These will be passed to the report upload function via the [images section](../images) of the JSON input
7+
These will be passed to the report upload function via the [images section](images.md) of the JSON input
88

99
## Copy Number Circos Plot
1010

docs/ipr/optional_analyses/expression_correlation.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,13 +6,13 @@ keys: `expression.chart`, `expression.legend`
66

77
!!! Info
88

9-
These will be passed to the report upload function via the [images section](../images) of the JSON input
9+
These will be passed to the report upload function via the [images section](images.md) of the JSON input
1010

1111
This plot represents the pairwise correlation of the RNA expression of the current sample against samples from a variety of reference distributions. Often this is used as a *sanity check* of the diagnosis. It is expected that the sample should correlate most highly with other samples within the disease distribution that is most closely related to the diagnosis. It is also expected that samples with a lower tumour content/purity may show correlation with their biopsy site.
1212

1313
![expression correlation plot](../images/expression_correlation.png)
1414

15-
An example of how this type of plot is created can be found in the scripting examples [here](../../scripting/RNA_Expression_Similarity).
15+
An example of how this type of plot is created can be found in the scripting examples [here](../scripting/RNA_Expression_Similarity.ipynb).
1616

1717
## Subtyping Plots
1818

docs/ipr/optional_analyses/immune.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ Example cell type values are
7474

7575
!!! Info
7676

77-
These will be passed to the report upload function via the [images section](../images) of the JSON input
77+
These will be passed to the report upload function via the [images section](images.md) of the JSON input
7878

7979
key: `cibersort.cd8_positive_t-cell_scatter`
8080

@@ -88,7 +88,7 @@ key: `cibersort.combined_t-cell_scatter`
8888

8989
!!! Info
9090

91-
These will be passed to the report upload function via the [images section](../images) of the JSON input
91+
These will be passed to the report upload function via the [images section](images.md) of the JSON input
9292

9393
[MiXCR Publication](https://pubmed.ncbi.nlm.nih.gov/25924071/)
9494

0 commit comments

Comments
 (0)