From: Ekaterina B. <de....@gm...> - 2013-01-11 08:55:25
|
Dear Niraj, the reason why I asked was that if I replace moose.useClock(0, '/model/##', 'process') with solver = moose.HSolve('/model/solve') solver.dt = moose.element('/clock/tick[0]').dt solver.target = '/model/' #I've tried also solver.target = '/model/##' moose.useClock(0,'/model/solve', 'process') then a simulation stopped working - I have a horizontal line instead of firing behavior... 2013/1/11 Niraj Dudani <ni...@nc...> > Hi Katja, > > > solver = moose.HSolve('/model/solve') > > solver.dt = moose.element('/clock/tick[0]').dt > > solver.target = '/model/' > > moose.useClock(0,'/model/solve', 'process') > > > > instead of: > > moose.useClock(0, '/model/##', 'process') > > > > does it look correct? > > This is perfect. > > Scheduling and solver setup is one thing that always leaves the doubt of: > "Am I doing this right?". For this reason, Aditya has already written a > utility function (moose.utils.resetSim()) to make scheduling of > biophysical objects easier. You may not need this, because you are only > scheduling the HSolve, and not Compartment, HHChannel, etc. We may even > look at resurrecting autoscheduling so that moose.useClock() is not needed > at all. Finally, I plan to upgrade Aditya's resetSim() function to handle > solver set up as well. > > For now, what you've done seems correct. Do let us know if you run into > problems. > > Best, > Niraj > > > > > > > ------------------------------------------------------------------------------ > Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and > much more. Get web development skills now with LearnDevNow - > 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. > SALE $99.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122812 > _______________________________________________ > moose-generic mailing list > moo...@li... > https://lists.sourceforge.net/lists/listinfo/moose-generic > |