zen quaker

A self quanitified zen quaker statistical programmer stumbles through a blog

Tag: python

Mood O

Okay, so I’ve been recording data on my moods. I think I’ve gone over the current methodology already, but allow me to reiterate. Skip to the the graph if you’ve seen it or don’t care. I have set up my Droid phone to ping me every hour using the Calendar app. I think that ties in to Google Calender, so I guess I’m shoving some screwy stuff into the data hoover that is Google, but I’m too small to affect them.

Read the rest of this entry »

Study III

One of the thing you are supposed to study for Chess is visualization. That’s what they call being able to see what the board will look like three moves into the future. Like many things in Chess you can build visualization up from small pieces. First you learn to be able to tell what color a square is without looking at it, and then which diagonals it is on, and so on. Being a programmer, I wrote a computer program to generate random visualization questions for me to answer. In a fit of originality I decided to call it Visualizer. I’ve set up a page for it here on WordPress, and one at the pygame site (since I wrote it in Python and pygame).

Adjutant II

Okay, I have converted the Python 2.7 code to Python 3.2 code. It wasn’t anywhere near as bad as I expected. Most of the problems were print statements becoming print functions, and some object which could be treated as lists in 2.7 but have to be explicitly converted in 3.2. Next step is to update the documentation. That is going to take a while for sure, since I want to add some graphical representations of objects and process flows, but that is a large part of why I downloaded Dia last month.

To share the current counts that I get when I run the test suite on Adjutant:

  • 2,514 lines of code.
  • 1,390 lines of comments.
  • 60 classes.
  • 208 methods.
  • 35 unbound functions.

Adjutant I

For a long time I’ve been working on a project to define Chess variants in XML. I did two rounds of coming up with a schema for Chess variants, and then decided that I really needed an application that used the XML to inform the schema design process. That led to me spending much of the past year working on Adjutant. Read the rest of this entry »