I’ll be at MICCAI for the full week, starting Saturday. I’m presenting poster P7-159-M (Monday at 3pm, Section P7: Segmentation) on some fun segmentation work. Drop me a line if you’d like to talk sometime or stop by my poster on Monday.
If you’re studying methods for image analysis relating to brain development, there will be a workshop at MICCAI 2011 called, appropriately, Image Analysis of Human Brain Development.
I probably will not be submitting a paper, as I should have a submission on segmentation in older kids at the main conference, but I will be reviewing papers for and attending the workshop.
This will be a great meeting, so please sign up – paper deadline is June 3 — see the site.
We’ve spent a good deal of time writing (often-complicated) multi-threaded code in order to take advantage of our multi-core machines. Our lab has two central compute servers, one with four quad-core processors, and another with six, and we have a lot of data to process.
The question is: if we have 100 cases to analyze on a 24-core machine, should we spend time re-writing algorithms to attempt to achieve a 24x speed-up on each case, or should we simply run 24 cases simultaneously? In many situations, the answer is the latter, especially since it incurs zero extra development time. To that end, you may find the following Bash script useful.
For revision control, I’ve been using git for about a year, with mostly (see below) good success. I haven’t compared it to other distributed revision control systems, but have cut my teeth on the original SCCS, followed by RCS, CVS, and Subversion, once the FSFS backend came about. Git is an entirely new beast.
So I’m building PySide on the Mac as part of a new medical imaging endeavor. For years I’ve wanted a usable mashup of ITK, VTK, Python, and Qt as a medical imaging toolkit. Add numpy and scipy on the Python side, and you have a very powerful combination of software. But if the interface to Python is achieved through automatically generated bindings for ITK, VTK, and Qt, you have a really brittle build. I keep finding such projects that seem to thrive for a year or so and then die as it becomes impossible to support people’s use of the bindings with changing toolkits and with Python itself evolving.
So I’m building PySide on the Mac as part of a new imaging endeavor and after struggling with tons of:
type ‘…’ is specified in typesystem, but not defined. This could potentially lead to compilation errors.
errors, I realized that ‘/usr/include’ was being prepended to every path passed to the generator and, with the help of Google (why I’m writing this for *you*), I realized that there’s a workaround:
This was set for a Qt installed from binary as Mac Frameworks and the variable should pop up in CMake for you to set manually.
Hope that helps someone!
The solution for:
Credit card processing is temporarily unavailable. You may continue to browse the store. Please try to make your purchase later.
from the Apple Store turns out to be:
Continue reading
If you’re using the “Exchange” method of synchronizing calendars and notice that not all of your multiple calendars from your Google Apps for Domains setup are being sync’d down, follow these instructions:
http://www.google.com/support/mobile/bin/answer.py?answer=139206
Basically, for those in the know, it’s the usual m.google.com/sync stuff, but there’s a link in the fine print at the bottom for Google Apps for Domains.
Also note: if someone directs you to a url with “iphoneselect” in it, that’s only when accessing calendars in a non-push way through the iphone’s “Gmail” setup. Â If you use the Exchange setup for getting push calendars, follow the url I posted above.
Whipped this up this morning.
The Error -128 exception is from one of DT’s own scripts, so I’m not sure what that error is, precisely.
Feel free to comment as I’m a novice at AppleScript.