Architecture is really a tough call now. I need to pick an overall design of Aperios Objects (modules) and keep it stable until the end of the year. I’m probably going to have one for vision (plus Python hooks), motion, and communication. And how to link various bits of code for each module? Common header files? Namespaces? Heck–I could do like UPenn and just have one Aperios object for everything.
.flickr-photo { border: solid 2px #000000; }
.flickr-yourcomment { }
.flickr-frame { text-align: left; padding: 3px; }
.flickr-caption { font-size: 0.8em; margin-top: 0px; }
After many frustrating days and numerous debugging styles, I’ve finally gotten Python to run on Aperios!
I’ve often read that good Programmers are not amazingly proficient coders but they instead excel at debugging their own code. Boy–do I need to get better at this. The technique that finally got things going was taking the entirety of the 2005 rUNSWift code and widdling it down to the Python layer. This allowed me to step incrementally while making sure things stay working. Long process–but I learned heaps about Aperios, Python, and C++ in general.
Onward!
The Age of Python is Nigh: weeded down UNSW’s code to the bare Python essentials. Both the python code and the C++ hooks now compile. They crash the dog on boot-up, but they compile!
Now into Chapter 5 in Dive into Python while simultaneously playing around with Python in the OPEN-R environment. This is tougher to crack than I thought.
Immersed in Dive Into Python — currently on Section 3.2: Introducing Lists!
OK–
I’ve just completely redone the way the team gets its code to the memory sticks. It’s heavily influenced from the open-source rUNSWift code, who know OPEN-R and Makefiles way better than I. The code is insanely modular which will allow our team to easily port among various platforms, code, and computer configurations.
We now use rsync to more efficiently copy files over, and use Makefiles instead of shell scripts. Moreover, I’ve added a lot more compiling flags to make our analysis of bad code easier.
This takes us a significant step closer to python integration.
