As in previous years submission is by uploading your solver to its
corresponding subspace of the 'CoCo 2024 tool submission' space. All
tool authors (as indicated on EasyChair) that are members of the
Confluence community on StarExec will be added to the spaces for
their tools. 

If you do not have a StarExec account (or are not a member of the
Confluence community) but need to submit, please register soon and
request membership in the Confluence community, so we can add you
to the space of your tool.

The easiest way to submit your solver to its space is to upload it
in a single archive containing the following files:

bin/  -- directory containing the executables needed by your solver
bin/my_tool
bin/starexec_run_default  -- the wrapper script that calls your tool
starexec_description.txt  -- a short description of your tool

Please note that the contents must not be contained in an additional
folder, that is, the archive needs to extract to bin/my_tool as
opposed to mytool/bin/my_tool.

Please do not add version numbers or years to the "solver name" field
when uploading the solver.

See

  https://www.starexec.org/starexec/secure/help.jsp?ref=/starexec/secure/add/solver.help

for more information on uploading solvers to StarExec.

If you registered for multiple categories and need to use your tool
with different configurations you can either add multiple
bin/starexec_run_config wrapper scripts or upload multiple solvers.
In any case please indicate in the description the intended category
for each solver/configuration.

For tools that team up with a certifier, you should no longer upload
the certifier yourself. Instead in the description of your tool and/or
configuration indicate the certified categories you want to participate
in (e.g. "TRS+CeTA", "COM+FORTify",..). In the certified categories it
is expected that your tool produces output, where the first line is the
answer (YES/NO/MAYBE) and the remaining lines contain the certificate.
For example:

YES/NO
... CPF3-output or FORTify-certificate ...

For tools that internally produce CPF2 certificates, we expect that
they run the corresponding converter to CPF3 themselves.
It is available at:
  
  http://cl-informatik.uibk.ac.at/isafor/cpf3.tgz

Tool submission will be open until June 19 (AoE).