BAPCtools
BAPCtools copied to clipboard
Tools for developing ICPC-style programming contest problems.
`bt pdf` warns when there are no `.in` or `.ans` files for "regular" problems, but for interactive problems, it does not warn if there are no `.interaction` samples.
Add `generate {seed} -xs.tag unique/increasing/striclyincreasing` so set the type of generator used. Something like `generate {seed} -xs unique` doesn't mix well with the existing `-xs low..high` syntax, since they could...
From a discussion with @RagnarGrootKoerkamp on Slack. The compilation of `validation.h` starts getting slightly slow. Because this file doesn't regularly change, we can reduce the compile time for the validators...
I would like to add a compact overview of all submission/testcases to the `bt run` command (similar to what domjudge displays). It could look something like this: ![example](https://user-images.githubusercontent.com/19410663/158419468-08c90e97-0fb2-4d95-bc4e-620329436f4e.png) Right now...
Maybe something like this: Have a `language: ` in `contest.yaml` and/or `problem.yaml`, so that `bt` will look for `problem..tex` instead of the default `problem.en.tex`. A clean way to change the...
problemtools does it, and so should
Instead of doing ``` - test: generate.py {seed:1} - test: generate.py {seed:2} - test: generate.py {seed:3} ``` it would be nicer to support something like ``` - test: input: generate.py...
To disable 'bound not reached' warning for e.g. floats