Tasker ID
Each tasker is an object in the VOV database and therefore it has its own VovId.
- vovtaskermgr (for command line operation)
- vtk_job_control to stop, suspend, resume jobs
- vtk_tasker_reserve to reserve a tasker.
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.
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.
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.
When a job becomes eligible to run, VOV places it on the fastest vovtasker host which offers all the resources requested when the job was submitted. The Tasker Compatibility page in the web browser UI shows details of a job's compatibility with each vovtasker machine. You can use this page to understand why a job seems stuck.
The taskers.tcl file describes the taskers for a project.
There are many options that can be used with vtk_tasker_define and vtk_tasker_set_default.
The main way to start, configure, and stop the taskers is with the vovtaskermgr command. This command acts relative to the VOV-project enabled in the shell where it is issued.
Each tasker is an object in the VOV database and therefore it has its own VovId.
A tasker is characterized by several attributes. These attributes are controllable by means of the command line arguments to the vovtasker binary as well as by means of the procedure vtk_tasker_define in the taskers.tcl configuration file for a VOV project.
Upon startup, the vovtasker computes the raw power of the CPU on the current host by timing a known test routine consisting of a balanced mix of integer, double and string operations. The power is inversely proportional to the time it takes to execute the test routine.
To monitor the activity of the taskers, use either vsm from the CLI, or click Console > Vov Monitor from the GUI.
The resources offered by a tasker are represented by a space-separated list of tokens. Resources can be explicit or symbolic.
Time-variant taskers resources can be configured using Tcl. Any procedure can be defined in the namespace VovResources
and then used to compute the resource list.
This section describes the predefined procedures that can be used to characterize the taskers in your farm in a time-variant fashion. To use these procedures, you have to use them as resources for a tasker.
The program vovtaskerowner gives the owner of a machine the control on the tasker running on such machine.
On UNIX, the script vovtaskerstartup is used to start a tasker on a remote machine.
When you no longer need a tasker that you started manually and that is running in the foreground, stop it with Ctrl-C
.
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.
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.
A tasker is a VOV client that provides computing resources, specifically CPU cycles, to the vovserver.
Each tasker is an object in the VOV database and therefore it has its own VovId.
Each tasker is an object in the VOV database and therefore it has its own VovId.
Copyright (c) 1994-2023. Altair Engineering, Inc. All Rights Reserved. Contains trade secrets of Altair Engineering, Inc. Copyright notice does not imply publication.
Intellectual Property Rights Notice | Technical Support | Cookie Consent