Star Exec Test

From Termination-Portal.org
Revision as of 13:24, 24 June 2012 by J.waldmann (talk | contribs) (Created page with "This is an collection of notes that I (JW) am making while using the Star Exec service. The plan is to submit some benchmarks (from TPDB), submit some solvers (initially, my o...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

This is an collection of notes that I (JW) am making while using the Star Exec service. The plan is to submit some benchmarks (from TPDB), submit some solvers (initially, my own Matchbox because that's easiest for me to modify if necessary), and run some jobs. Ordering of notes is mostly by time (during that process), and not by importance.

  • password is transmitted via http (not https)?
  • white on black lettering is hurting my eyes. Please make it black on white.
  • "report a bug" equals "mail to developer". I would much prefer a bug tracker that is world-readable, to avoid double reports, and be able to follow progress.

Defining and uploading a benchmark collection

  • order of user guide is inverted (I am doing: 1. define benchmark type, 2. upload benchmark, 3. upload solver)
  • when adding a benchmark type, platform asks for name/description/processor. I don't want a processor, but it seems I am required to do so. Platform could provide a default processor that just says "starexec-valid=true".
  • definining the benchmark type (SRS_Standard) seems OK.
  • the "upload benchmarks" in the space explorer is somewhat hidden (need to expand the "root" symbol in the left bar). I upload a .tar.gz file that corresponds to the SRS_Standard subdir of tpdb-8.0.6. There are several import options, I keep the defaults. Import seems OK, I see the directory structure in the left bar.