File: BUGS

package info (click to toggle)
ngspice 44.2%2Bds-1
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 73,372 kB
  • sloc: ansic: 560,757; cpp: 17,623; xml: 9,372; makefile: 4,076; sh: 2,664; perl: 2,442; yacc: 1,549; tcl: 1,040; lex: 320; pascal: 241; python: 179
file content (32 lines) | stat: -rw-r--r-- 1,415 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
This file contains a list of known but not yet fixed bugs in ngspice.
===========================================================================

How to submit a bug report:

There are two methods to report a bug you have discovered in ngspice:

    * Bug tracker: This is the preferred method of reporting a bug.
      Using the tracker on Sourceforge.net site will make your report
      open by everyone and the chances of finding a fix will increase.

    * ngspice-devel list: If you are a member of this list, you can write
      directly to the developers' list. Do not subscribe to the list only
      for sending bug reports.

Before sending a bug report please note: all information you send to the bug
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 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:
------------------------------------------------------------------------------
* pole-zero analysis

  The pole-zero (.pz) analysis, which still uses the original spice3f5
  algorithms, does not give correct results for all tested input files.
  The effort to correct that issue seems to be large.