Warning (!)

Wiki Cloud Migration Deadline


On January 8th, 2024 the University of Iowa Wiki hosted at https://wiki.uiowa.edu will be shut down permanently. If you would like to continue using Confluence (Wiki) in the Cloud, you will need to request licenses by filling out this Workflow form if you haven't done so already.

For more information and other options for your content, please visit the Wiki Service Change Options and FAQs page. Your content from https://wiki.uiowa.edu will be available for migration upon request for two years (until 1/8/2026).

Child pages
  • User Guide

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Post-processors are a mechanism for retrieving additional information ("attributes") from a job pair's output. The process program will be given run with three command-line arguments: the name of a file containing a job pair's combined stdout/stderr, as well as the path to the benchmark, and the path to the directory for any additional output files.  They are then expected to produce textual output in a StarExec-defined format. When the job completes, StarExec scans the post-processors output and adds attributes for the job pair run to its database. This is useful if you wish to extract and collect additional information about a job pair run that is community-dependent.  Any additional output files which the postprocessor write to the output files directory (third command-line argument) will also be copied back to StarExec and saved with the data from the job pair.

Post-processors are defined by community leaders and are global across all communities in StarExec. For example, if a SAT community leader creates a post-processor, users of SMT and TPTP can see and use the processor when creating new jobs.