Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add in mass migration event #22

Open
GertjanBisschop opened this issue Jan 4, 2024 · 1 comment
Open

add in mass migration event #22

GertjanBisschop opened this issue Jan 4, 2024 · 1 comment

Comments

@GertjanBisschop
Copy link
Member

As pointed out by @A-J-F-Mackintosh, the currently available Event classes could be made more flexible by adding in a discrete MassMigrationEvent that moves all lineages from one population to another at a discrete point in time.

@GertjanBisschop
Copy link
Member Author

General pattern of _single_step(): as you said in #20 @A-J-F-Mackintosh, this method returns the index of the event, and the new configuration of lineages after a single step. The count essentially tallies the number of ways that the same new configuration can be achieved by combining different lineages. For example a pairwise coalescence event for ['a', 'a', 'a'] will always result in ['aa', 'a']. However, there are 3 different ways of achieving this result.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant