dsengupta wrote:1. How does NEURON deternime how long the x axis has to be on the graph
Figures it out for itself. If you save the graph to a session file (not sure how? see
What is a ses (session) file? in NEURON's FAQ list (link is on the Documentation page at
http://www.neuron.yale.edu/) and examine the contents of that file, you will see something that looks like this:
- Code: Select all
objectvar save_window_, rvp_
. . . a bunch of code . . .
flush_list.append(save_window_)
save_window_.save_name("flush_list.")
objectvar rvp_
rvp_ = new RangeVarPlot("v")
node[5] rvp_.begin(1)
dend[0] rvp_.end(1)
rvp_.origin(0)
. . . more code . . .
}
objectvar scene_vector_[1]
{doNotify()}
from which you might infer that the RangeVarPlot class has something to do with it, and reading the Programmer's Reference documentation of that class you would confirm your suspicion--and discover a link to documentation of a hoc function called distance(), which you might also want to read.
How do you inject a current/ impulse at a specific point along the axon.
Use an IClamp. Can be created with hoc statements (see Programmer's reference documentation of the IClamp class) or via the GUI (see
the tutorial
Construction and Use of Models: Part 1. Elementary Tools (link is on NEURON's Documentation page)).
when I am graphing the myelinated model in a space plot, I am getting waves, but when I am running the unmyelinated model I am getting I flat line moving up and down. I think this is because the default x axis of the unmyelinated space plot is much shorter (1000 units) than the myelinated model (35000 units).
First a comment: in NEURON the units of length are microns. The behavior of your nonmyelinated model suggests to me that its spatial discretization parameter nseg is 1, so the entire axon is treated as a single compartment. You might try executing
forall nseg*=3
at the oc> prompt, and see how that affects the simulation. To discover an appropriate value for nseg, you might try (in pseudocode)
- Code: Select all
REPEAT
forall nseg*=3
run a simulation
UNTIL there is no significant change from the previous simulation results
Hint: the keyboard's up arrow can be used to retrieve previous commands.