Home
Altair FlowTracer Developer Guide
Resource Management
The Resource Map Set represents the collection of resource maps that have been assigned to a project and the constraints associated with such resources.
Delete Resources
To delete a resource map, use the Tcl procedure vtk_resourcemap_delete in vovsh. Resource maps may be deleted by ID or by name.

Welcome
What's New
View new features for FlowTracer 2025.1.2.
FlowTracer Overview
An advanced mission critical dependency management platform for developing and executing flows.
FlowTracer Tutorials
Discover FlowTracer functionality with interactive tutorials.
Altair FlowTracer User Guide
FlowTracer is a complete system to create, manage, and execute design flows.
Altair FlowTracer Administrator Guide
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.
Altair FlowTracer Developer Guide
- FlowTracer Roles
  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.
- Environment Management
  To ensure the correct and repeatable behavior of the tools, the environment must be controlled. This chapter explains how VOV supports multiple reusable environments.
- Execute Jobs From the Command Line
- Flowbuilding
  The trace is built using a combination of techniques.
- Flow Description Language (FDL)
- Tool Integration
- Integrate Difficult Tools
- Runtime Change Propagation Control
  The patented technique of Runtime Change Propagation Control (RCPC) provides the ability to stop the propagation of insignificant changes through the flow.
- Flow Library
  FlowTracer captures your design in design flows described by Flow.tcl files. The Flow Library is meant to help users locate and deploy instances of packaged flows bound to their specific design data.
- 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.
- Makefile Conversion
- Advanced Tasker Topics
- Resource Management
  The Resource Map Set represents the collection of resource maps that have been assigned to a project and the constraints associated with such resources.
  - Resource Mapping
    As the vovservers determines which tasker is most suited to execute a particular job, it performs a mapping of the job resources, followed by a matching of the mapped resources.
  - Resource Reservation
    Resource reservation ensure that specific groups always has access to licenses, regardless of the number of jobs.
  - Delete Resources
    To delete a resource map, use the Tcl procedure vtk_resourcemap_delete in vovsh. Resource maps may be deleted by ID or by name.
  - Resource Daemon Configuration
  - vovresourcemgr
    vovresourcemgr is a utility for managing VOV resource maps. It may be used to create, modify, forget, and reserve resource maps.
  - Policies and Resources
    You can define site-specific policies on how resources are allocated to various projects by creating a file called $VOVDIR/local/resources.tcl. This file contains the definition of a procedure called vtk_resources_policy_hook and can be used to limit the amount of resources assigned to a given project.
  - Add Resources
- CGI Interface
- Events
  Every change in the trace is recorded as an event, which is then sent to all clients that subscribe to them.
- Miscellaneous

Delete Resources

To delete a resource map, use the Tcl procedure vtk_resourcemap_delete in vovsh. Resource maps may be deleted by ID or by name.

For example:

# Delete a resource by name
vtk_resourcemap_delete License:dc_shell

# Delete a resource by id
vtk_resourcemap_forget 00023456

Resource maps are automatically deleted after they expire, as soon as no job is using the resource.

The License: resources that are maintained by vovresourced and by Allocator are created with relatively short (typ. 5m) expiration times, but these are intended to be several times the duration at which they are refreshed by the daemon from license in-use information.

Rarely, you may observe jobs where nc info or the browser UI will show waiting on INFO: being deleted. This is shown when a job is waiting on a resource map that is in the process of being deleted or expiring.