Re: [ng-spice-devel] ACS new code


To ng-spice-devel@ieee.ing.uniroma1.it
From "GLAO S. Dezai" <dezai@hotbot.com>
Date Wed, 14 Feb 2001 08:23:18 -0800
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
Organization HotBot Mail (http://mail.hotbot.mailcity.lycos.com:80)
Reply-To ng-spice-devel@ieee.ing.uniroma1.it

  
Hi,
Paolo suggested to move to ACS for the new simulator. 
1)What does it means ?
   a)Building a new simulator with ACS as   basis   but with a new name new 
code organization, new parser (according to the previous discussions on 
netlist issues),...
   b)Hacking ACS code as we did in ng-spice.
   c)?

2)we must better know what ACS is.
 a)ACS code: Speed,Reliability and Robustness. 
Does the code has been tested on the standard Spice  benchmarks ?
 b)Portability ?
 c)Compatibility with Spice3(results and commands)
 ....
3)How can we organize for such a task ?.
4) What is the target platform: Linux, Windows, Both ?.
5)...
==========================================
I have a good opinion about ACS because it is written in C++. I found ACS 
when trying myself to rewrite spice3 in C++, two years ago.I have not been 
able to compile it under my Microsoft Visual C++ 4.0 compiler. But i think it 
should be less buggy than the spice3f5 code. But is it faster ? In Spice3 I 
have found the code written by Quarles imself more robust and reliable. The 
analysis part of spice3f5 and the sparse matrix package are well written 
(with the spirit of object oriented langage, while written in C). A 
comparaison has been made between spice3 and ACS on the analysis results 
basis.
Finaly if we have to move to ACS, then  a better organization must take place 
for such a job. I suggest an organization by topics with a todo list by topic 
a moderator by topic and a devellopement list by topic. Topics could be 
1. Testing and benchmarks
2. Analysis  
3. Math package
4. Models
5. Frontend (GUI)
   5.1 Entry (schematic editor, text editor)
   5.2 Parser 
6. Documentation

Other suggestions
 .Target Both Linux and Windows. 
   (Cross platform compilation ? Qt? UWIN? CYGWIN?)
 .Not keep al ".dot" format but choose between alan or paolo format. Let 
".dot" format for commands and everything else for devices \resistance or 
#resistance or
 5%#%5%%#%resistance :-)

Cheers










HotBot - Search smarter.
http://www.hotbot.com

Partial thread listing: