Blog Posts

  • Double Edged Rejoinder
    July 22, 2016

    A cool article on the philosophy of simulation science is up on JASSS. I like the idea and the execution but I think the fear of “equifinality” is overstated.

  • My Dissertation Defense
    June 07, 2015

    I completed my dissertation defense on Friday. It went reasonably well. I was pleased I could embed the Dart version of the model straight into my slides. I am amazed that RMarkdown + ioslides + dart work so well together. The only thing I couldn’t do was to have the model learn on its own when a slide was called so that I always need to press “reset” before “start” when a slide containing the model shows up. Minor inconvenience but still.

  • Agent based fishing
    February 04, 2015

    Conservation notice: this is a simple model I cobbled up in about a week both as a spike to test the capabilities of google maps APIs and as a demo for a post-doc job. The code is open-source on MIT license. It was programmed in pure dart.

  • Zero-Knowledge Traders, Redrawn
    January 20, 2015
  • Big Ideas in Macroeconomics -- A book review
    September 03, 2014

    A very good book. To read. Detailed, learned and thorough. Also deeply flawed.

  • Common Control Models in Differential Equation Format
    June 28, 2014

    If you are like me and spent months looking for these, you are welcome. For everyone else, these are just common approximative models used in control theory to fit processes to. Unfortunately they are always expressed as Laplace transforms. S-space isn’t very useful to me, I really need processes in time. All credit to this stackexchange answer. An explanation of its math is here. Thank you, kind strangers.

  • A Model of Lancasterian Competition
    April 17, 2014

    I want to try and apply PID controllers to monopolistic competition. Partially because monopolistic competition is more interesting, but partially because I don’t like the way some ABMs model it.

  • Bad Unit Tests
    March 30, 2014

    Unit testing is awesome. Writing your assumptions in code so that they’ll always hold no matter what else changes, what’s there not to like? But the real question is, are extremely poorly written unit tests also awesome?