Hacking

[da]

This week started off slowly at work, but wow, it picked up nicely. I've been working on the most interesting project I've had in many months: a c++ program to process data from a large IR emitter and sensor array, which reports 3-d positions (within 1/10 a millimeter) for a set of markers within a 3m x 3m x 4m cube space.

I was asked to learn how this machine talks with the computer over the serial line, and figure out if it can report raw 3-d position data for each of 4 sensors, instead of reporting the aggregate position and orientation of the sensors. There's a sample C++ project which fully demoed the program's capabilities, which I've been hacking on. There's no tricky math- and their code is quite well documented. And a friendly support engineer helped me determine that I had the right approach to get the data using their API. I also found a bug in their code, which we're fortunately able to work around.

So I've gone from zero to almost-but-not-quite-there in the last 48 hours. This involved: learning Visual Studio, learning the API, and figuring out enough of this C++ program to be useful. This is what I wish I'd been working on for the last year. I'll be done with this project on Tuesday... (at least I hope I will, because I'm leaving with melted_snowball for Florence on Wednesday, not back until the following Thursday!)

Visual Studio is the best Microsoft product I've ever worked with; I got up to speed quite quickly and the only thing holding me back was, um, a bit of fuzziness on C++ datatypes. Also, I wish I could get the debugger to use the breakpoints I set; I'm having to do more debugging-via-print-statements than I'd prefer.

Comments

[earthling177.livejournal.com]

Under OSX you are supposed to be using XCode for anything that you want support from the OS and easy transition to the billion things they are planning to do and will of course not tell us. Just take a look on the web and find out the big examples of people who shot themselves in their feet for staying with other products, including Microsoft (which was almost the last company to release a product native on the Intel Macs) and Adobe, which was basically the last one and hasn't finished yet. If you don't like something like the editor, I think you can even tell XCode which external editor you want (emacs, vi etc). For contrast, Mathematica, one of the largest apps/systems out there, compiled almost with no changes in no time at all and was the first non-Apple app to be ready for the Intel Macs. Steve didn't even let them know what was gonna happen, he just asked Wolfram "can you send me one of your engineers with a hard drive containing your code?" and as he said "boom!, it was ready to deliver". It may also have been the *only* app that ever happened to, I heard people complaining about the contortions they had to do to be able to compile as Universal App, which only highlights my profs saying "don't go to assembly/tricks just to get 1% faster, 'cuz you'll spend a huge amount of time porting it to the next OS/architecture...", which seems true enough but no one in the computer industry seems to want to hear.

As for VMware Fusion vs. Parallels, the dust is not settled yet: each one is better than the other depending on what you want and what you're doing. Latest rumors I've heard is that if you want to deal with a lot of peripherals, particularly USB, you might be in better luck with Parallels, if you wanted to tell the VM how many CPUs you want to use and how, you might like VMware better and so on and so forth. "Stable" is one of those funny words when it comes to VM, some people say that while VMware tends to process stuff in the VM faster, once you stop VMware it continues to take CPU resources/time because some of the processes don't sleep/go away like Parallels. Reports of which one is better if you sleep the physical machine without stopping the VM or even just which one suspends the VM and lets you quit the program and resume later are conflicting at best.

But here's the good news: as far as I know, *both* let you use the program for free for a few days so you can check. Just remember to ask the uninstaller to remove the systems completely before installing the other one, 'cuz they sink their teeth deep into the OS and the machine to get the VMs to work and you don't want both running fragments of code at once, bad bad plan. Good luck!