5-neuron-model of neocortex for producing realistic extracellular AP shapes (Van Dijck et al. 2012)

 Download zip file 
Help downloading and running models
This is a 5-neuron model of neocortex, containing one tufted layer-5 pyramidal cell, two non-tufted pyramidal cells, and two inhibitory interneurons. It was used to reproduce extracellular spike shapes in a study comparing algorithms for spike sorting and electrode selection. The neuron models are adapted from Dyhrfjeld-Johnsen et al. (2005).
1 . Van Dijck G, Seidl K, Paul O, Ruther P, Van Hulle MM, Maex R (2012) Enhancing the yield of high-density electrode arrays through automated electrode selection. Int J Neural Syst 22:1-19 [PubMed]
Citations  Citation Browser
Model Information (Click on a link to find other models with that property)
Model Type: Extracellular; Neuron or other electrically excitable cell; Realistic Network;
Brain Region(s)/Organism:
Cell Type(s): Neocortex U1 L5B pyramidal pyramidal tract GLU cell; Neocortex U1 L2/6 pyramidal intratelencephalic GLU cell;
Gap Junctions:
Simulation Environment: GENESIS;
Model Concept(s):
Implementer(s): Maex, Reinoud [reinoud at bbf.uia.ac.be];
Search NeuronDB for information about:  Neocortex U1 L5B pyramidal pyramidal tract GLU cell; Neocortex U1 L2/6 pyramidal intratelencephalic GLU cell;
This dir deals with graphical or file output.

L5P_history.g can be used to save spike times (of neurons
or fibres) to a file.

L5P_ascout.g is commonly used to write time series (of
membrane potential, electrode LFP, etc) to a file.

L5P_view.g will open a window picturing all the neurons' 
compartments, colour-coded by membrane potential and 
updated every 50 ms.

Likewise, L5P_graphsolve.g will open a window with online
graphs of the time-evolution of the membrane potential of
selected compartments. Note that L5P_graphsolve.g replaces
L5P_graph.g because of an unsolved problem with Genesis or
my code. The original code of L5P_graph.g intended to establish 
the messages from compartments to graphs before setting up 
the hinessolver. Unfortunately this resulted in a bus error. 
So L5P_graphsolve.g now makes these messages directly from 
the hinesolver element to the graphs, after creation of the 
hinessolver element.