The directory in which the Ptolemy software is installed.
An atomic (indivisible) function in a dataflow model of computation.
(1) Asynchronous transfer mode network protocol. (2) A sub-domain of the synchronous dataflow and discrete-event domains to provide the infrastructure for simulating ATM networks.
A fork star that is automatically inserted when a single output is connected to more than one input.
A C++ object that is used to define common interfaces and common code for a set of derived classes. An object may be a base class and a derived class simultaneously.
A domain using the Boolean-controlled dataflow model of computation. This domain attempts to use compile-time scheduling, but will fall back to run-time scheduling if necessary.
The base class defined in the kernel for stars, galaxies, universes, and targets.
A star or a galaxy.
code generation domain
A domain that defines many of the base classes and schedulers used in code generation domains. It has no direct application by itself.
A domain that synthesizes assembly code for the family of Motorola DSP56000 digital signal processors. It uses the synchronous dataflow model of computation.
A domain that synthesizes assembly code for the family of Motorola DSP96000 digital signal processors. It uses the synchronous dataflow model of computation.
A domain that synthesizes C code. It uses the synchronous dataflow or Boolean-controlled dataflow model of computation.
A code generation domain that uses the dynamic dataflow model of computation. This has not been maintained beyond version 0.4.1 of Ptolemy.
The simultaneous design of the software and hardware composing a system.
A simulation domain using the communicating processes model of computation. Each star forms a process that runs under the Sun lightweight process library.
A C++ object that is derived from some base class. It inherits all of the members and methods of the base class.
A model of computation in which actors process streams of tokens. Each actor has one or more firing rules. Actors that are enabled by a firing rule may fire in any order.
A simulation domain that uses the dynamic dataflow model of computation.
A simulation domain that uses the discrete-event model of computation. In the DE domain, particles transmitted between blocks represent events that trigger changes in system state. Events carry an associated timestamp, and are processed in chronological order.
A specific implementation of a model of computation.
The base class in the Ptolemy kernel from which all domains are derived.
The action of holding a mouse button while moving the mouse.
A particle generated by a block in a discrete-event model of computation. This particle carries a timestamp.
A schematic, palette, or icon as represented in oct. In pigi, a facet is exactly that represented by one vem window.
The Fast Fourier Transform is an efficient way to implement the discrete Fourier transform in digital hardware.
A unit invocation of an actor in a dataflow model of computation.
A rule that specifies how many tokens are required on each input of a dataflow actor for that actor to be enabled for firing.
A star that reads one input particle and replicates it on any number of outputs.
A block that contains a network of other blocks.
The class (derived from Block) in the Ptolemy kernel that represents a network of other blocks.
A graphical display of a parallel schedule of tasks. In Ptolemy, the tasks are the firings of stars and galaxies.
A domain implementing higher-order functions that are expanded at compile-time and incur no run-time overhead. HOF stars are typically embedded in other domains, and provide graphical expression of parameterized parallel, cascaded, and recursive structures.
homogeneous synchronous dataflow
A graphical object that represents a single block or palette.
[incr Tcl], an object oriented extension to Tcl.
A set of executions of blocks that constitutes one pass through the precomputed order of a compile-time schedule.
The set of classes defined in the directory $PTOLEMY/src/kernel.
In vem, a color with a given precedence. Colors with higher precedence will obscure colors with lower precedence.
In vem, the interface and contents facet referred to by an icon. The master is represented by an absolute Unix path name pointing to the directory in which the facet is stored.
A program for examining and changing the list of masters (see above) that make up a schematic or palette.
A simulation domain that uses a multidimensional extension to the synchronous dataflow model of computation. Actors in MDSDF consume data defined on rectangular grids, e.g. a subblock in an image.
A C++ object that forms a portion of another object.
A function defined to be part of an object in C++.
model of computation
A graphical connection between ports in vem.
A data type in C++ consisting of members and methods. These members and methods may be private, protected, or public. If they are private, they can only be accessed by methods defined in the object. If they are protected, then they can also be accessed by methods in derived classes. If they are public, then they can be accessed by any C++ code.
A design database developed by the CAD Group at U. C. Berkeley. Oct is used to store graphical representations of Ptolemy applications.
A collection of CAD tools based on the oct database. Some programs from the octtools distribution are used within Ptolemy.
A facet that contains a library of icons.
The initial value of a state.
A datum (e.g. a floating-point value) communicated between blocks.
The program that translates stars written in the Thor domain to C++.
The Ptolemy interactive graphical interface. Pigi is implemented as a shell script that starts vem and pigiRpc.
The program that forms the core of the Ptolemy graphical user interface. PigiRpc communicates with vem via a remote procedure call interface. It is mainly responsible for handling Ptolemy-specific commands from vem and translating oct representations of Ptolemy systems into a form executable by the Ptolemy kernel.
A class in the Ptolemy kernel that serves as a repository for used particles of any particular types. When new particles of the appropriate type are needed, they are taken from the Plasma, if possible, thus avoiding memory allocation.
A simulation domain based on the process networks computational model. Each star forms a process under this domain.
An input or output of a star or galaxy.
The base class in the Ptolemy kernel for all ports.
A textual, interactive command interpreter for Ptolemy. As the name implies, ptcl is based on Tcl.
(1) A schema language used to define stars in Ptolemy. (2) The program that translates stars written in the ptlang language to C++.
A program to play sound on the workstation speaker.
An environment variable with value equal to the name of the directory in which the Ptolemy system is installed.
A design environment that supports simultaneous mixtures of different models of computation. Ptolemy has been developed at the University of California at Berkeley. The Ptolemy design environment is named after the second century Greek astronomer, mathematician, and geographer.
A plotting program used by several standard Ptolemy stars.
The actual time (cf. simulated time).
Register-transfer level description of digital systems. This kind of description is used by the Thor domain.
An object associated with a domain that determines the order of execution of blocks within the domain. Domains may have multiple schedulers.
A block diagram.
A simulation domain using the synchronous dataflow model of computation.
(1) A functional language developed by Paul Hilfinger at U. C. Berkeley for specifying signal processing systems. It is used primarily as input for VLSI synthesis tools. (2) A code generation domain in Ptolemy that synthesizes Silage code and uses the synchronous dataflow model of computation.
The execution of a system specification (a Ptolemy block diagram) from within the Ptolemy process (i.e., without generating code and spawning a new process to execute that code).
In vem, an invisible grid defining the points at which graphical objects can have endpoints or corners.
An atomic (indivisible) unit of computation in a Ptolemy application. Every Ptolemy simulation ultimately consists of executing the methods of the stars used to define the simulation.
The base class in the Ptolemy kernel for all stars.
A member of a block that stores data values from one invocation of the block to the next.
The base class in the Ptolemy kernel for all states.
Within a timed domain, the time at which a simulation halts.
An object that manages the execution of a simulation or code generation process. Thus, for example, in code generation, the target would be responsible for compiling the generated code and spawning the process to execute that code, if desired.
The base class in the kernel for all targets.
Tool command language, a textual, interpreted language developed by John Ousterhout at U.C. Berkeley. Tcl is embedded in both pigi and ptcl.
A register transfer level digital hardware simulator from Stanford University. Thor is incorporated as a domain within Ptolemy.
A real number associated with a particle in timed domains that indicates the point in simulated time at which the particle is valid.
An X windows toolkit for Tcl. Tk is embedded in pigi, which uses it extensively. The interactive sliders, buttons, and plotting capabilities of pigi are implemented in Tcl/Tk.
An experimental front-end to Ptolemy that replaces vem. It is a Tk interface to schematics stored as oct facets. It executes universes by calling ptcl to evaluate the ptcl description of the universe.
A unit of data in a dataflow model of computation. Tokens are implemented as particles in Ptolemy.
A graphical development environment for Ptolemy that is implemented in Itcl.
An entire Ptolemy application.
The Utah Raster Toolkit for image and video processing. It is used by the image processing stars in the synchronous dataflow domain. The multidimensional synchronous dataflow domain treats images as matrices and does not use the Utah Raster Toolkit.
A graphical editor for objects stored under oct. The vem schematic capture interface is part of the octtools distribution from U. C. Berkeley, and forms a significant part of pigi.
The VHSIC hardware description language, a standardized language for specifying hardware designs at multiple levels of abstraction.
A code generation domain for functional modeling of hardware. This domain synthesizes a system description in VHDL.
A code generation domain for behavioral modeling of hardware. This domain synthesizes a system description in VHDL
A star in a particular domain that internally contains a galaxy in another domain.