From: D. C. Sessions (firstname.lastname@example.org)
Date: Mon Jan 24 2000 - 07:43:39 PST
Jim Freeman wrote:
> Hi Fred,
> Hspice will accomodate different models from different vendors but not automatically. If scale is the same for different models, all you
> have to do is rename the models from other vendors with a unique name and edit the netlist to reference the same name. I have simulated up to
> 8 different technologies in the same simulation using this technique. I have no idea how high it can go but I suspect the limit has to do more
> with the simulation machine than the Hspice code.
That's fine if you have editable models.
The problem arises when people propose *encrypted* models as
a solution to the distribution-of-proprietary-data problem.
> Fred Balistreri wrote:
> > Hello Jim, the answer is no. Not even Hspice will do that if the
> > parts are from different vendors that use different modeling
> > methodologies. Hspice also uses propietary models, those
> > cannot be done by law. However the levels that are public
> > are compatible. That is one of the reasons why I said I
> > understand why people use Hspice.
> > However realize that Hspice is designed for IC not SI
> > engineers. Where as Aspice is designed for SI engineers.
> > The advantages we have are not in the IC areas but rather
> > in the SI area. I realize that transistor level model do play
> > an important role and for that we do have a solution although
> > it may not be as "clean" as one would like.
> > Best Regards,
> > Jim Freeman wrote:
> >> Part 1.1 Type: Plain Text (text/plain)
> >> Encoding: 7bit
> > --
> > Fred Balistreri
> > email@example.com
> > http://www.apsimtech.com
-- D. C. Sessions firstname.lastname@example.org
**** To unsubscribe from si-list: send e-mail to email@example.com. In the BODY of message put: UNSUBSCRIBE si-list, for more help, put HELP. si-list archives are accessible at http://www.qsl.net/wb6tpu ****
This archive was generated by hypermail 2b29 : Thu Apr 20 2000 - 11:34:48 PDT