Next: , Previous: Configurations, Up: Top



3 Auto-pilot Command Line Options

Auto-pilot processes and executes configuration files that describe a series of benchmarks. Post processing tools such as Getstats and Graphit are used to read the results that it produces. Auto-pilot has a rather simple command line structure. The simplest usage is simply auto-pilot config.ap, which reads config.ap and executes it. config.ap can also be a saved Auto-pilot checkpoint.

The following command line options are supported:

-d
Run the configuration in debug mode, printing out the PC and the source line before execution. Add extra -d options to produce more debugging (currently the highest debugging level is 4).
-h
Display the manual page.
-n
Don't actually run any programs or predicates, just pretend that they all succeed. This can be used to check the syntax of your Auto-pilot configuration.
--[no]status
By default Auto-pilot creates status.out that describes the what tests have started and finished (actually the file is named after the environment variable APSTATUS). If --nostatus is passed, then this file is not created.