RE: [ng-spice-devel] Spice output format


To "'ng-spice-devel@ieee.ing.uniroma1.it'" <ng-spice-devel@ieee.ing.uniroma1.it>
From "Gillespie, Alan" <Alan.Gillespie@analog.com>
Date Thu, 11 Jan 2001 18:19:10 -0000
Delivered-To mailing list ng-spice-devel@ieee.ing.uniroma1.it
Mailing-List contact ng-spice-devel-help@ieee.ing.uniroma1.it; run by ezmlm
Reply-To ng-spice-devel@ieee.ing.uniroma1.it

I also like the reference variable update to the screen,
since I was used to using PSPICE, which always tells you
what its doing.

I'm off till Monday, so I won't be able to comment any
more till then but I think I should be able to do a quick
hack to arrange this. I've a niggly feeling that there's
more too it than that, though, or I'd have done it already.

Cheers,

Alan


> -----Original Message-----
> From: Paolo Nenzi [mailto:pnenzi@ieee.ing.uniroma1.it]
> Sent: 11 January 2001 18:01
> To: ng-spice-devel@ieee.ing.uniroma1.it
> Subject: [ng-spice-devel] Spice output format
> 
> 
> Hi all,
> 
> I hope that you have spent nice holidays. Last ngspice release is the 
> rework13, released in November 2000 (too muche time ago, for ngspice
> standards ;-)). Rework-13 suffers from bugs introduced trying 
> to correct
> arroneous memory handling in the file varialbe.c. The code in 
> the CVS has
> been corrected, but some bugs still resists, as the noise bug 
> appeared on
> this list. 
> 
> 
> Now on the output format issue:
> 
> I agree with the opinions expressed on the list, to revert the output
> format to the original one, since the pspice raw format may violate 
> copyright and most postprocessing tools written around spice 
> expect the
> original format. I agree with the idea to write a converter (or see if
> a such piece of software is already available). 
> 
> What I would like to leave in code is the branch currents "hack".
> 
> Wait for your opinions
> Paolo  
> 

Partial thread listing: