Re: gEDA-user: Using .global statements in GNUcap and mult transistors

2009-03-06 Thread r
On Thu, Mar 5, 2009 at 2:23 AM, al davis ad...@freeelectron.net wrote: The Gnucap behavior is consistent with Hspice and Spectre.  At least that is what I have been told.  I don't have access to them to check it out. That's incorrect. Both Spectre and Hspice treat devices with m1 as

Re: gEDA-user: Using .global statements in GNUcap and mult transistors

2009-03-06 Thread al davis
On Friday 06 March 2009, r wrote: ok  maybe you can help solve this. Well, I'm not sure. I don't know how it is implemented in these simulators. I guess these guys have simply modified the models (they have modified quite a few other things there so I guess they wouldn't have minded

Re: gEDA-user: Using .global statements in GNUcap and mult transistors

2009-03-06 Thread Dan McMahill
r wrote: BTW, some simulators preprocess the netlist and reduce parallel devices into a single device with an m parameter set. This gives a huge performance boost in extracted sims. I'm curious as to which simulators and if they are smart enough to get the reduction right all the time. -Dan

Re: gEDA-user: Using .global statements in GNUcap and mult transistors

2009-03-04 Thread r
On Wed, Mar 4, 2009 at 7:07 AM, al davis ad...@freeelectron.net wrote: like it, for example, I put m=50 to report the full current instead of 1/50 of the current going into it. The Gnucap behavior is consistent with Hspice and Spectre.  At least that is what I have been told.  I don't have

Re: gEDA-user: Using .global statements in GNUcap and mult transistors

2009-03-04 Thread al davis
On Wednesday 04 March 2009, r wrote: On Wed, Mar 4, 2009 at 7:07 AM, al davis ad...@freeelectron.net wrote: like it, for example, I put m=50 to report the full current instead of 1/50 of the current going into it. The Gnucap behavior is consistent with Hspice and Spectre.  At least

Re: gEDA-user: Using .global statements in GNUcap and mult transistors

2009-03-04 Thread John P. Doty
al davis wrote: The Gnucap behavior is consistent with Hspice and Spectre. At least that is what I have been told. I don't have access to them to check it out. The behavior is an artifact of the implementation. In Gnucap, m works for all devices, including plugin models and

Re: gEDA-user: Using .global statements in GNUcap and mult transistors

2009-03-04 Thread al davis
On Wednesday 04 March 2009, John P. Doty wrote: I hope you haven't implemented the ngspice brain damage that causes it to apply the m= multiplier repeatedly for each successive analysis (your transistors grow as you proceed). Only when you use NGspice models as plugins. :-) Seriously I

gEDA-user: Using .global statements in GNUcap and mult transistors

2009-03-03 Thread Yamazaki R2
Quick questions: Why doesn't the .global statement work in gnucap? Do you have to add flags to compile it with that option similar to ngspice? If so how? Another question is when you probe current of transitors with multiple legs, it splits up the current instead of giving you

Re: gEDA-user: Using .global statements in GNUcap and mult transistors

2009-03-03 Thread al davis
On Tuesday 03 March 2009, Yamazaki R2 wrote: Why doesn't the .global statement work in gnucap? There hasn't been much demand for it. In other simulators that have it, it often leads to surprise results. Do you have to add flags to compile it with that option similar to ngspice? If so how?