luke
/
ngspice
mirror of https://git.code.sf.net/p/ngspice/ngspice
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

./BUGS, update the list of known bugs

This commit is contained in:
h_vogt 2013-07-27 09:19:06 +02:00 committed by rlar
parent 88cd0f324d
commit 4f39648320
1 changed files with 13 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
BUGS
View File

@ -18,20 +18,21 @@ tracking system or on the mailing lists is public. If you need to send
sensitive information, send them to a developer directly but still write non sensitive information, send them to a developer directly but still write non
sensitive data on the bug tracking system to keep track of bug history. sensitive data on the bug tracking system to keep track of bug history.
* please refer to the sourceforge bug tracker at
http://sourceforge.net/p/ngspice/bugs/
------------------------------------------------------------------------------ ------------------------------------------------------------------------------
OPEN BUGS: OPEN BUGS:
------------------------------------------------------------------------------ ------------------------------------------------------------------------------
* return value: * pole-zero analysis
When ngspice is called in batch mode it returns 1 even if the simulations The pole-zero (.pz) analysis, which still uses the original spice3f5
are run. The problem arises when there is a .control section but no algorithms, does not give correct results for all tested input files.
.print, .plot or .fourier lines. Ngspice outputs: The effort to correct that issue seems to be large.
Note: No ".plot", ".print", or ".fourier" lines; no simulations run
and exits returning 1. * voltage (and current) controlled switches need better timing
Workaround: add -r <dummyfile> to the command line to avoid this. The controlled switches (SW, CSW), which still stem from the original
spice3f5 implementation, sometimes lead to wrong results when on and off
* please refer to the sourceforge bug tracker at ramp times differ considerably.
http://sourceforge.net/tracker/?group_id=38962&atid=423915