-
Notifications
You must be signed in to change notification settings - Fork 16
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'master' into jelic/cvode_visitors
- Loading branch information
Showing
29 changed files
with
844 additions
and
92 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
Longitudinal Diffusion | ||
====================== | ||
|
||
The idea behind ``LONGITUDINAL_DIFFUSION`` is to allow a ``STATE`` variable to | ||
diffuse along a section, i.e. from one segment into a neighbouring segment. | ||
|
||
This problem is solved by registering callbacks. In particular, NEURON needs to | ||
be informed of the volume and diffusion rate. Additionally, the implicit | ||
time-stepping requires information about certain derivatives. | ||
|
||
Implementation in NMODL | ||
----------------------- | ||
|
||
The following ``KINETIC`` block | ||
|
||
.. code-block:: | ||
KINETIC state { | ||
COMPARTMENT vol {X} | ||
LONGITUDINAL_DIFFUSION mu {X} | ||
~ X << (ica) | ||
} | ||
Will undergo two transformations. The first is to create a system of ODEs that | ||
can be solved. This consumed the AST node. However, to print the code for | ||
longitudinal diffusion we require information from the ``COMPARTMENT`` and | ||
``LONGITUDINAL_DIFFUSION`` statements. This is why there's a second | ||
transformation, that runs before the other transformation, to extract the | ||
required information and store it a AST node called | ||
``LONGITUDINAL_DIFFUSION_BLOCK``. This block can then be converted into an | ||
"info" object, which is then used to print the callbacks. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.