[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: gEDA-user: Google Summer of Code on gEDA Webpages
Hi John,
On Sunday 11 March 2007 18:31, John Griessen wrote:
> Werner Hoch wrote:
> > On Sunday 11 March 2007 11:20, Ben Jackson wrote:
> >> On Sun, Mar 11, 2007 at 11:02:33AM +0100, Werner Hoch wrote:
> >>> I've played with LTSpice an hour.
> >>>
> >>> Things I don't like:
> >>> * only one simulation at a time.
> >>
> >> Is that true even if you open multiple schematics?
> >
> > No, no. I need a simulator where I can specify lots of simulations
> > to the same circuit.
> >
> > If you have a simple transistor amplifier circuit you'd like to
> > know:
> >
> > * the bias point (maybe with the temperature as parameter)
> >
> > * small signal ac analyses (with different parameters)
> >
> > * large signal ac analyses (maybe with fourier analyses)
> >
> > * step response
> >
> > * behavior when using the circuit at different loads.
> >
> > * and many more.
>
> Werner, does your workflow involve just one schematic for all those
> cases, or some different ones, for the different parameters, loads,
> large vs. small signal?
Yes, that's the idea.
> It seems as if the cases could be handled as many schematics, but
> having one schematic with lots of probes/sources and a way to change
> properties and sources based on just the probes and signal sources
> would be better for iterating changes to the circuit since the
> circuit changes would be on just one page.
Yes. Think about the oppisite:
If you can only do one simulation with one schematic at a time, you can
either:
* Copy your schematic multiple times (each with different simulations)
* Change the simulation setup between the differen simulations.
If you have to make a small change in the circuit both cases are stupid.
You have to apply that change to all circuits, or remember all your
different simulation and parameter setups.
> The Hspice front ends I've used had little change in the graphical
> part, and parameters were changed in a text file to get all the
> corner cases, etc.
That's possible in (ng)spice, too. But I don't think that many people
can write simulation files (cir-files) or tcl-scripts for tclspice.
The target should be to reduce the gap between the "one simulation at a
time" and the hand written simulation files.
> A blend of both would be great. In gnucap (Future edition with
> plugins for all), that might look like probes and sources as plugins
> that can be updated with a GUI, and also have properties coming from
> a text file, and both GUI and text file are always in sync.
Fully agreed.
Regards
Werner
_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user