Quick Reference Guide


This a quick reference to help you accomplish basic tasks in StarExec. For a more extensive guide, see the User Guide. This guide is organized by the method one uses to accomplish tasks.

The main page on StarExec is the Space Explorer. This page is accessed by selecting the Spaces tab in the upper right and selecting Explore in the dropdown menu. The left hand side of the Space Explorer is a representation of the space hierarchy that you have access to. When you click on a space on the space tree, you can see information about it on the right hand side.

Space Information All of the following are represented in tables with rows that can be clicked on for additional information:

  • Jobs
  • Solvers
  • Benchmarks
  • Users
  • Subspaces

Dragging and Dropping All drags are from the right hand side of the Space Explorer page to the left

Drag and Drop uses

  • Add benchmarks, users, or solvers to a space by dragging them to the space in the space explorer tree
  • Delete a space, benchmark or user by dragging to a trash can icon that appears near the top of the screen

Action buttons At the bottom of the right hand side

  • create job - this will take you to a sequence of pages where you enter job parameters, select benchmarks and solvers, and submit the job
  • add subspace to the currently selected space
  • upload benchmarks - typically you will be creating a space hierarchy corresponding to the directory structure of a zipped directory of benchmarks
  • upload and download xml representations of space hierarchies - an upload will create the space hierarchy using already existing benchmarks and solvers.
  • edit space - edit basic information about the space
  • upload solver
    • upload a compressed directory that contains at least one configuration(run script) that will tell starexec how to run your solver on the execution nodes
    • configuration file name must have the prefix "starexec_run_". Everything after the prefix will be the name of the configuration within starexec
    • configurations must be placed in a /bin folder in the top level directory of the uploaded archive
    • Your script has access to a few different arguments and environmental variables, the most important being $1, the absolute path the the benchmark input file