Datasets:

deepsai8
/

nttd-submissions

Error code:   StreamingRowsError
Exception:    CastError
Message:      Couldn't cast
session_id: string
company_id: int64
company_name: string
performance_rating: int64
total_cargo: int64
company_value: int64
final_balance: int64
final_loan: int64
task_id: string
scenario_id: string
map_seed: int64
settings_digest: string
map_size_x: int64
map_size_y: int64
landscape: string
terrain_type: string
profile_version: string
runtime_mode: string
end_reason: string
wall_seconds: double
game_days: int64
start_game_date: int64
end_game_date: int64
participant_type: string
agent_id: string
nttd_framework: string
model: string
total_actions: int64
successful_actions: int64
prompt_tokens: int64
completion_tokens: int64
total_cost_usd: double
spend_is_reported: bool
model_breakdown_json: string
scored_session: bool
clean_run: bool
blocked_attempts: int64
blocked_operations: string
capability_digest: string
nttd_git_sha: string
nttd_git_dirty: bool
gamescript_digest: string
scenario_file_digest: string
final_save_name: string
final_save_digest: string
final_save_bytes: int64
openttd_version: string
recorded_at: timestamp[us]
started_at: string
entrant: string
submission_id: string
verdict: string
nttd_commit: string
verified_at: string
to
{'entrant': Value('string'), 'submission_id': Value('string'), 'check': Value('string'), 'passed': Value('bool'), 'detail': Value('string'), 'verified_at': Value('string')}
because column names don't match
Traceback:    Traceback (most recent call last):
                File "/src/services/worker/src/worker/utils.py", line 147, in get_rows_or_raise
                  return get_rows(
                      dataset=dataset,
                  ...<4 lines>...
                      column_names=column_names,
                  )
                File "/src/libs/libcommon/src/libcommon/utils.py", line 272, in decorator
                  return func(*args, **kwargs)
                File "/src/services/worker/src/worker/utils.py", line 127, in get_rows
                  rows_plus_one = list(itertools.islice(safe_iter(ds, dataset=dataset), rows_max_number + 1))
                File "/src/services/worker/src/worker/utils.py", line 483, in safe_iter
                  yield from ds.decode(False) if ds.features else ds
                File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 2840, in __iter__
                  for key, example in ex_iterable:
                                      ^^^^^^^^^^^
                File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 2373, in __iter__
                  for key, pa_table in self._iter_arrow():
                                       ~~~~~~~~~~~~~~~~^^
                File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 2398, in _iter_arrow
                  for key, pa_table in self.ex_iterable._iter_arrow():
                                       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
                File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 536, in _iter_arrow
                  for key, pa_table in iterator:
                                       ^^^^^^^^
                File "/usr/local/lib/python3.14/site-packages/datasets/iterable_dataset.py", line 419, in _iter_arrow
                  for key, pa_table in self.generate_tables_fn(**gen_kwags):
                                       ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^
                File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/parquet/parquet.py", line 220, in _generate_tables
                  yield Key(file_idx, batch_idx), self._cast_table(pa_table)
                                                  ~~~~~~~~~~~~~~~~^^^^^^^^^^
                File "/usr/local/lib/python3.14/site-packages/datasets/packaged_modules/parquet/parquet.py", line 156, in _cast_table
                  pa_table = table_cast(pa_table, self.info.features.arrow_schema)
                File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2378, in table_cast
                  return cast_table_to_schema(table, schema)
                File "/usr/local/lib/python3.14/site-packages/datasets/table.py", line 2306, in cast_table_to_schema
                  raise CastError(
                  ...<3 lines>...
                  )
              datasets.table.CastError: Couldn't cast
              session_id: string
              company_id: int64
              company_name: string
              performance_rating: int64
              total_cargo: int64
              company_value: int64
              final_balance: int64
              final_loan: int64
              task_id: string
              scenario_id: string
              map_seed: int64
              settings_digest: string
              map_size_x: int64
              map_size_y: int64
              landscape: string
              terrain_type: string
              profile_version: string
              runtime_mode: string
              end_reason: string
              wall_seconds: double
              game_days: int64
              start_game_date: int64
              end_game_date: int64
              participant_type: string
              agent_id: string
              nttd_framework: string
              model: string
              total_actions: int64
              successful_actions: int64
              prompt_tokens: int64
              completion_tokens: int64
              total_cost_usd: double
              spend_is_reported: bool
              model_breakdown_json: string
              scored_session: bool
              clean_run: bool
              blocked_attempts: int64
              blocked_operations: string
              capability_digest: string
              nttd_git_sha: string
              nttd_git_dirty: bool
              gamescript_digest: string
              scenario_file_digest: string
              final_save_name: string
              final_save_digest: string
              final_save_bytes: int64
              openttd_version: string
              recorded_at: timestamp[us]
              started_at: string
              entrant: string
              submission_id: string
              verdict: string
              nttd_commit: string
              verified_at: string
              to
              {'entrant': Value('string'), 'submission_id': Value('string'), 'check': Value('string'), 'passed': Value('bool'), 'detail': Value('string'), 'verified_at': Value('string')}
              because column names don't match

Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.

nttd

Runs submitted to the nttd benchmark, and what the board concluded about each of them. Agents, multi-agent systems, RL and ES policies, and people, playing OpenTTD as one transport company on one world.

The board is at deepsai8/nttd-leaderboard.

Layout

submissions/<entrant>/<submission-id>/   one bundle, added by pull request
results.parquet                          one row per submission, with its verdict
checks.parquet                           one row per check per submission
trajectories.parquet                     each run's series, for the trend chart
board.json                               the same rows shaped for display

<entrant> is the HuggingFace account that opened the pull request. Identity comes from the platform rather than from anything inside a bundle, because a bundle is written by the contestant.

A pull request may only touch submissions/<your-account>/. Everything at the root is written by the verification job. HuggingFace has no per-path write permissions, so this is a check on the pull request rather than a property of the repository: without it, a diff adding a bundle could edit its own verdict in the same commit.

What a bundle contains

Every file does one of three jobs, and nothing does none of them.

Evidence, which cannot be derived from anything else:


`final.sav`	the savegame. The score is recomputed from this
`snapshots.parquet`	the series. How the run got where it got
`actions.parquet`	what the contestant did
`tiles.parquet`	the terrain scan. Shows where two worlds differ
`events.parquet`	lifecycle and game events
`nttd_scenario.conf`	the resolved scenario, including the map seed

The claim, recomputed from the evidence and compared:


`result.parquet`	the score, all provenance, and the business metrics

Integrity:


`manifest.json`	a sha256 per artifact, plus the map digest

No bundle carries a verdict. One that did would be asserting something anyone could write.

Playing the same map

result.parquet carries map_seed, map_size_x, map_size_y and terrain_type, and nttd_scenario.conf carries the same seed as _map_seed. Together those are everything needed to generate the identical world and play the same problem, which is why the board shows the seed on every row: any run can be reproduced rather than taken on trust.

Reading a result row

Rank is OpenTTD's own performance_rating, unchanged: it is game-authoritative and hard to game, unlike company value which rises by drawing a loan. The tiebreak is total_cargo, every unit delivered over the run, banked as each quarter ends because the counter the game exposes resets on the day a 366 day run finishes.

One row per submission, always. An entrant who played six worlds has six rows.

Rows are frozen once verified. There is no score version and no business metrics: both ranked columns come straight from the game, so a change to either is a bug fix rather than a change to what winning means.

Two readings worth knowing. Cost is absent, not zero, when spend was not reported: a policy that genuinely cost nothing said so, and that is a different claim from silence. A check that was not attempted is not a check that failed, so passed is null rather than false in that case.

verdict
`verified`	every check passed, including that the world matches its declared seed
`replayed`	the score was recomputed from the savegame, the world was not reconciled
`unverified`	the artifacts do not support checking, or nobody has run the job yet

Failing rows are published rather than hidden, and every check is published by name, so a failure can be diagnosed without access to the job that produced it.

Submitting

nttd submit --session ses_...     # builds the bundle
nttd verify -s ses_...            # check it yourself first, advisory

Then open a pull request adding the bundle under submissions/<your-account>/<id>/.

Only scored, single-company runs are eligible. A scored run is one whose world conforms to the benchmark profile; check with nttd scenario validate. A session with several contestant companies is a different problem, and nttd does not score it.

Downloads last month: 115