Browse Prior Art Database

Mixed Simulation Model Generation System

IP.com Disclosure Number: IPCOM000101723D
Original Publication Date: 1990-Aug-01
Included in the Prior Art Database: 2005-Mar-16
Document File: 2 page(s) / 89K

Publishing Venue

IBM

Related People

Williams, RQ: AUTHOR

Abstract

A system is disclosed for creating single circuit simulation model libraries automatically by combining complex existing model libraries with a minimum of user interaction. This system allows different FET simulation models to be available in one simulation, and applications include analysis of chip-to-chip and macro-to-macro circuits.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Mixed Simulation Model Generation System

       A system is disclosed for creating single circuit
simulation model libraries automatically by combining complex
existing model libraries with a minimum of user interaction. This
system allows different FET simulation models to be available in one
simulation, and applications include analysis of chip-to-chip and
macro-to-macro circuits.

      Without the described system, conflicts arise when attempting
to utilize several versions of similarly configured model libraries
in the same circuit simulation. Examples include naming conflicts,
entry point conflicts, and file allocations used.

      When implementing a new mixed model simulator, a menu system
collects parameters, such as existing model dataset names, external
Fortran dataset names, and the name for the new mixed model library.
Referring to the figure, components of a mixed model generation
system are shown. The first step in the process (1) performs
initialization and bookkeeping, such as verification of valid model
names, and creates empty files for the new mixed model library. Step
2 is an analysis of the model libraries to be mixed. During the
analysis, each model is identified by name, separated from its
original library, and a table of models is created. In step 3, any
external Fortran subroutines and functions are parsed for structural
content (entry points). As each program unit is analyzed, its entry
points (external addresses) are recorded in a symbol table for later
use. In steps 4 and 5, the source code for ASTAP and Fortran are
copied into files for the mixed model library.

      Step 6 is an editing phase where each ASTAP model is modified
to have unique model names. This is an important step since the model
name is one of the...