Glossary (Terms & Definitions)

A "Bookmark" is used to save the state of a window. It can be restored later.

Software package from Flexera Software (former Acresso, Macrovision and Globetrotter) that verifies license keys. SpiceVision PRO requires a FlexNet license key to run.

A FlexNet protected license that is automatically shared between computers in a local network.

A FlexNet protected license that is bound to a certain computer.

A "Project" file includes all design related settings used to load the input files. The project file has the extension .vpj.

A "Snapshot" is used to save the state of the Cone window to a file. It can be restored later — or sent to a colleague.

Name of the software tool. It reads Spice files, generates and displays schematic pictures for debugging and documentation.

File format to define netlist information (originally developed at UCB).

Additional hints for the Spice parser. This includes the identification of power/ground and input/output nodes (to override the default recognition methods). See also Read Spice dialog.

A "Workspace" defines all current settings of the GUI (including all check boxes, colors, etc.). The workspace file has the extension .ws.

The Cone window displays schematic fragments that allow for incremental navigation using double clicks.

The Console window displays warnings and error messages and can be used to interactively enter API commands.

A Context Menu is popped up if the right mouse button is pressed (but not moved) over a Database Object.

Drag & Drop is done by pressing the left (or right) mouse button over a Database Object and then moving it to another window (Schem, Cone, Source, Mem) or to the Read Spice dialog’s advanced buttons (for defining Spice Additives).

A mechanism to highlight certain Database Objects (instance, net, pin) simultaneously in all views (in all windows).

The Mem window can be used as a notepad (memory) to temporarily store Database Objects.

A dialog window to select the Spice file and all additives (Spice parser options). The dialog’s Read button starts the Spice parser. The buttons in the "Advanced" part of the dialog are also drop-targets for Drag & Drop.

The Schem window displays the schematic pages of one Module.

The Search window is used to query the Database. Search results are displayed in a list of Database Objects and can be used for highlighting and other functions.

The Selection Label displays the most recently selected Database Objects.

The Source window displays the source file of the loaded design.

A label that is displayed under the mouse cursor on appropriate objects after a small delay. Tooltips usually give additional context sensitive information or hints about the object under the mouse cursor.

The Tree window displays the design hierarchy tree.

The Pane window is a container for a Tab group.

Each Database Object can store attribute strings in a name=value syntax (these attributes are module-based in contrast to Flat Attributes).

ZDB binary file representation of the database memory.

A database stores the full design: the top Module(s) plus all sub modules.

A Database object is one of: Module, Primitive, Port, PortBus, Instance, Pin, PinBus, Net or NetBus.

Each Database Top Module can store instance-tree-based attributes - called "Flat Attributes" (in parallel to module-based Attributes). They also follow the name=value syntax.

The "Meta Attributes" control what Attributes and Flat Attributes are displayed in the Schem and Cone windows. They are called @nlv or @nlv:.. and are attached to a Module or Primitive or to the Database root.

A Database Module represents a Spice sub-circuit or the top-level circuit. The Tree window displays the tree of Modules.

Each Database Object can be referred to by an OID (Object Identification). OIDs can store the path through the hierarchy tree to a certain instance.

A Database Primitive represents a cell with a defined function. For a Spice design this is a device, e.g. a MOS transistor or a resistor.