BAPCtools

BAPCtools copied to clipboard

Sometimes generators have bugs where they generate valid but unintended data, and you only find them after a while by inspecting the generated `.in` files manually. Maybe we could come...

RagnarGrootKoerkamp

data/bad: renaming and generation

6

TODOs for invalid inputs: 1. Make BAPCtools recognise `data/invalid_inputs`, continue supporting `data/bad` but with a warning 2. Move the files currently created by `bt new_problem` in `data/bad` to the generator....

thorehusfeldt

Generators: reconsider -f --samples defaults

1

The generators framework work very smoothly, but I now constantly get tripped up in the following dance: ```bash > bt generate PROBLEM closestpairscoring Generate: sample/2 SKIPPED: 2.ans; supply -f --samples...

thorehusfeldt

[problem] Rename `Problem.name` to `Problem.id`

1

The `Problem.name` field left me confused just a bit too often, as I thought it would contain the human-readable name of the problem instead of the problem's ID/"short name" :innocent:

mpsijm

RagnarGrootKoerkamp

Generators: semantics of `#testgroup/testdata.yaml` key

1

## In a Nutshell Q: The contents of a testcase’s `testdata.yaml` file be overwritten by the entries in `#testcase/"testdata.yaml"`. Should this happen 1. for the entire file or 2. for...

thorehusfeldt

Generators documentation: more accessible terminology

2

(This is not about changing functionality, but using terminology that is more aligned with the terminology used in the problem format specification.) *Analysis*: Too many things are called `generator(s)` right...

thorehusfeldt

Many `test/problems/*/problem.yaml`s break the specification

4

## Background In a `problem.yaml`, the key `name` specified as | Key | Type | Default |Comments | |--|--|--|--| name | String or map of strings |   | Required. If...

thorehusfeldt

`bt export` skips interactive samples

10

Why are they not exported? We only seem to export `.interaction`, and `.in.statement` for some reason?

mzuenni

Generators: Add `testcase: count: X` for multiple testcase copies

10

Currently we do ```yaml - random: gen.py {seed:1} - random: gen.py {seed:2} - random: gen.py {seed:3} ``` which would be nice to replace with ```yaml - random: input: gen.py {seed}...

RagnarGrootKoerkamp