Excitation-contraction coupling/mitochondrial energetics (ECME) model (Cortassa et al. 2006)

 Download zip file 
Help downloading and running models
"An intricate network of reactions is involved in matching energy supply with demand in the heart. This complexity arises because energy production both modulates and is modulated by the electrophysiological and contractile activity of the cardiac myocyte. Here, we present an integrated mathematical model of the cardiac cell that links excitation-contraction coupling with mitochondrial energy generation. The dynamics of the model are described by a system of 50 ordinary differential equations. The formulation explicitly incorporates cytoplasmic ATP-consuming processes associated with force generation and ion transport, as well as the creatine kinase reaction. Changes in the electrical and contractile activity of the myocyte are coupled to mitochondrial energetics through the ATP, Ca21, and Na1 concentrations in the myoplasmic and mitochondrial matrix compartments. ..."
1 . Cortassa S, Aon MA, Marbán E, Winslow RL, O'Rourke B (2003) An integrated model of cardiac mitochondrial energy metabolism and calcium dynamics. Biophys J 84:2734-55 [PubMed]
Model Information (Click on a link to find other models with that property)
Model Type: Neuron or other electrically excitable cell; Electrogenic pump;
Brain Region(s)/Organism:
Cell Type(s): Heart cell;
Channel(s): I L high threshold; I Sodium; I Potassium; Na/Ca exchanger; I_SERCA;
Gap Junctions:
Simulation Environment: C or C++ program;
Model Concept(s): Activity Patterns; Temporal Pattern Generation; Signaling pathways; Calcium dynamics;
Search NeuronDB for information about:  I L high threshold; I Sodium; I Potassium; Na/Ca exchanger; I_SERCA;
 *                                                                 *
 * File          : fcmixpar.h                                      *
 * Programmers   : Alan C. Hindmarsh @ LLNL                        *
 * Version of    : 19 August 2002                                  *
 * Copyright (c) 2002, The Regents of the University of California *
 * Produced at the Lawrence Livermore National Laboratory          *
 * All rights reserved                                             *
 * For details, see sundials/shared/LICENSE                        *
 * This file contains machine-dependent definitions of parameters  *
 * that characterize the treatment of externals by the Fortran     *
 * compiler, for use with Fortran/C interface routines.            *
 *                                                                 *
 * Definitions:                                                    *
 *                                                                 *
 *   CRAY          If the system is a Cray, set CRAY to 1, else    *
 *                 set it to 0. This is needed since the Cray has  *
 *                 non-standard include files, and the loader      *
 *                 expects names all upper case.                   *
 *                                                                 *
 *   UNDERSCORE    Set this to 1 if the system's Fortran77 expects *
 *                 C functions to have an underscore at the end of *
 *                 the name, and also the Fortran77 appends an     *
 *                 underscore on all Fortran subroutine names.     *
 *                 Otherwise set it to 0. If CRAY = 1, UNDERSCORE  *
 *                 is ignored.                                     *
 *  Some examples:                                                 *
 *         1 for Sun, DEC Alpha, SGI, IBM with -q extname, Meiko   *
 *         0 for HP, IBM default                                   *
 *                                                                 *
 * Declarations:                                                   *
 *                                                                 *
 *   F2C_machEnv  A global variable used to communicate the        *
 *                machine environment structure among the various  *
 *                routine in a Fortran - C interface. It is        *
 *                declared extern here and must defined in the     *
 *                Fortran - C interface implementation file of the *
 *                NVECTOR module.                                  *
 *                                                                 *

#ifdef __cplusplus     /* wrapper to enable C++ usage */
extern "C" {

#ifndef _fcmixpar_h
#define _fcmixpar_h
#define CRAY        0
#define UNDERSCORE  1

#include "nvector.h"

extern M_Env F2C_machEnv;


#ifdef __cplusplus

Loading data, please wait...