2025.1.0
View new features for FlowTracer 2025.1.0.
An advanced mission critical dependency management platform for developing and executing flows.
Discover FlowTracer functionality with interactive tutorials.
FlowTracer is a complete system to create, manage, and execute design flows.
This manual is aimed at the person who will be the administrator for FlowTracer. This person will be responsible for configuring the network resources, setting up the licensing, and establishing security and access rules for the system.
When using FlowTracer in large deployments, three main roles emerge: Administrator, Developer and User. In smaller organizations, a given person may have multiple roles, but the duties of each role still exist.
To ensure the correct and repeatable behavior of the tools, the environment must be controlled. This chapter explains how VOV supports multiple reusable environments.
The trace is built using a combination of techniques.
Add annotations to the most recently declared node.
Declare an artificial dependency between two jobs.
Set the database for subsequent files.
Declare an input dependency.
Execute a code fragment in a directory.
Declare a job and use the capsule to compute IO's (see also T and P).
Set the legal exit values for subsequent jobs.
Set the jobname.
Declare an output dependency. All jobs require at least one output to be valid.
Add a property to the most recently mentioned object.
Declare the parallelism between two or more tasks and subflows (See also TASK and SERIAL).
Declare a job to be executed periodically (see also T and J).
Set the priority to be used for the subsequent jobs.
Set resources for subsequent jobs.
Precise definition of a set of jobs.
Append jobs to a set.
Serially order a number of tasks and subflows (See also TASK and PARALLEL).
Get the next argument from argv
Start running jobs -- rarely used.
Declare a job (see also PJ and J).
Declare a job with no specific dependencies (see also SERIAL and PARALLEL).
Set the expected duration for subsequent jobs.
Set the zippable flag for a list of files.
In FDL there are two procedures that can be used to add a job to a flow: T and J. Which one should you use?
The patented technique of Runtime Change Propagation Control (RCPC) provides the ability to stop the propagation of insignificant changes through the flow.
FlowTracer captures your design in design flows described by Flow.tcl files. The Flow Library is meant to help users locate and deploy instances of packaged flows bound to their specific design data.
The files used in a project reside in one or more directories spread all around your filesystems. Each logical name defined in the equiv.tcl file implicitly declares the root of a workspace. You can browse the workspaces using the browser interface.
The Resource Map Set represents the collection of resource maps that have been assigned to a project and the constraints associated with such resources.
Every change in the trace is recorded as an event, which is then sent to all clients that subscribe to them.
View All Altair Accelerator Help
