RE: awaves file format

"Rui Tavares" <[email protected]>
Newsgroups gmane.comp.gnu.gnucap.general,gmane.comp.gnu.gnucap.devel
Message-ID <[email protected]>
.:-----Original Message-----
.:From: [email protected] [mailto:help-gnucap-
.:[email protected]] On Behalf Of nbs_r
.:Sent: sexta-feira, 9 de Junho de 2006 15:22
.:To: [email protected]; [email protected]
.:Subject: Re: [Help-gnucap] awaves file format
.:
.:There was a library for reading *.tr? files in gwave last time I
.:checked. It cannot read all hspice file formats though (you need set
.:specific simulation options).

Ok. I'll check it.

.:
.:Why not to just use a .print or .measure statement? I am using hspice
.:quite extensively and rarely start waveform viewer.

I'm trying to calculate the settling time of an ampop. I wanted to do it
automatically/programmable. The thing that came to my mind, was ".measure".
It was easier and simpler...

>From what I understood from the hspice manual, it is difficult to measure it
with ".measure". I do not know how many times the signal RISEs and/or FALLs
before settle, or enter the acceptable error margin... Is it any other way?


Thanks for your answer,



.:
.:Rui Tavares wrote:
.:> Hi all,
.:>
.:>
.:> Does anyone know the awaves file format generated by hspice?
.:>
.:> I need to read it, and make some processing based on the graph point
.:values.
.:>
.:>
.:> Thanks in advance,
.:>
.:> 	Rui Tavares
.:>
.:>
.:>
.:> ------------------------------------------------------------------------
.:>
.:> _______________________________________________
.:> Help-gnucap mailing list
.:> [email protected]
.:> http://lists.gnu.org/mailman/listinfo/help-gnucap
.:>
.:>
.:
.:
.:
.:
.:
.:_______________________________________________
.:Help-gnucap mailing list
.:[email protected]
.:http://lists.gnu.org/mailman/listinfo/help-gnucap

_______________________________________________
Help-gnucap mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/help-gnucap
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.