Skip to content

Commit 35e5fef

Browse files
authored
Merge pull request #50 from Eeeeelias/master
Update docs
2 parents c14a816 + 9718e3b commit 35e5fef

2 files changed

Lines changed: 23 additions & 23 deletions

File tree

docs/README.md

Lines changed: 22 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -40,22 +40,22 @@ The isoform-level analysis investigates the difference in interactions between i
4040

4141
As input (Figure 2), isoform-level analysis accepts the name of a gene, an Ensebml identifier of a gene, and an Ensembl identifier of a transcript. A user can also put multiple identifiers separated by a comma. Then a user should select an organism. Currently, DIGGER contains the data from Homo sapiens and Mus musculus.
4242

43-
<img src=https://github.com/OlgaVT/DIGGER/blob/patch-1/docs/Figure2.png/>
43+
<img src="./Figure2.png">
4444
<p align="center">
4545
<em>Figure 2: Input genes are BAG1 and NCK2; the chosen organism is Homo sapiens.</em>
4646
</p>
4747

4848
If there is information about interactions for the isoforms of interest, the resulting window will show a summary of information about them in a network ('Network') and tabular views ('Queries'). A user can switch between them in the menu in the upper left corner.
4949

5050
A network view (Figure 3) provides information about known/predicted interactions of query isoforms. Predicted DDIs toggle bars allow the addition of predicted DDIs of different levels of confidence. Interactions lost or impaired due to splicing are marked as dashed lines. A user could also adjust the view of the network by enabling/disabling physics and adjusting the height of a canvas.
51-
<img src=https://github.com/OlgaVT/DIGGER/blob/patch-1/docs/Figure3.png/>
51+
<img src="./Figure3.png">
5252
<p align="center">
5353
<em>Figure 3: A network view for chosen isoforms of BAG1 and NCK2.</em>
5454
</p>
5555

5656
The tabular view (Figure 4) presents the information about query isoforms or all annotated protein-coding isoforms if a query consists of a gene name/identifier. The Pfam domains column contains information about known PFAM domains of a resulting protein. "Present / Missing interacting domains in the isoform" column demonstrates the percentage of interactions possibly lost or impaired for this particular isoform due to alternative splicing. To further investigate the impact of a splicing event, a user can click 'Visualize'.
5757

58-
<img src=https://github.com/OlgaVT/DIGGER/blob/patch-1/docs/Figure4.png/>
58+
<img src="./Figure4.png">
5959
<p align="center">
6060
<em>Figure 4: a tabular view on isoforms of BAG1 and NCK2.
6161
A transcript BAG-207 possibly lost a PPI due to alternative splicing that leads to removing the part of the protein that encodes a domain PF02179. A transcript NCK-202 also lost a PPI due to splicing of domains PF00017 and PF14604.</em>
@@ -65,36 +65,36 @@ A "Visualize" window, provides five different visualization panels: Overview, Pr
6565

6666
The Overview window header (Figure 5) shows the general information about the transcript.
6767

68-
<img src=https://github.com/OlgaVT/DIGGER/blob/patch-1/docs/Figure5.png/>
68+
<img src="./Figure5.png">
6969
<p align="center">
7070
<em>Figure 5: General information about a transcript</em>
7171
</p>
7272

7373
This page also contains a scheme of transcript exons and mapped Pfam domains, and the table of all exons and Pfam domains mapped on exons (Figures 6, 7).
7474

75-
<img src=https://github.com/OlgaVT/DIGGER/blob/patch-1/docs/Figure6A.png/>
76-
<img src=https://github.com/OlgaVT/DIGGER/blob/patch-1/docs/Figure6B.png/>
75+
<img src="./Figure6A.png">
76+
<img src="./Figure6B.png">
7777
<p align="center">
7878
<em>Figure 6: Comparing BAG1-210 and BAG-207 isoforms, one can detect that these isoforms differ in exons that encode a domain PF02179 as well as exons that contain interacting residues</em>
7979
</p>
8080

