Some of our lab’s “competitors” have a really nice article covering many many of the existing cardiac ionic models up on Scholarpedia, with illustrations and even java applets and movies.

The article is entitled Models of cardiac cell [sic].

Kudos to Drs. Fenton and Cherry for the excellent article, it looks like it was quite a lot of work to put together!

We had a family emergency last week, so this post is delayed. I hope you all had a great weekend.

This is from a post by Dr.Wes. A friend of one of the device nurses got the tattoo to go with her ICD. “No jumpstart needed” per the shirts that inspired the design.

Today the latest CSM demo video went live on the CardioSolv site. It showcases the use of our mapping interface, which makes it easy to create useful maps of activity in simulation models.

It’s currently non-trivial to show movies in papers, so instead we do time-lapse type things called activation maps. These show the activation times as a series of lines (‘isochrones’ or ‘isochronal lines’, meaning that all of the points on the line are activated at the same time) or bands of color representing the same thing. We can extend this to also show repolarization times, or non-sequential data such as action potential duration maps and dominant frequency maps.

Here’s a sample activation map of a wave moving across a sheet from right to left:

Activation Map Right to Left

And here’s one of a spiral (this with 20ms isochrones):

Activation Map of a Spiral Wave

To give you an idea of the correspondence between an activation map and a movie of the simulation, here’s a movie of that spiral:
Spiral Wave

There’s a lot more to this — for instance, deciding when a cell has activated or repolarized, and back-end processing. We use a program I wrote that does the analysis in parallel, making it rather quick to analyze even huge datasets, provided you have the computing power.

If you have any questions about the process I’d be happy to answer them here or on the CardioSolv post.

Today I’m really excited to finally show you something that’s been in the works, both in implementation and in the planning stages, for a long time. The CardioSolv Simulation Manager.

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.

(more…)

The whole article is here.

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.