Home
Altair Accelerator Administrator Guide
Configure and manage the use of Accelerator after it is installed.
Directories and Files
Working Directories and Equivalences
The directory where the top level job is executed must be visible and accessible to both the Accelerator vovserver, which is running on UNIX, and the remote Windows NT machine.

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
  - Working Directories and Equivalences
    The directory where the top level job is executed must be visible and accessible to both the Accelerator vovserver, which is running on UNIX, and the remote Windows NT machine.
  - Canonical and Logical File Names
    VOV clients and server exchange dependency information by using file names; each file needs a single name that is valid on both the client and the server.
  - Define Equivalences for File Names
    There are multiple methods to define the equivalences used to compute the canonical names of files and directories.
  - Historical Job Data Files
    vovserver creates a CSV (comma-separated variable) file containing data about each job that ran. This format may be directly imported into many spreadsheet and database programs. The jobs files are stored in the jobs subdirectory of the vovserver configuration directory.
  - Journals
    The vovserver records all events in a journal file that resides in a the subdirectory journals/ of the server configuration directory.
- 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.

View All Altair Accelerator Help

Working Directories and Equivalences

The directory where the top level job is executed must be visible and accessible to both the Accelerator vovserver, which is running on UNIX, and the remote Windows NT machine.

This is normally not a limitation, since there is always at least one directory that satisfies this requirement, the one of the Accelerator installation itself. Nothing prevents you from changing to any other directory as part of the job.

It is imperative that you explain to the Accelerator vovserver the naming equivalences between UNIX files and Windows NT files. Keeping up with our examples, the path to the Accelerator installation is /usr/local/rtda on UNIX and f:\rtda on Windows NT. This can be described in the file vnc.swd/equiv.tcl as:

# Fragment of vnc.swd/equiv.tcl
vtk_equivalence NCROOT /usr/local/rtda
vtk_equivalence NCROOT f:/rtda;  # Notice the forward slashes!!

where NCROOT is the "logical name" we want to use for both the directory /usr/local/rtda and /usr/local/rtda.

After you change the vnc.swd/equiv.tcl file, you must always do a full reset:

% ncmgr reset -full