81-
<img src=https://github.com/OlgaVT/DIGGER/blob/patch-1/docs/Figure7A.png/>
82-
<img src=https://github.com/OlgaVT/DIGGER/blob/patch-1/docs/Figure7B.png/>
81+
<img src="./Figure7A.png">
82+
<img src="./Figure7B.png">
8383
<p align="center">
8484
<em>Figure 7: Comparing NCK-201 and NCK-202 isoforms, one can detect that these isoforms differ in exons that encode domains PF14604, the second PF00018, PF00017 as well as exons that contain interacting residues</em>
8585
</p>
8686

8787
The Protein view shows all known direct interactors of an isoform. View mode can be changed from PPI to PPI-DDI view (Figure 8).
8888

89-
<img src=https://github.com/OlgaVT/DIGGER/blob/patch-1/docs/Figure8.png/>
89+
<img src="./Figure8.png">
9090
<p align="center">
9191
<em>Figure 8: PPI-DDI view for BAG1-207 depicts possibly missing interactions with BAG3, HSPA1A, HSPA4, and HSPA8</em>
9292
</p>
9393

9494
Interaction View (Figure 9) allows investigation into details of the PPI between a query isoform and all known and predicted interactors. The interactors can be chosen from the **Select Interaction Partner Menu** (just tick the box with the interaction of interest there).
9595

9696
<p align="center">
97-
<img src=https://github.com/OlgaVT/DIGGER/blob/patch-1/docs/Figure9.png/ width="400" align="center">
97+
<img src="./Figure9.png" width="400" align="center">
9898
</p>
9999
<p align="center">
100100
<em>Figure 9: Interaction View of BAG1-207 isoform. An interaction with HSPA8 might be lost due to alternative splicing of PF02179</em>
@@ -103,15 +103,15 @@ Interaction View (Figure 9) allows investigation into details of the PPI between
103103
Domain View (Figure 10) shows all interactors known for a particular domain.
104104

105105
<p align="center">
106-
<img src=https://github.com/OlgaVT/DIGGER/blob/patch-1/docs/Figure10.png/ width="400" align="center">
106+
<img src="./Figure10.png" width="400" align="center">
107107
</p>
108108
<p align="center">
109109
<em>Figure 10: Splicing out a domain PF02179 in the isoform BAG1-207 leads to missing PPIs with BAG3, HSPA1A, HSPA4, and HSPA8</em>
110110
</p>
111111

112112
Other isoforms View (Figure 11) again depicts the table of all other known protein-coding isoforms of a gene.
113113
<p align="center">
114-
<img src=https://github.com/OlgaVT/DIGGER/blob/patch-1/docs/Figure11.png/>
114+
<img src="./Figure11.png">
115115
</p>
116116
<p align="center">
117117
<em>Figure 11: All transcripts of BAG1</em>
@@ -124,7 +124,7 @@ The Exon-level analysis investigates the consequences of exon skipping events to
124124
In addition to input (Figure 12) as in isoform-level analysis, exon-level analysis accepts an Ensebml identifier of an exon, an Ensembl identifier of a gene with the coordinates of an exon. A user can also put multiple identifiers separated by a comma. Then a user should select an organism.
125125

126126
<p align="center">
127-
<img src=https://github.com/OlgaVT/DIGGER/blob/patch-1/docs/Figure12.png/>
127+
<img src="./Figure12.png">
128128
</p>
129129
<p align="center">
130130
<em>Figure 12: An input exon is exon ENSE00003569638 from BAG1; the organism is Homo sapiens</em>
@@ -133,7 +133,7 @@ In addition to input (Figure 12) as in isoform-level analysis, exon-level analys
133133
Results of the exon analysis consist of DomainView, ProteinView, InteractionView, and the table of Proteins that use this exon. DomainView, ProteinView, and InteractionView are similar to Isoform-level analysis but for an exon of interest. DomainView additionally shows the information about the corresponding Pfam domain with a link to the Pfam and 3did database (Figure 13).
134134

135135
<p align="center">
136-
<img src=https://github.com/OlgaVT/DIGGER/blob/patch-1/docs/Figure13.png/>
136+
<img src="./Figure13.png">
137137
</p>
138138
<p align="center">
139139
<em>Figure 13: A DomainView for and exon ENSE00003569638 </em>
@@ -142,7 +142,7 @@ Results of the exon analysis consist of DomainView, ProteinView, InteractionView
142142
A table "Proteins that use this exon" (Figure 14) reports the list of all protein-coding isoforms that encodes this exon:
143143

