[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Help-gnucap] Stochastic current inputs

From: Chinasaur
Subject: [Help-gnucap] Stochastic current inputs
Date: Thu, 29 Nov 2007 14:32:52 -0800 (PST)

Hi, I'm new to gnucap, trying to use it to simulate the behavior of a network
of biological cells.

At the moment the only analyses I need to run are operating points.  The
task is, given a network of cells with resistive connections between them,
get the operating points under a series of stationary, stochastic input

In case that wasn't clear, here's one simple approach to the task.  I have
one netlist with all the resistive elements.  I merge this with a netlist
describing the independent current sources and then run the operating point,
saving the output.  Then I stochastically generate a new current source
netlist, merge the resistor netlist with the new current netlist, and run
another operating point.  I repeat this several thousand times.

Any advice on more sophisticated approaches to this problem?  I read through
the documentation on behavioral modeling but didn't see any methods for
designating stochastic current sources.  Are there SPICE variants with
relevant functionality?

Assuming I must implement this myself, any advice on optimization?  I
thought the method described above was a bit inefficient since it involves
reading in the resistive network over and over.  So I tried an
implementation that at least avoids doing that.  I created a netlist
describing the resistors and current sources, but using parameters to
designate the current values.  Then I created a command file with .parameter
commands for every current source followed by .op commands; this command
file resets the current source parameters and runs the operating point over
and over, up to 1000 times.  I thought this would be more efficient as it
only loads the architecture of the resistive network once and then just
overwrites the current source parameters each time.  But it seems there's
some leak because the more times the parameters are reassigned, the slower
everything runs.  Is this the behavior expected?

Thanks in advance for any insight!
View this message in context:
Sent from the Gnucap - Help mailing list archive at

reply via email to

[Prev in Thread] Current Thread [Next in Thread]