Re: [ng-spice] introduction, ideas, compiler warning fix
Jan Vercammen wrote:
> I have a good background in algorithms for analog simulation, however I
> lack the handson expertise. In order to bring ng-spice to a good end I would
> suggest the following list:
>
> -1- remove the compiler warnings
> -2- improve on the make and configuration?
> -3- convert to Ansi-C (I remember that a conversion K&R C to Ansi-C exists,
>right?)
> -3- remove current memory leaks
> -4- have a look at subcircuit expansion, it does not always work
> -5- think about a new front-end - pre-processor (.param, .global, ...),
>lexical stuff,
> parsing, subckt expansion, scripting, ...
> -6- work out and document kernel operation, find details of .op, .dc, .ac
>and .tran
> -7- work out details and document component models: RLCK, sources,
>transmission lines, ..
> -8- work out details and document on how to include new elements
> -9- work out details and document sparse matrix package
> -10- study algorithms for block sparse matrix codes, can we use the current
>code?
> What about threading or MPI?
> -11- and many other things for doing EMC analysis
>
> I would like to keep working in C, I do not favour C++. With respect to
>rebuilding
> the analog kernel from scratch or to use a new sparse matrix package I
>would advice
> negative.
>
Hello!
-3)?? Memory leaks are also big problem for me. Have You any idea of
finding them?
-4-5) Front-end is one of the worst part in Berkeley Spice3f5. I spend a
looong time working on it some
time ago to fix core dumps. It was terrible.
And I also prefer C over C++.
Welcome on the group!
--
Best Regards
Michael Widlok
University of Mining and Metallurgy
ul. Heleny 12/137
30-838 Krakow
Poland
Partial thread listing: