eltociear/pandas-tasks-v1
pandas-tasks-v1 Task dataset for a pandas RL / eval environment, in the shape used by the Prime Intellect Environments Hub. 43 pandas DataFrame manipulation tasks across 6 categories. Each task gives the model one or more input frames and an instruction; the answer is the frame left in df, graded with pandas.testing.assert_frame_equal against a reference result. Grading is fully deterministic — no LLM judge, no external API. Category Tasks Covers transformation 10… See the full description on the dataset page: https://huggingface.co/datasets/eltociear/pandas-tasks-v1.
pandas-tasks-v1
Task dataset for a pandas RL / eval environment, in the shape used by the Prime Intellect Environments Hub.
43 pandas DataFrame manipulation tasks across 6 categories. Each task gives the model one or more input frames and an instruction; the answer is the frame left in df, graded with pandas.testing.assert_frame_equal against a reference result. Grading is fully deterministic — no LLM judge, no external API.
Fields
Frames are serialised as {"data": <to_json orient="split">, "dtypes": {col: dtype}}. The dtype map is carried explicitly because to_json alone loses dtypes (int32 returns as int64, datetimes as strings) and the reward compares dtypes.
How it was built, and why you can trust the answer key
Tasks are defined as (deterministic input frames, instruction, reference solution). The expected output is computed by executing the reference solution, never written by hand, so the answer key cannot drift from the instruction.
Every task is then independently verified:
- the reference solution runs without error and returns a DataFrame
- it is deterministic (executed twice, compared with
assert_frame_equal) - the result is non-empty
- the result is not identical to the input (identity tasks carry no signal)
- both the result and every input frame reproduce exactly through the serialisation round-trip, dtypes included
All 43 tasks pass. The builder and its verifier are open: `build_tasks.py`.
Notes
Because grading is an exact frame comparison, column order, row order, the index and dtypes all matter. Prompts state the required index handling and any non-obvious dtype explicitly, so a correct solution is never ambiguous.
