2025.1.0
This manual provides information about managing a VOV project, including starting the server and connecting computing resources such as computers and licenses.
View new features for VOV Subsystem 2025.1.0.
Discover the workspace, licensing and installation, and training.
Discover VOV Subsystem functionality with interactive tutorials.
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.
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.
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.
To connect to a VOV project, get a list of the projects with vovproject list, and then enable the selected 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.
A thin client (VOV protocol) runs on a machine that does not have access to the SWD directory of the vovserver.
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.
The vovserver implements several protections against denial-of-service (DoS) attacks. One of these is the detection of clients that use a relatively large share of the server time. These clients are considered service hogs, and their subsequent service requests can be ignored for up to 3 seconds.
VovUserGroups are an access control mechanism. They are internally-defined groups of users that are utilized to make the job of allocating access easier within Altair Accelerator tools.
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.
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.
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.
This document is a collection of techniques that have proven to be useful when applying FlowTracer in Electronic Design Automation.
View All Altair Accelerator Help
