After a little spelunking of old mailing list entries (which I am trying to spare you with this post, dear reader), I discovered that the Ubuntu folks flipped around how the “nodelayacct” kernel boot parameter works for various arcane reasons. Here’s the short version of how to enable it.

1) Edit /etc/default/grub, adding “delayacct” as an option to the GRUB_CMDLINE_LINUX_DEFAULT entry. If you hadn’t already modified that line, it would go from


GRUB_CMDLINE_LINUX_DEFAULT=""


to


GRUB_CMDLINE_LINUX_DEFAULT="delayacct"


2) Run “sudo update-grub”
3) Reboot, and you should be good to go

Assuming bluetooth is already working, and you’ve paired your headsets, do the following things:

1. Download the x-lite 4.0 software for Linux
2. Run the softphone with ‘padsp xtensoftphone’ (this will wrap it’s audio i/o with pulseaudio
3. Change the audio settings in the x-lite phone to use the PulseAudio virtual device
4. Make sounds in the x-lite phone, call an 800 number or something, then while sound is being made run ‘pavucontrol’
5. In the output and recording tabs, find the padsp streams and select the bluetooth headset inputs/outputs.

Caveats: I haven’t tested whether this is remembered between logins, and I think if you are using padsp to wrap other applications this will send them all through bluetooth.

Let me know if this helps you or if you get stuck!

Thunderbird to the rescue!

I use Mozilla Thunderbird for my email for mostly the same reason I still use FireFox to browse the web: there’s a plugin for almost anything I want to do. Also, in Linux it’s easy to use a CUPS-PDF virtual printer to print to PDF. Combining this with the attachment extractor Thunderbird plugin allows me to dump all of the attachments and emails to files on my hard drive in just a few clicks.

I have ‘Invoices’ and ‘Receipts’ email folders that need to be dumped, so I just go into each folder, select all messages, print them using CUPS-PDF, and then right-click and tell AttachmentExtractor to dump any attachments as well. Done, in about 5 minutes. Trying to do this manually would take countless hours, meaning in reality that I would just never do it, and if my taxes were audited, it would be a total nightmare.

Hopefully if you have this same problem google + this post will help you out. Enjoy!

Following some instructions here and using the patch provided here (from this thread), I was finally able to get it working.

Here’s the resulting package.

python-qwt5-qt4_510dfsg-1ubuntu1_amd64

Steps to build:

Create some directory where you want to build this. Change to that directory. Then…

sudo apt-get build-dep python-qwt5-qt4

(installs dependencies for building)


sudo apt-get source python-qwt5-qt4


This should download the package source. Download the patch from the comment I linked to above, then change into the directory and patch the files. You may have to change the directory ownership so that your user can write to it (sudo chown -R yourusername .)


patch -p0 < ~/Inbox/pyqwt-final.diff

(of course your patch may be located in a different location)

Per the GPLv2, here's the patched source I used to build the .deb file (note -- I think you can just download this instead of patching it yourself).

brocks_patched_pywqt5_src.tar.bz2

Once it's patched, rebuild it with:

sudo dpkg-buildpackage -rfakeroot -uc -b


Go get a cup of coffee or whatever, it's a fairly involved build. When it's done, in the directory above you should find your .deb packages. A simple:

sudo dpkg -i python-qwt5-qt4_5.1.0.dfsg-2_amd64.deb

(replace the filename with whatever yours is, of course)

will install it for you. Hope this is helpful for someone, as I wasted a few hours trying to install this all from source and so on.

Running cardiac electrophysiology (and mechanics) simulations has traditionally been really complicated. It involved learning a bunch of UNIX command-line tricks, dealing with queuing systems and their associated script files, and so on. Furthermore, there are many, many options in a sophisticated cardiac simulator, and the novice user (and even the expert) can easily get lost in all of the choices.

We’ve taken years of experience setting up, running, and analyzing simulations to build a really cool (excuse my excitement) web interface that handles all of the dirty work, and guides the user through the important choices when running simulations.

The video below is my first demo. In it, I demonstrate how to create a plane wave moving across a sheet of tissue, then create a spiral wave, all from the web interface.

Note: If you’d like to view the high-definition version, I suggest you either click through to YouTube or expand the video to full-screen mode.

The post about it on the company blog is here, with contact info and all of that.

The HPC service lets the small, five-employee company do the heavy lifting that would otherwise cost a fortune. “With what we could purchase out of pocket, we’d have to bootstrap very slowly, or look for VC [venture capital] funding,” said Dr. Brock Tice, the vice president of operations at Cardiosolv, a privately funded medical research firm. Instead, Tice uses a new HPC on-demand service from Penguin Computing called Penguin on Demand.

…

While Cardiosolv has its own small cluster on the premises for calculations, Tice estimates the resources he rents from Penguin would probably cost $500,000 to build, and other cloud options weren’t suitable.

“We can’t use [Amazon's Elastic Compute Cloud] EC2, since there’s a lot of latency between the nodes,” he said.

Brock Tice is one of those scientists. As vp of operations at the Baltimore, Maryland-based CardioSolv, he works to model, yes, the heart – simulating its mechanical and electrical activity. And though he can run some simulations on Amazon’s cloud – or on individual local machines – more complex models require HPC. “We’re [sic] tried on Amazon and it just doesn’t scale,” he tells The Reg. “We can run on single EC2 instances, but if we need to scale up to a dog or human heart, it’s just impossible.

“The connections between Amazon’s machines are Gigabit Ethernet and they’re shared. If you fire up 10 machines and you want to run them like a cluster, some might be in the same rack, and others might be halfway across the data center, five or six switches away.”

You can find the full story here.

I fixed an outstanding screen rotation bug, made it so that vibrate mode applies to both the bell and the ringtone, and upgraded to the Android 1.5 (Cupcake) API.

I’m also sick of missing out on current events, like the Conficker worm, which somehow made the top story on Google News last night. Top story! I was feeling really left out. Once I have windows installed on my Mac Pro, though, I should be able to join the Conficker party in no time.

Sure, it’ll be difficult to do my work, since it relies largely on UNIX-based software, but hey, that’s what Cygwin is for, right? And PuTTY. Got any recommended software for me? It’s been a while since I was a full-time Windows user. A Quicksilver replacement would be particularly welcome. And send me a copy of Conficker if you have it — thanks.

However, I’m finally getting back into the swing of things with work, around the house, etc. I’ve started roasting my own coffee, which is great, and Amanda got me an espresso machine that should be arriving within hours in which to use my freshly-roasted beans.

The thing that has been using up the greatest amount of my “free” time (whatever that means these days) has been hacking on an improved email client for the new “Google Phone”, the G1. The included email client was utter crap, to put it kindly, not even as sophisticated as the client on my little Razr2 v8 flip phone. However, someone forked the open-source email client that came with the device into a project called K-9. The name is derived from that of an old UNIX-y email client called mutt, the idea being that K-9 (canine) is a sort of androidy name for a dog, I guess.

Anyway, the client has been rapidly improving. I haven’t done much — just a few bug fixes here and there, and possibly the addition of some bugs (hope not) — but several people are working on it. It’s already getting rave reviews in the Android market, particularly since people have only the crappy built-in client an an alternative. Heh. I don’t know Java, really, but that hasn’t been stopping me. It’s not that different from Python and C++. Anyway, if you have a G1, check it out. We’re improving performance, fixing bugs, and adding features all of the time.