Home
Altair FlowTracer Developer Guide
Runtime Change Propagation Control
The patented technique of Runtime Change Propagation Control (RCPC) provides the ability to stop the propagation of insignificant changes through the flow.
Triggers on Files

Welcome
What's New
View new features for FlowTracer 2025.1.0.
FlowTracer Overview
An advanced mission critical dependency management platform for developing and executing flows.
FlowTracer Tutorials
Discover FlowTracer functionality with interactive tutorials.
Altair FlowTracer User Guide
FlowTracer is a complete system to create, manage, and execute design flows.
Altair FlowTracer Administrator Guide
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.
Altair FlowTracer Developer Guide
- FlowTracer Roles
  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.
- Environment Management
  To ensure the correct and repeatable behavior of the tools, the environment must be controlled. This chapter explains how VOV supports multiple reusable environments.
- Execute Jobs From the Command Line
- Flowbuilding
  The trace is built using a combination of techniques.
- Flow Description Language (FDL)
- Tool Integration
- Integrate Difficult Tools
- Runtime Change Propagation Control
  The patented technique of Runtime Change Propagation Control (RCPC) provides the ability to stop the propagation of insignificant changes through the flow.
- Flow Library
  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.
- Files, Equivalences, Exclusions
  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.
- Makefile Conversion
- Advanced Tasker Topics
- Resource Management
  The Resource Map Set represents the collection of resource maps that have been assigned to a project and the constraints associated with such resources.
- CGI Interface
- Events
  Every change in the trace is recorded as an event, which is then sent to all clients that subscribe to them.
- Miscellaneous

View All Altair Accelerator Help

Triggers on Files

There are two possible triggers that can be set that depend on a file's timestamp:

Run Trigger: when this trigger is set, and the timestamp of the file changes, the downcone of the file is automatically run.
Stop Trigger: when this trigger is set, and the timestamp of the file changes, all running jobs in the downcone of the file are automatically stopped.

If both triggers are set, first the jobs are stopped, then the downcone is scheduled. The run is always performed at NORMAL priority.

Set the Triggers

The simplest way to set triggers in FDL is to use the options -trigger,run and -trigger,stop in the I call that registers the file as input.

# Example of setting a trigger flag in FDL
J vw cp aa bb
I -trigger,run aa

Other Ways to Change the Triggers

Triggers on a file can be set using the vtk API.

# Example of manipulation of both trigger flags using the VTK API.
set placeId [vtk_place_find "FILE" "aa"]
vtk_place_get $placeId placeInfo

set placeInfo(trigger,run)  1
set placeInfo(trigger,stop) 1

vtk_place_set $placeId placeInfo