Comments (5)
It would be also nice to have a category for output validator checking.
from problemtools.
Agree that this would be nice. Do you have concrete suggestions/preferences for how to extend the problem format to include this?
For input files, one could consider adding something like input_format_validators/bad_inputs
containing .in files, or data/bad_inputs
.
For output files, maybe one wants to be able to add incorrect outputs to some of the actual test cases, rather than adding new cases? If so, maybe allowing adding data files with suffix .out.wrong-<id>
?
@niemela do you want to weigh in on this?
from problemtools.
For separation of concerns input_format_validators/bad_inputs is probably nicer. Your suggestion for output files sounds good to me.
from problemtools.
Hey,
I implemented this feature based on your ideas. See pull request #86 for details.
from problemtools.
I've just implemented some version of this for BAPCtools: RagnarGrootKoerkamp/BAPCtools#35.
Happy to change that to whatever structure is decided upon eventually.
from problemtools.
Related Issues (20)
- input_validator_flags unexpected behaviour with test data groups HOT 1
- No support for F# HOT 1
- Required plasTeX version? HOT 2
- OSX 12.5 install attempt HOT 2
- OSX running verifyProblem trying to compile c++ solution HOT 2
- problem2html crashing HOT 1
- Timing calculation needs to be conservative HOT 3
- Strange TLE verdicts for PAC submissions - unreported time margin used HOT 3
- MacOS Support - ERROR in input format validators: No input format validators found HOT 5
- pip3 system-wide option installs in $HOME/.local/bin HOT 4
- accept_score expected to be number, not string HOT 1
- Outdated DockerHub images HOT 3
- Disentangle score, score, and score.txt for scoring problem with scoring and nonscoring validators
- Verifyproblem Kotlin version >= 1.7
- Symlinks for reuse of input files with different output validator flags HOT 5
- verifyproblem not showing what test case led to WA if it gets PAC
- Use Black formatting HOT 3
- Unclear how the problemtools toolchain relates to the problem package format spec HOT 1
- verifiy problem not working HOT 2
- Fix ambiguous warning around languages that are "not recommended" for output validators HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from problemtools.