Home
VOV Subsystem Administrator Guide
This manual provides information about managing a VOV project, including starting the server and connecting computing resources such as computers and licenses.
Tasker Policies
Stop Taskers
When you no longer need a tasker that you started manually and that is running in the foreground, stop it with Ctrl-C.

Welcome
What's New
View new features for VOV Subsystem 2025.1.2.
Overview
Discover the workspace, licensing and installation, and training.
VOV Subsystem Tutorials
Discover VOV Subsystem functionality with interactive tutorials.
VOV Subsystem Administrator Guide
This manual provides information about managing a VOV project, including starting the server and connecting computing resources such as computers and licenses.
- Client/Server Architecture
  All of Altair Accelerator's products are based on a client/server architecture to support concurrent activities, team coordination, distributed data management, and distributed processing. The program vovserver runs in the background as a service to implement the main product features. It is the server.
- VOV Projects
  A "project" is a named collection of jobs, together with all the files that are used and produced by those jobs. The contents of VOV projects can be custom organized.
- VOV Registry
  The VOV Registry contains the list of all projects known to an installation of Altair Accelerator software. The registry is used by the vovproject command, and stores metadata such as the host machine and port number of a project.
- Get Started
- Start and Configure the Server
- Connect to a Project
- Stop the Server
- Recovery and Redundancy
- 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.
- Taskers
  A tasker is a VOV client that provides computing resources, specifically CPU cycles, to the vovserver.
- Tasker Policies
  - Tasker Reservations
  - Tasker Owner
    The program vovtaskerowner gives the owner of a machine the control on the tasker running on such machine.
  - Taskers: Mixed Windows NT and UNIX Environment
    It is common to run VOV in a mixed network of UNIX and Windows NT workstations. Following is a set of guidelines to facilitate the deployment in such a network.
  - Start a Remote UNIX TASKER Details
    On UNIX, the script vovtaskerstartup is used to start a tasker on a remote machine.
  - Stop Taskers
    When you no longer need a tasker that you started manually and that is running in the foreground, stop it with Ctrl-C.
  - Taskers Running as Root: Security Implications
  - vtk_job_control
    From Tcl, you can control both the taskers and the jobs running on the remote taskers with the procedure vtk_job_control.
- Interfaces to Accelerator, SGE, LSF, and Others
  FlowTracer can be used also as a front end to an existing batch processing system (BPS), for example, Accelerator, LSF, SGE, SGEEE, etc.
- Advanced Tasker Topics
- Resource Management
  Altair Accelerator includes a subsystem for managing computing resources. This allows the design team to factor in various constraints regarding hardware and software resources, as well as site policy constraints.
- IT Administrator Topics
VOV Subsystem Reference Guide
EDA Tool Integration Guide
This document is a collection of techniques that have proven to be useful when applying FlowTracer in Electronic Design Automation.

Stop Taskers

When you no longer need a tasker that you started manually and that is running in the foreground, stop it with Ctrl-C.

Background taskers, and taskers started with vovtaskermgr, can be shut down forcibly with vovkill pid or more cleanly with

% vovtaskermgr stop
% vovtaskermgr stop <tasker_name>

Clean Up

Occasionally, the taskers leave some files in /usr/tmp. You can use vovcleanup -host to browse for files left over by the taskers.

% vovcleanup -host