Skip to content

Packaging#

rbx supports exporting problem/contest packages into a few formats. You can see in the table below which formats are supported, and what are its supported features and limitations:

Format

Target Systems

Supports

ICPC
(coming soon)

DOMjudge, Kattis

✅ Interactive problems (without checker)
✅ Batch problems
✅ Test grouping
✅ Limits per language
✅ Solution verification
✅ Package upload

BOCA

BOCA

✅ Interactive problems (with checker)
✅ Batch problems
✅ Limits per language
✅ Package upload
❌ Test grouping
❌ Solution verification

Polygon

Codeforces, Polygon

✅ Interactive problems (with checker)
✅ Batch problems
✅ Limits per language
⚠ Package upload (with limitations)
❌ Solution verification
❌ Test grouping

rbx package#

rbx provides an umbrella rbx package <format> command group that contains commands for each of the formats supported by it.

All these formats support a -v flag, that sets the verification level for building the package.

By default, packages will be built with the -v flag set to 4 (the maximum value), which means that tests will be built, validated and all solutions will be run against them, and their expected outcomes will be verified.

You can change this by setting the -v flag to a different value, with the following meanings:

  • 0: Tests will be built, no validation will be done.
  • 1: Tests will be built and validated.
  • 2: Tests will be built, validated and accepted solutions will be run against them, and their expected outcomes will be verified.
  • 3: Tests will be built, validated and non-TLE solutions will be run against them, and their expected outcomes will be verified.
  • 4: Tests will be built, validated and all solutions will be run against them, and their expected outcomes will be verified.

The example below shows how to build an ICPC package by only generating tests and validating them.

rbx package icpc -v1

See each one of the sections dedicated to each of the avilable formats on the sidebar.