Home
Altair Accelerator User Guide
Basic tasks in Accelerator, including submitting jobs, tracking job information, and analyzing and solving common problems.
Running a Job
This section summarizes how to submit and run a job.
View Job Progress and Results
Submitted Job Information Display
By default, nc run provides information when a job is submitted.

Welcome
What's New
View new features for Accelerator 2025.1.2.
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.
- 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
- User Shell Setup
  To set up your user shell with Accelerator you need to know where the Altair Accelerator software has been installed.
- Running a Job
  This section summarizes how to submit and run a job.
  - Submit Jobs
  - View Job Progress and Results
    - Submitted Job Information Display
      By default, nc run provides information when a job is submitted.
    - Get Job Information
      The nc info command gives information about a job.
    - Get Detailed Information about a Job
      The command nc displays information about a job.
    - Graphical View of Job Progress and Results
  - Manage Jobs
    Accelerator provides several commands of job controls, including wait, stop, cleaning and debugging.
  - Rerun Jobs
    The nc rerun command initiates scheduling and executing jobs that are already in the server database.
- Job Management
- Schedule Job Submission
- Modify Running Jobs
- FairShare Groups
- Job Placement Policies
- Clean Up Log Files
  All log files are normally stored under the subdirectory ./vnc_logs. To remove all obsolete log files in the current working directory, use the nc clean command.
- Debug Jobs without Running Accelerator
  On occasion, jobs that run successfully outside of Accelerator fail when run through Accelerator. When this occurs, mostly likely the setups are not the same: the environment, inputs or other parameters may be different, a misconfiguration or there is a problem with NFS.
- Job Runtime - Monitor and Profile
  When a job is running through a vovtasker, the tasker automatically monitors RAM and CPU utilization of the job, including all of its children.
- Monitor the Workload
- Statistical Information about Resources and Jobs
  Reports provide statistical information about all the jobs that are run during a specified time and the usage of the resources that run jobs. The resources include CPU time, licenses, memory and more.
- Environment Control
  Setting the environment is critical for correct job execution. Accelerator provides two methods to control the execution environment.
- Job Resources
  Some jobs may require a specific platform or operating system (OS) to run. As Accelerator automatically lists platform/OS as a tasker resources, the task of finding the right host to execute a job is easy: specify the required platform/OS as part of the job resource requirements.
- Advanced Information
- Frequently Asked Questions and Troubleshooting Tips
- Deprecated Commands
  This section lists the recently deprecated and obsoleted Accelerator commands and options, and the corresponding current commands and options.
- LSF Emulation
  This document is intended for those who have been using the Platform LSF batch system and are now moving over to the Accelerator system.
Altair Accelerator Administrator Guide
Configure and manage the use of Accelerator after it is installed.

View All Altair Accelerator Help

Submitted Job Information Display

By default, nc run provides information when a job is submitted.

The following example shows information that is output with a simple command. The amount of information displayed is determined by the verbose level. In the following example, verbose is at the default level of 4.

Note: The environment is set with a snapshot.

% nc run sleep 10
Fairshare= /time/users.andrea
Resources= macosx CPUS/1 RAM/500
Env = SNAPSHOT(vnclogs/snp/joe/macosx/env27227.env)
Command  = vw sleep 10
Logfile  = vnc_logs/20130220/104930.33137
JobId    = 024609542

FairShare: the FairShare ranking of this job.
Resources: the resources used to run this job: the machine, number of CPUs, amount of RAM, and so on.
Env: the environment in which the job was submitted.
Command: the command that was used to execute this job.
Logfile: the name of the logfile.
JobID: the unique identifier of this job.

The amount of information can be changed by setting the verbose level by using the -v option, such as

nc run sleep 10 -v 2

.


Verbose Level	Effect
0	Silent: no output is generated
1	Only the job ID is displayed
4	Default level
9	Very verbose