Home
Altair Accelerator Administrator Guide
Configure and manage the use of Accelerator after it is installed.
Backwards Compatibility and Migrating from Previous Versions
This chapter provides information about deprecated features that are still supported. This information is provided should you see older commands in use after a software upgrade or migrating to a newer Accelerator.
Pre and Post Conditions

Welcome
What's New
View new features for Accelerator 2025.1.0.
Accelerator Overview
Discover the available Altair Accelerator guides.
Accelerator Tutorials
Discover Accelerator functionality with interactive tutorials.
Altair Accelerator User Guide
Basic tasks in Accelerator, including submitting jobs, tracking job information, and analyzing and solving common problems.
Altair Accelerator Administrator Guide
Configure and manage the use of Accelerator after it is installed.
- Use Accelerator Help
  Accelerator documentation is available in HTML and PDF format.
- Accelerator Quick Start
  Accelerator has two main commands, nc and ncmgr.
- Command Line Interface
- Quick Reference
- Accelerator Server and System Customization
- Start and Stop Accelerator
- Job Management
- Log Files
- Database
  Accelerator stores historical information about jobs in a relational database. As of version 2015.09, the database is fully integrated and managed as part of Accelerator. This section provides an overview of the components that run and manage the database.
- FairShare
- Jobclasses
- Preemption
  Preemption is the process of reserving or revoking resources from other jobs in order to help "important jobs" finish quickly.
- 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.
- Resource Management with RDS
  This is a usage guide for the Resource Data Service (RDS), an alternative service for managing License resources and License-first scheduling in Accelerator.
- Configure Container Integration
- Streaming Data Service
  The Streaming Data Service (SDS) publishes a time series data stream that can be consumed by existing Kafka systems and compatible reporting tools to monitor VOV projects.
- 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.
- Directories and Files
- Alerts and Notifications
- System Tasks
- Upgrade Accelerator
  This section provides instructions to change the software version on which Accelerator runs.
- Storage Aware Scheduling
  This daemon vovfilerd replaces older daemons like vovisilond, vovnetappd and vovregulatord. Also the utility vovfiler_setup is no longer needed. The visualization of the filer information is now done either via the vovfilerd.cgi page or via the utility vovfilerdgui.
- Frequently Asked Questions and Troubleshooting Tips
- Backwards Compatibility and Migrating from Previous Versions
  This chapter provides information about deprecated features that are still supported. This information is provided should you see older commands in use after a software upgrade or migrating to a newer Accelerator.
  - Tasker Resources
    The resources offered by a tasker are represented by a space-separated list of tokens. Resources can be explicit or symbolic.
  - Pre and Post Conditions
  - Configure FairShare via the policy.tcl File
  - Migration of Preemption from 2013.03 and Prior Versions
  - Convert Old VovPreemptPolicy into VovPreemptRule
  - FairShare Groups

Pre and Post Conditions

The execution of Pre and Post conditions based on the environment definition have been deprecated as of version 8.2.0. For current information, refer to Pre-Command and Post-Command Job Conditions. The information provided in this section describes behavior that is supported for backward compatibility.

As part of the environment definition, two scripts can be prepared to take care of pre- and post-conditions on a job-by-job basis. These scripts are called NameOfEnv.pre.tcl and NameOfEnv.post.tcl.