Dear Johannes,
* what do you recommend for --name? (how many lines, words, characters) (e.g., can/should it contain precise version information?)
That's up to you. I think including version information would be useful. I'll probably use something like "LoAT v0.2.0" or "LoAT $SHORT_GIT_SHA" for my tool.
* I can just ignore timeout? (and expect it to be 60 seconds?)
Yes, you can do that.
* how many cores can I expect to use? RAM?
4 Cores, 20.345 MiB RAM.
* what are the possible values for $category? (they are names of top-level directories in TPDB?
Yes, for most categories, it'll just be the name of the top-level directory. We just have to think about an alternative for categories that do not have their own benchmark set (e.g., parallel rewriting).
e.g., SRS_Standard, SRS_Relative ? Could you provide empty files in https://github.com/TermCOMP/registration ?)
Please just create the missing files before creating a pull request.
* How do I know whether it's certified or not?
Good question. I didn't test with certification yet. I guess an additional argument '--cert' would do. Could you provide a (containerized) solver with support for certification (via '--cert')? Then I can start testing with certification and figure out the details.
* $benchmark : will it have a specific extension (.ari)?
Yes, .ari for all TRS/SRS/Transition System categories. Best Florian