Altair FlowTracer 2024.1.0
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.
View new features for FlowTracer 2024.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.
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.
This section explains how to set up a UNIX user's shell environment to have a proper context for the user to run installed Altair Accelerator programs from the command line. The programs that are run from the command line are called the CLI commands.
This section explains how to set up a Window user's command prompt environment to have the proper context for the user to run installed Altair Accelerator programs from the command line. The programs that are run from the command line are called the CLI commands.
FlowTracer documentation is available in HTML and PDF format.
When a project is created, a server working directory (.swd directory) is created to hold configuration and state information about the project.
VOV issues an "alert" when an event requires attention. An alert can range from information that does not require action to an urgent fault that requires immediate action.
The VOV security model consists of assigning a Security Code to each client or client group (VovUser Group) and granting the permission to execute critical tasks only to clients with the appropriate security level.
A tasker is a VOV client that provides computing resources, specifically CPU cycles, to the vovserver.
FlowTracer can be used also as a front end to an existing batch processing system (BPS), for example, Accelerator, LSF, SGE, SGEEE, etc.
If a server crashes suddenly, VOV has the capability to start a replacement server on a pre-selected host. This capability requires that the pre-selected host is configured as a failover server.
FlowTracer now supports a "multi-user" mode of operation, as a Beta feature. In the multi-user mode, many different users can share the same project, in terms of modifying a flow as well as running different compoments of the flow.
If you use SSH to login onto certain machines in your LAN that you want to use as taskers, you need to setup SSH so that it will not ask for your password.
Each computer has its own clock. Clocks on different computers in the same network might not be synchronized. The system administrator should keep all clocks in the network synchronized.
The file system that contains the design files may reside on a machine that is not the same as the one where the vovserver is running. The clocks in the two machines may be different, resulting in an offset. These offsets can be easily avoided. Here we show what can be done to work with an unsynchronized network.
Before you can use NFS, be it as server or client, you must make sure your kernel has NFS support compiled in.
When you request a run, the FlowTracer server checks the timestamp of all primary inputs in the upcone of the target.
The utility vovcleanup is used to clean old log files from /tmp and from the server working directory.
Both the vovconsole's main GUI and its Node Editor GUI can be customized with the gui.tcl file.
Annotations are text strings which may be attached to VOV objects. These are typically used to provide additional information about objects in the project's graph. The text must be less than 32k characters.
If you use DesignSync, you want to ignore links to the DesignSync cache.
View All Altair Accelerator Help