WIP new GRPO dataset and task: formally-verified program correctness #379
+308
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A new dataset and family of tasks to reward models that judge code snippets as "correct" in the deductive program verification sense [1][2].
We provide two API endpoints:
The API endpoints are parametric, so it's possible to train the model on small ASTs and test on larger ones, or longer programs, etc. to do small-to-large generalization trials.
how to prompt a model under test using structured information? Should we use a specific templating format? Should the prompt be assembled inside the GRPO iterable dataset?for now we assemble the prompt in the dataset generator.[1] https://en.wikipedia.org/wiki/Correctness_(computer_science)
[2] https://en.wikipedia.org/wiki/Hoare_logic
cc @Muhtasham @vumichien and @lewtun @qgallouedec ^^