h.run vs h.continuerun(h.tstop)
Posted: Wed Sep 25, 2024 9:09 pm
Hello all,
Apologies if this is a very novice question. I am just getting started but struggling to understand the difference between h.run and h.continuerun(h.tstop), after explicitly defining h.tstop in both situations.
I found that h.continuerun(h.tstop) applies my h.finitialize(-60 * mV), but h.run() seems to ignore this and sets it to the default -65 mV.
However, h.run() applies the extracellular potential field (that I precomputed in COMSOL) to the axon, but h.continuerun(h.tstop) doesn't do this.
This makes it very annoying as I cannot get both constraints in the same simulation.
Further, when I use h.run(), I seem to get a remnant of the previous simulation at the beginning of my code. What could be the reason for this?
Apologies if this is a very novice question. I am just getting started but struggling to understand the difference between h.run and h.continuerun(h.tstop), after explicitly defining h.tstop in both situations.
I found that h.continuerun(h.tstop) applies my h.finitialize(-60 * mV), but h.run() seems to ignore this and sets it to the default -65 mV.
However, h.run() applies the extracellular potential field (that I precomputed in COMSOL) to the axon, but h.continuerun(h.tstop) doesn't do this.
This makes it very annoying as I cannot get both constraints in the same simulation.
Further, when I use h.run(), I seem to get a remnant of the previous simulation at the beginning of my code. What could be the reason for this?