A new model for evolution in a spatial continuum.

Barton, Nick H.; Etheridge, Alison M.; Véber, Amandine

Electronic Journal of Probability [electronic only] (2010)

  • Volume: 15, page 162-216
  • ISSN: 1083-589X

How to cite

top

Barton, Nick H., Etheridge, Alison M., and Véber, Amandine. "A new model for evolution in a spatial continuum.." Electronic Journal of Probability [electronic only] 15 (2010): 162-216. <http://eudml.org/doc/227391>.

@article{Barton2010,
author = {Barton, Nick H., Etheridge, Alison M., Véber, Amandine},
journal = {Electronic Journal of Probability [electronic only]},
keywords = {genealogy; evolution; multiple merger coalescent; spatial continuum; spatial lambda-coalescent; generalised fleming-viot process},
language = {eng},
pages = {162-216},
publisher = {University of Washington, Department of Mathematics, Seattle, WA; Duke University, Department of Mathematics, Durham},
title = {A new model for evolution in a spatial continuum.},
url = {http://eudml.org/doc/227391},
volume = {15},
year = {2010},
}

TY - JOUR
AU - Barton, Nick H.
AU - Etheridge, Alison M.
AU - Véber, Amandine
TI - A new model for evolution in a spatial continuum.
JO - Electronic Journal of Probability [electronic only]
PY - 2010
PB - University of Washington, Department of Mathematics, Seattle, WA; Duke University, Department of Mathematics, Durham
VL - 15
SP - 162
EP - 216
LA - eng
KW - genealogy; evolution; multiple merger coalescent; spatial continuum; spatial lambda-coalescent; generalised fleming-viot process
UR - http://eudml.org/doc/227391
ER -

NotesEmbed ?

top

You must be logged in to post comments.

To embed these notes on your page include the following JavaScript code on your page where you want the notes to appear.

Only the controls for the widget will be shown in your chosen language. Notes will be shown in their authored language.

Tells the widget how many notes to show per page. You can cycle through additional notes using the next and previous controls.

    
                

                
Note: Best practice suggests putting the JavaScript code just before the closing </body> tag.