The solver name should respect the guidelines given in the rules of the SMT-competition (derived solver, wrapper solver, ...)
The contributors will not be contacted except if they are also in contacts
Must contain a minimum of 1 items
Contributors in the developement of the solver. If only name is provided,
it can be directly given. UTF8 can be used.
"Jane Smith"
{
"name": "Jane Smith",
"website": "http://jane.smith.name"
}
Must be at least 1 characters long
Must be at most 2083 characters long
Used if the organizers need to discuss the submission
Must contain a minimum of 1 items
Name and valide email "name <email>"
"Jane Smith <jane.smith@edu.world>"
The url must be record from http://zenodo.org for the final submission. So
the hash is not required because zenodo records are immutable.
The hash can be used if you want to be sure of the archive used during the
test runs.
The url should be valid at the time of submission and during all the competition. The url should be at zenodo for the final submission.
Must be at least 1 characters long
Must be at most 2083 characters long
Fields command given in participations have priority over this one
Command with its arguments to run after the extraction of the archive.
The path are relative to the directory in which the archive is unpacked.
The input file is added at the end of the list of arguments.
Two forms are accepted, using a dictionnary (separate binary and arguments) or a list ([binary]+arguments).
The command run in the given environment
https://gitlab.com/sosy-lab/benchmarking/competition-scripts/#computing-environment-on-competition-machines
[
"relative_cmd",
"default_command_line"
]
{
"arguments": [
"default_command_line"
],
"binary": "relative_cmd"
}
Used only for internal tests
Must be at least 1 characters long
Must be at most 2083 characters long
Must be at least 1 characters long
Must be at most 2083 characters long
tracks: select the participation tracks
divisions: add all the logics of those divisions in each track
logics: add all the specified logics in each selected track it exists
aws_repository should be used only in conjunction with Cloud and Parallel track
archive and command should not be used with Cloud and Parallel track. They superseed the one given at the root.
Can be a list of logics or a regexp matched on all the existing logics
No Additional ItemsThe url must be record from http://zenodo.org for the final submission. So
the hash is not required because zenodo records are immutable.
The hash can be used if you want to be sure of the archive used during the
test runs.
The url should be valid at the time of submission and during all the competition. The url should be at zenodo for the final submission.
Must be at least 1 characters long
Must be at most 2083 characters long
Command with its arguments to run after the extraction of the archive.
The path are relative to the directory in which the archive is unpacked.
The input file is added at the end of the list of arguments.
Two forms are accepted, using a dictionnary (separate binary and arguments) or a list ([binary]+arguments).
The command run in the given environment
https://gitlab.com/sosy-lab/benchmarking/competition-scripts/#computing-environment-on-competition-machines
[
"relative_cmd",
"default_command_line"
]
{
"arguments": [
"default_command_line"
],
"binary": "relative_cmd"
}
Used only for internal tests
Must be set for the final version of the submission. An archive on zenodo is needed in this case.