Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use originalFilename (?) in benchmark display and for comparisons #84

Open
jwaldmann opened this issue Jul 7, 2015 · 4 comments
Open

Comments

@jwaldmann
Copy link
Owner

there are several ways of denoting (indexing) a termination problem

  • starexec benchmark id (but for each upload of tpdb, problems will get fresh ids, so it cannot be used to compare 2015 and 2014 competitions, and older results (uibk) don't have these ids at all)
  • tpdb file name (tpdb promises to never overwrite files) (but some information has gone missing, e.g.
    SRS_Standard/Secret_06_SRS/5.xml is missing "jambox", see next item)
  • original file name (the old TPDB entries have that, e.g., /SRS/secret06/jambox/5.srs)

so, what's best? I guess

  • original filename if available,
  • else tpdb file name.
@jwaldmann
Copy link
Owner Author

@jwaldmann
Copy link
Owner Author

Plan: two (global) maps. Assume DOI = Int for now, but keep it abstract

  • toDOI :: BenchmarkID -> DOI
  • fromDOI :: DOI -> Text (human readable name, to be shown in tables)
    these maps will be read at startup, from files or DB (not from starexec)

@jwaldmann
Copy link
Owner Author

micro-steps: read benchmark names from space files: commit 668fca0 ,
introduce DOI type: commit 0f5b972,
build DOI resolver at startup 92c762d

@jwaldmann
Copy link
Owner Author

not nice but it works: commit cc84625 ,
for usage example see http://lists.lri.fr/pipermail/termtools/2015-August/001083.html
note that urls for benchmarks in table look like http://nfa.imn.htwk-leipzig.de/termcomp-2015/resolve/tpi:21729 and are being redirected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant