Now, the point of this post: thanks to the changes to Geneagrapher mentioned above, I have set up a web-based “Geneacache“. It is a very early preview, so the API may change in the near future. A lot of other changes are needed, too, and it is possible I will move the page to a different address. Here’s the idea: your software can use the Geneacache to retrieve records from the Mathematics Genealogy Project (MGP), saving you the trouble of scraping the MGP pages or having to use Geneagrapher to do it for you. The response contains the record’s information in JSON. For example, for Gauß you currently get:

{
    "advisors": [
        18230
    ],
    "descendants": [
        151876,
        55175,
        29642,
        18603,
        19953,
        29458,
        62547,
        18232,
        18233
    ],
    "institution": "Universität Helmstedt",
    "name": "Carl Friedrich Gauß",
    "year": 1799
}

Behind the scenes, the Geneacache either returns what it has locally or fetches it from the MGP, stores it locally, and then returns the record to you.

This is not used for anything at the moment, but I intend to start exposing Geneagrapher through a web page again (history lesson: the first version of Geneagrapher, from when I was in graduate school — was a web service) at some point in the future. The Geneagrapher client is nice and all, but I imagine most users are not interested in installing it locally to use it.

I am also planning to get in touch with the MGP folks about this and related topics.

Conveniently, there was an orienteering event in Seattle yesterday, and I went (results here). This was my first event, so I ran the beginner course. I liked it and plan to continue attending events. I think the sport will be really interesting on more challenging courses because of the decision making that will go into navigating to the controls.

Back to the book: it would benefit from updating and releasing a new edition. The basic information is still accurate, but parts of the book have become outdated, based on what I saw and learned from talking to an experienced club member.

I kind of wonder about cleaning the thing, but bees are pretty obsessive about hygiene, so maybe there is no issue. Let me know how it goes.

This beehive is part of the company’s Microbial Home design project.

He said it a few more times, clearly referring to the apple, although it did become “bapple” a couple times.

Amazing.

He has said other words (including “owl” when looking at one of his sippy cups), but this seemed much more interactive.

My code needs to compute the convex hull in order to start the Delaunay triangulation. Since that is sort of interesting in itself (and may be needed on its own in the future), I pulled out the convex hull generation into its own class. The computation proceeds using Graham scan. Here’s an example (created with ‘conhull -s 50 -n 20′):

You can see that’s correct, but visually, it’s not too interesting. For fun, I added the ability to generate nested convex hulls. The next image was created with ‘conhull -s 50 -n 500 –num-hulls all –no-plot-points’:

With more points (‘conhull -s 50 -n 1000 –num-hulls all –no-plot-points’):

The package is here.

The code is still a mess, and will be updated, but you can find it here. You need Python with matplotlib to run the code.

The King County Library System offers e-book check out for the Kindle.

So am I about to set up a hive or two of my own? I don’t think the HOA in the condo complex where we rent would be happy with me housing hundreds of bees thirty feet from the community pool. Maybe later. Still, attending “beekeeping school” might be interesting to learn something new.

I had to reorganized my Subversion repository to make it work, and my tags were trashed in the end due to conflicts in my tags and the way Git tags things. That’s not a huge deal, though, because I can recreate everything, if needed. Anyhow, the big take-home message here is that the Geneagrapher repository is now open to the public.

One other action that I took, after moving the repository, was to nuke the trunk (er, master). I had made new feature progress in the trunk years ago, but stopped. I decided it would just be easier to continue by reverting the trunk to the latest maintenance branch.