nowadays, docs with rarely interpretation is difficult to understand the algorithm,
Such as bayes rule sets and other Underdogs have little references.
If can provide a common introduce in interface level may be good for programmers
who have little information of algorithm to start

despite the documentation suggesting otherwise

$ ./picolrn > howto.txt

does nothing....

there are no details of the format that the training data must be in.

Create a new folder print-nodes-top-view-binary-tree in Binary Tree .
Use implemented BinaryTree.
Problem is statement here: [print-nodes-top-view-binary-tree](https://www.gee

A persistent source of confusion in msprime has been what the migration in rates in msprime actually mean.

#978 updated the simulation model section with some clarifications from @petrelharp, and harmonised the usage of source/dest in the MigrationRateChange and MassMigration events. We should review this, and try to clarify as much as possible - perhaps adding a section in the tutorial to real

Other than what we've already discussed, I'd like to work on some things listed below. I tend to enjoy micromanaging things, so please let me know if I'm stepping on your toes or if you desire something different. In the end I just want to help out.

Add Labels

I discovered zenhub a long time ago, but I recently started using it more. Especially for bigger projects. I've also started u

I noticed that I forgot to update the API docs for a refactor that moved mathy.mathy to mathy.api.

Currently, you have to run:

cd libraries/website
sh tools/docs.sh

And it generates all the API doc files. This means it's too slow to run all the time. It should be updated to run as part of lint-staged and support passing individual files on the command-line, similar to th

Currently the doc comments for everything in id_tree::behaviors refer to VecTree functions. These should be updated such that they refer to Tree (the Trait) functions instead.