Spike burst-pause dynamics of Purkinje cells regulate sensorimotor adaptation (Luque et al 2019)

 Download zip file   Auto-launch 
Help downloading and running models
Accession:256140
"Cerebellar Purkinje cells mediate accurate eye movement coordination. However, it remains unclear how oculomotor adaptation depends on the interplay between the characteristic Purkinje cell response patterns, namely tonic, bursting, and spike pauses. Here, a spiking cerebellar model assesses the role of Purkinje cell firing patterns in vestibular ocular reflex (VOR) adaptation. The model captures the cerebellar microcircuit properties and it incorporates spike-based synaptic plasticity at multiple cerebellar sites. ..."
Reference:
1 . Luque NR, Naveros F, Carrillo RR, Ros E, Arleo A (2019) Spike burst-pause dynamics of Purkinje cells regulate sensorimotor adaptation. PLoS Comput Biol 15:e1006298 [PubMed]
Citations  Citation Browser
Model Information (Click on a link to find other models with that property)
Model Type: Neuron or other electrically excitable cell; Realistic Network;
Brain Region(s)/Organism: Cerebellum;
Cell Type(s): Cerebellum Purkinje GABA cell; Cerebellum interneuron granule GLU cell; Vestibular neuron; Abstract integrate-and-fire leaky neuron;
Channel(s): I K; I Na,t; I L high threshold; I M;
Gap Junctions:
Receptor(s): AMPA; Gaba;
Gene(s):
Transmitter(s):
Simulation Environment: EDLUT; NEURON; MATLAB;
Model Concept(s): Activity Patterns; Sleep; Long-term Synaptic Plasticity; Vestibular;
Implementer(s): Luque, Niceto R. [nluque at ugr.es];
Search NeuronDB for information about:  Cerebellum Purkinje GABA cell; Cerebellum interneuron granule GLU cell; AMPA; Gaba; I Na,t; I L high threshold; I K; I M;
/
LuqueEtAl2019
EDLUT
Articulo purkinje
CASE_B
include
m4
src
README *
AUTHORS.txt *
CASE_A.ncb
CASE_A.vcproj
CASE_B.ncb
CASE_B.sln *
CASE_B.suo
configure *
configure.ac *
COPYING.txt *
Doxyfile *
flags.makefile.in *
INSTALL *
makefile.in *
noout2par.m *
rules.makefile.in *
static-variables.makefile *
varlog_reduced_VOR.m *
                            
Basic Installation
==================

   These are generic installation instructions.

   The simplest way to compile this package is:

  1. `cd' to the directory containing the package's source code and 
  type `./configure' to compile the package. It automatically checks
  for all the needed prerequisites in order to compile EDLUT, i.e. if it finds
  Matlab and Simulink installed in the system, it configures the makefile
  to compile also the edlut mexfile and edlut sfunction, if it finds openMP
  installed in the system, it sets the makefile to use this utility, and similarly
  to CUDA installation. Several configuration parameters can be used on configuring
  the compilation:
  - '--with-matlab=/pathmatlab': It forces to use /pathmatlab as the root matlab dir.
  It can be needed if matlab folder is not included in your system path.
  - '--without-matlab': It avoids the generation of matlab mex file and simulink sfunction.
  - '--without-simulink': It avoids the compilation of EDLUT as a simulink sfunction.
  - '--enable-debugging': It generates debugging information (by default this option is disabled).
  - '--enable-profiling': It generates profiling information (by default this option is disabled).
  - '--disable-openmp': It disable the use of openMP (by default openMP is enabled if it is installed in the system).
  - '--with-cuda=/cudapath': It forces to use /cudapath as the root cuda dir. It can be
  needed if cuda folder is not included in the system path.
  - '--without-cuda': It avoids the generation of cuda version of EDLUT.
  
  1. Type `make' to compile the package. By default it compiles EDLUTKernel executable, 
  Stepbystep and PrecisionTest examples, EDLUT library for C/C++ developers, matlab mex 
  function in the mex folder, and simulink sfunction in the sfunction folder. Other 
  installations are commented below. 

  2. Type `make install' to install the programs and any data files and
  documentation. Probably you will need root permisions to execute this command.

  3. You can remove the program binaries and object files from the
     source code directory by typing `make clean'.  

Other Installations
===================

   You can use differents targets with make command. In this installation package,
the following ones are allowed:

- library     : generates the library
- dox         : generates the doxygen documentation if Doxyfile exists
- doxclean    : cleans up the documentation
- clean       : cleans up .o lib and exe files
- distclean   : cleans everything except source+headers
- install     : installs the library
- install-dev : installs the library along with documentation+header files
- install-exe : installs the executable
- uninstall   : uninstalls the library
- pkgfile     : generates the pkg-config file
- flags       : shows the flags that will be used
- rules       : shows this text
- clear       : clears #* & dependency files