144144
<p align="center">
145-
<img src=https://github.com/OlgaVT/DIGGER/blob/patch-1/docs/Figure14.png/>
145+
<img src="./Figure14.png">
146146
</p>
147147
<p align="center">
148148
<em>Figure 14: A table "Proteins that use this exon" for an exon ENSE00003569638 </em>
@@ -152,15 +152,15 @@ A table "Proteins that use this exon" (Figure 14) reports the list of all protei
152152
## Network-level analysis
153153
Network analysis investigates the systematic impact of alternative splicing events on the PPIs. As input (Figure 15), Network-level analysis accepts the list of genes, transcripts, proteins, or a transcript count file and constructs a subnetwork from this list.
154154
<p align="center">
155-
<img src=https://github.com/OlgaVT/DIGGER/blob/patch-1/docs/Figure15.png/>
155+
<img src="./Figure15.png">
156156
</p>
157157
<p align="center">
158158
<em>Figure 15: An example input for Network-level analysis </em>
159159
</p>
160160

161161
If interactions between isoforms are known, the isoforms are connected to the subnetworks, and the interactions are marked as lost or present as well as based on the interaction evidence (Figure 16). For further exploration, the network can be downloaded in SIF or GraphML formats.
162162
<p align="center">
163-
<img src=https://github.com/OlgaVT/DIGGER/blob/patch-1/docs/Figure16.png/>
163+
<img src="./Figure16.png">
164164
</p>
165165
<p align="center">
166166
<em>Figure 16: An example output for Network-level analysis </em>
@@ -191,7 +191,7 @@ For MAJIQ:
191191
</p>
192192

193193
<p align="center">
194-
<img src=https://github.com/OlgaVT/DIGGER/blob/patch-1/docs/FigureNEASE.png/>
194+
<img src="./FigureNEASE.png">
195195
</p>
196196
<p align="center">
197197
<em>Figure 17: NEASE starting page </em>
@@ -212,23 +212,23 @@ NEASE contains three further types of analysis: enrichment analysis, pathway ana
212212

213213
NEASE edge enrichment supports the following ontologies:
214214

215-
Homo sapiens:
215+
#### Homo sapiens:
216216
- PharmGKB
217217
- HumanCyc
218218
- Wikipathways
219219
- Reactome
220220
- KEGG
221221

222-
Mus musculus
222+
#### Mus musculus
223223
- KEGG
224224
- Reactome
225225
- MouseCyc
226226

227-
Type in the name of the ontology of interest and click the "Run enrichment" button. The resulting table will show the list of pathways, the list of genes that lost/impaired interactions with these pathways due to alternative splicing, and the significance assessment with p-value and adjusted p-value. NEASE score re-weights the pathways according to the hub bias. For more details, check the [NEASE publication] (https://doi.org/10.1186/s13059-021-02538-1).
227+
Type in the name of the ontology of interest and click the "Run enrichment" button. The resulting table will show the list of pathways, the list of genes that lost/impaired interactions with these pathways due to alternative splicing, and the significance assessment with p-value and adjusted p-value. NEASE score re-weights the pathways according to the hub bias. For more details, check the [NEASE publication](https://doi.org/10.1186/s13059-021-02538-1).
228228

229229
To investigate the enriched pathways in detail, use Pathway analysis. Type in the pathway ID from NEASE edge enrichment analysis, e.g., "path:mmu04010". The resulting table contains the information about each gene with list/impaired interactions with this pathway due to alternative splicing: whether it belongs to the pathway, how many interactions were lost/impaired, and the p-value.
230230

231-
Finally, "Visualize pathways" option provides the visualization of teh resulting network with lost/impaired interactions. Be aware, the visualization might take up to several minutes.
231+
Finally, "Visualize pathways" option provides the visualization of the resulting network with lost/impaired interactions. Be aware, the visualization might take up to several minutes.
232232

233233
# Hosting your own instance
234234

docs/index.html

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
<html lang="en">
33
<head>
44
<meta charset="UTF-8">
5-
<title>Document</title>
5+
<title>DIGGER 2.0 Docs</title>
66
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1" />
77
<meta name="description" content="Description">
88
<meta name="viewport" content="width=device-width, initial-scale=1.0, minimum-scale=1.0">

0 commit comments

Comments
 (0)