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 278f3c64fd update to 4.3 16 years ago
..
bin tiny update 16 years ago
bsim1 tiny update 16 years ago
bsim2 tiny update 16 years ago
bsim3 tiny update 16 years ago
bsim3soi tiny update 16 years ago
bsim3soidd tiny update 16 years ago
bsim3soifd tiny update 16 years ago
bsim3soipd tiny update 16 years ago
bsim4 tiny update 16 years ago
filters tiny update 16 years ago
general tiny update 16 years ago
hfet tiny update 16 years ago
hisim tiny update 16 years ago
jfet tiny update 16 years ago
mes tiny update 16 years ago
mesa tiny update 16 years ago
mos6 tiny update 16 years ago
polezero tiny update 16 years ago
resistance tiny update 16 years ago
sensitivity tiny update 16 years ago
transient tiny update 16 years ago
transmission tiny update 16 years ago
vbic tiny update 16 years ago
.cvsignore * DEVICES: Adjusted spacing. 26 years ago
ChangeLog Update of docs and test. Added mesa test files. 25 years ago
Makefile.am Removed adms directory from dist target 17 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.