You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
dwarning 09561884fe to see the full beautiness 19 years ago
..
TransImpedanceAmp polishing 19 years ago
adms polishing 19 years ago
bin polishing 19 years ago
bsim1 polishing 19 years ago
bsim2 polishing 19 years ago
bsim3 polishing 19 years ago
bsim3soidd polishing 19 years ago
bsim3soifd polishing 19 years ago
bsim3soipd polishing 19 years ago
bsim4 polishing 19 years ago
filters polishing 19 years ago
general polishing 19 years ago
hfet polishing 19 years ago
hisim polishing 19 years ago
jfet polishing 19 years ago
mes polishing 19 years ago
mesa polishing 19 years ago
mos6 polishing 19 years ago
polezero polishing 19 years ago
resistance polishing 19 years ago
sensitivity polishing 19 years ago
transient polishing 19 years ago
transmission polishing 19 years ago
vbic polishing 19 years ago
.cvsignore * DEVICES: Adjusted spacing. 26 years ago
ChangeLog Update of docs and test. Added mesa test files. 25 years ago
Makefile.am Added bin directory to dist target. 22 years ago
README Fixed spelling errors 21 years ago

README

ngspice test and example files:
===============================

This directory is organized as a tree of subdirectories containing test files
for devices and analyses implemented in ngspice.

Some files comes from the original Spice3f5 package and others have been
contributed by developers and users.


File Extension Convention:

.cir : Circuit file. This can be a simple circuit description or a spice2
input file.
.out : .cir files have been run and results are recorded into this
type of file. This is useful if want to test ngspice against
known (hopefully correct results).

REPLICATE TESTS

To replicate tests you have to launch configure without any option and
compile ngspice. In the future this will change.

TO ADD NEW TESTS

Take an existing test and adopt it to your liking. Add the test
script and its supporting files to Makefile.am. Use `make check' to
see your new test in action.