Skip to content

Commit 7b8dac3

Browse files
committed
Figure size update
1 parent 4943e74 commit 7b8dac3

2 files changed

Lines changed: 7 additions & 7 deletions

File tree

README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
---
22
author: "Nicola F. Müller,Tim Vaughan"
3-
beastversion: 2.4.2
4-
tracerversion: 1.6.0
5-
figtreeversion: 1.4.2
3+
beastversion: 2.7.x
4+
tracerversion: 1.7.3
5+
figtreeversion: 1.4.x
66
level: Professional
77
subtitle: Population structure using MultiTypeTree
88
title: Structured coalescent
@@ -91,7 +91,7 @@ The packages MultiTypeTree is not implemented in the core of BEAST, but has to b
9191
9292
<figure>
9393
<a id="fig:install_mtt"></a>
94-
<img style="width:50.0%;" src="figures/install_mtt.png" alt="">
94+
<img src="figures/install_mtt.png" alt="">
9595
<figcaption>Figure 1: Install MultiTypeTree.</figcaption>
9696
</figure>
9797
<br>
@@ -205,7 +205,7 @@ Next, we can have a look at the estimates of the effective population sizes (Fig
205205

206206
<figure>
207207
<a id="fig:estimated_peff"></a>
208-
<img style="width:60.0%;" src="figures/effectivePsize_tracer.png" alt="">
208+
<img src="figures/effectivePsize_tracer.png" alt="">
209209
<figcaption>Figure 6: Estimated effective population sizes.</figcaption>
210210
</figure>
211211
<br>
@@ -216,7 +216,7 @@ Hong Kong ({% eqinline \sim %}7 Mio Inhabitants) is inferred to have the larger
216216

217217
<figure>
218218
<a id="fig:etimated_mig"></a>
219-
<img style="width:60.0%;" src="figures/migrationrates_tracer.png" alt="">
219+
<img src="figures/migrationrates_tracer.png" alt="">
220220
<figcaption>Figure 7: Estimated migration rates.</figcaption>
221221
</figure>
222222
<br>
@@ -240,7 +240,7 @@ MultiTypeTree logs 3 different tree files:
240240

241241
<figure>
242242
<a id="fig:single_child"></a>
243-
<img src="figures/single_child.pdf" alt="">
243+
<img src="figures/single_child.png" alt="">
244244
<figcaption>Figure 8: An example of a tree where the migration events are logged as single child nodes (left) and of the same tree where only the location of a coalescent event is logged (right).</figcaption>
245245
</figure>
246246
<br>

figures/single_child.png

35.2 KB
Loading

0 commit comments

Comments
 (0)