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 project name is normally used to compute the number of the TCP port on which the vovserver listens for connections. This is done by hashing the project name into the port range 6200-6455, using the function vtk_port_number.
vovserver configuration parameter values may be changed in a running vovserver using the CLI, or prior to the starting the server via the policy.tcl file. An administator can configure the parameters in the running vovserver using the vovservermgr command or the vtk_server_config procedure.
The maximum number of clients - the combination of vovtaskers, user interfaces and proxies, that can be concurrently connected to a vovserver is limited by the number of file descriptors available.
As the server farm becomes larger and larger, it becomes useful to allow the vovserver to use multiple threads to handle the costly read-only services, such as listing sets of jobs or retrieving the complete list of taskers.
A VovId is a nine-digit string assigned by VOV to each object in the trace.
With the command vovautostart, on vovserver startup, scripts can be specified to execute automatically.
With the command vovautostop, on vovserver shutdown, scripts can be specified to execute automatically.
The daemon vovtriggerd taps the event stream and executes commands that are based on selected events.
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.
View All Altair Accelerator Help