|
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
See:
Description
Interface Summary | |
---|---|
RTBounds | Interface to define the objects stored in an R-Tree. |
Class Summary | |
---|---|
ArcInst | An ArcInst is an instance of an ArcProto (a wire type) An ArcInst points to its prototype, the Cell on which it has been instantiated, and the connection at either end of the wire. |
Connection | An abstract class Connection is the link between a PortInst on a NodeInst and an ArcInst. |
Geometric | This class is the superclass for the Electric classes that have visual bounds on the screen, specifically NodeInst and ArcInst. |
HeadConnection | A HeadConnection represents connection on the head end of the ArcInstance. |
NodeInst | A NodeInst is an instance of a NodeProto (a PrimitiveNode or a Cell). |
PortInst | The PortInst class represents an instance of a Port. |
RTNode | The RTNode class implements R-Trees. |
RTNode.Search | Class to search a given area of a Cell. |
TailConnection | A TailConnection represents connection on the tail end of the ArcInstance. |
Topology | A class to manage nodes and arcs of a Cell. |
Package for connected Nodes and Arcs. Each facet consists of a network of nodes and arcs. Nodes are electrical components such as transistors and contacts. Arcs are wires that connect nodes. Each node has ports on it which are the sites of arc connections. A port may connect to any number of arcs, but every arc connects exactly two ports.
Actual implementation of the database uses two types of objects for the nodes, arcs, and ports. A single prototype object describes the typical node, arc, or port; and multiple instance objects are created for every actual node, arc, and port used in a circuit. Thus, the transistor is represented as a node prototype and four port prototypes in the technology. Every use of a transistor in a circuit is then represented as a node instance with port instances for the connections.
|
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |