Re: [moose-devel] Error in moose.connect method

[Jaeger, D. <dj...@em...>]

Same interest here.  -Dieter

-----Original Message-----
From: Dave Beeman [mailto:db...@Co...] 
Sent: Tuesday, April 29, 2014 4:05 PM
To: Moose development issues
Subject: Re: [moose-devel] Error in moose.connect method

I will be very interested in trying out the MOOSE Python implemention of hsolved when it is fully ready.

In GENESIS 2, hsolve performs both the functions of a Hines method compartmental solver, and of a Discrete Event Solver for the efficient delivery of spike messages.  Ideally, these should be in separate solvers, as they are in GENESIS 3 (unfortunately still under development).

How is this being handled in MOOSE?  Can networks of hsolved cells in MOOSE benefit from equivalent optimizations in spike delivery that GENESIS hsolve gives?  Or is a separate mechanism used for spike delivery?

On Tue, 29 Apr 2014, Dilawar Singh wrote:

> Hi Saeed,
>
>     We are in process of integrating 'hsolve' into async13 branch. Only today, I
>     got some sanity check of hsolve working. I am not sure how long it will take
>     to get hsolve properly integrated with python.
>
>     For time being -- if you want to use async13 branch -- you can change the
>     solver to 'ee' from 'hsolve'.
>
>     I'll let you know as soon as hsolve is ready.
>
> Dilawar

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos.  Get unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
moose-devel mailing list
moo...@li...
https://lists.sourceforge.net/lists/listinfo/moose-devel