kaggle-orbit-wars

KO | EN

gitlite — search

#ai #llm #go #machine-learning #linux #java #awesome #kubernetes #vue #awesome-list #pytorch #openai #mcp #open-source

kaggle-orbit-wars

(★ 50)

An RL library for the Kaggle 2026 Orbit Wars competition

kaggle-orbit-wars Latest Version Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# OWL: Orbit Wars (reinforcement) Learning

## Setup instructions

1. Install prerequisites:
   - [Rust](https://www.rust-lang.org/tools/install)
   - [uv](https://docs.astral.sh/uv/getting-started/installation/)
   - [just](https://github.com/casey/just)
2. Install the repository's pinned Rust toolchain and `rustfmt` component:

```sh
rustup toolchain install nightly-2026-04-18 --component rustfmt
```

3. Generate replay fixtures:

```sh
scripts/regenerate_test_fixtures.sh
```

4. `just prepare` should run without errors. If mapped docs are genuinely still
   current after a small code change, rerun it as `DOCS_CURRENT=1 just prepare`
   to acknowledge that review.

## Containerized builds

See `docs/containerization.md` for building a Docker image with the locked Python
dependencies, Rust toolchain, compiled extension module, and example Slurm launch
patterns.

## Kaggle submission build

Build a Kaggle-compatible image from the current worktree and create
`artifacts/submission.tar.gz` with:

```sh
just kaggle-submission runs/20260505-120000/checkpoint_last_best.pt
```

Pass a submission name to write `artifacts/<name>.tar.gz` instead:

```sh
just kaggle-submission runs/20260505-120000/checkpoint_last_best.pt my-run
```

Pass a quantization format as the third argument to quantize the packaged
model weights during submission generation:

```sh
just kaggle-submission runs/20260505-120000/checkpoint_last_best.pt my-run fp4
```

Pass an optional fallback checkpoint after the existing arguments to package a
second, faster model:

```sh
just kaggle-submission runs/20260505-120000/checkpoint_last_best.pt my-run fp4 \
  --fallback-checkpoint runs/20260501-090000/checkpoint_last_best.pt
```

The submission recipe runs `just prepare`, rebuilds the `orbit-wars:kaggle`
image with Buildx zstd layer compression, compiles the Rust extension inside
Kaggle's Python image, and packages `python/owl`, `python/main.py` or `main.py`,
the requested model bundle, and its adjacent `config.yaml` under
`models/primary/`. If a fallback checkpoint is provided, its model bundle and
adjacent `config.yaml` are packaged under `models/fallback/`.
Rebuilding the image during submission generation keeps the packaged Python code
aligned with the current checkout. The packaged checkpoint keeps the original
checkpoint contents only for validated model state-dict tensor weights needed by
the Kaggle agent; malformed model entries fail during packaging rather than at
agent startup. To store packaged models below fp32 precision, pass a
quantization format such as
`fp8_e4m3fn`, `fp4_e2m1fn_x2_scaled_block16`, or
`nf5_g128_lsq_policy_last_fp8`. Lower-bit normal-float formats `nf4_g128_lsq`,
`nf3_nf4_structured_3p5`, and `nf3_g128_lsq` are also supported; unique prefixes
such as `fp4` are accepted.
The default `fp32` leaves checkpoint weights unchanged. The Kaggle agent
loads quantized slim checkpoints by dequantizing and copying one tensor at a
time into the model, avoiding a full fp32 state-dict copy during startup.
The checked-in `python/owl/agent/agent_config.yaml`
sets `int8_quantization: always`, which converts loaded `nn.Linear` layers to
PyTorch dynamic int8 CPU inference while keeping final actor/critic output heads
in fp32. Set it to `2p` or `4p` to use int8 only for that game size, or `never`
to disable serving-time quantization and use fp32 CPU inference. The packaged
Kaggle agent is CPU-only; model serving, action expansion, and Kaggle action
conversion all keep tensors on CPU. Set
`lora_mode` to control whether LoRA adapters are dequantized and folded into
regular `nn.Linear` weights for every game (`always`) or only for two-player or
four-player games (`2p` / `4p`); folding happens before int8 inference
quantization. Set
`fallback_min_overage_time` in `python/owl/agent/agent_config.yaml` to switch to
the fallback model when remaining overage time drops below that threshold;
`null` disables fallback routing even if the fallback model is packaged. A
packaged fallback config is validated during startup, but the fallback model
weights are loaded on the second observed turn rather than during initial agent
construction. The delayed load still happens even if remaining overage time has
already fallen below the fallback threshold, preferring to risk that one timeout
over giving up fallback for the rest of the game.

The Kaggle observation encoder filters fleets smaller than the configured
`min_fleet_size` while encoding observations. This intentionally trades a small
amount of board-state detail for lower inference latency, because many tiny
fleets can increase entity count enough to trigger fallback routing. To avoid
marking a still-alive player as gone, if a player has no current planets and
all of their fleets are below that threshold, the encoder keeps that player's
single largest fleet in the encoded observation.

## Orbit Wars reference

The Rust rules engine targets the installed `kaggle-environments` Orbit Wars
implementation. Resolve the local module and gameplay prose paths with:

```sh
uv run python -c 'from importlib import import_module; from pathlib import Path; m = import_module("kaggle_environments.envs.orbit_wars.orbit_wars"); print(Path(m.__file__).resolve()); print(Path(m.__file__).with_name("README.md").resolve())'
```

## PPO training configs

Training presets live in `configs/`:

- `baseline.yaml`: PPO with last-best teacher stabilization and the 6m GELU
  stateless transformer preset,
  discrete-target actions, `max_entities=256`, one PPO epoch per rollout,
  larger rollout/minibatch sizing, Muon/AdamW optimizer rates, periodic
  checkpoints every 20M environment steps, `torch.compile` default mode for PPO
  tensor helpers, compiled transformer trunk with
  `max-autotune-no-cudagraphs`, and bfloat16 autocast by default.
- `baseline_adam.yaml`: Adam optimizer variant with explicit optimizer
  settings, including `1e-4` learning rate, `(0.9, 0.999)` betas, `1e-5`
  epsilon, no weight decay, and the same warmup/cosine scheduler shape.
- `baseline_adamw.yaml`: AdamW optimizer variant matching `baseline_adam.yaml`
  except for decoupled `0.01` weight decay.
- `model/stateless_transformer_21m_swiglu.yaml`: larger SwiGLU stateless
  transformer config with an inline discrete-target actor override using eight
  action mixtures.
- `model/stateless_transformer_6m.yaml`, `model/stateless_transformer_11m.yaml`,
  and `model/stateless_transformer_21m_gelu.yaml`: GELU variants of the
  stateless transformer presets.
- `model/stateless_transformer_28m.yaml`: larger SwiGLU stateless transformer
  preset with a discrete-target actor.
- `model/stateless_transformer_12m.yaml`,
  `model/stateless_transformer_25m.yaml`, and
  `model/stateless_transformer_50m.yaml`: a GELU `mlp_ratio=2.0`
  discrete-target ladder scaling width at a fixed `head_dim=32`
  (`320x10`, `448x11`, `512x19`).
- `model/stateless_transformer_200m_d38.yaml`,
  and `model/stateless_transformer_200m_d60.yaml`: depth-specific 200M stateless
  transformer presets with discrete-target actors.

The training entrypoint configures PyTorch for TF32 matmul/conv precision and
cuDNN benchmarking before constructing the environment, model, and optimizer.
Fresh launches explicitly reset model parameters before optimizer construction.
When `--load-model-weights` is set, the fresh trainer then replaces those
parameters from the checkpoint. Set
`--load-model-weights-mode model_and_optimizer` to also load optimizer
moment/momentum state while keeping the fresh optimizer hyperparameters and
scheduler state.
resume launches load checkpoint weights and optimizer state without resetting
the model first.
Set `model.lora` on stateless transformer configs to run PPO as a LoRA
fine-tune. LoRA freezes the base model, wraps selected linear projections, and
trains only the low-rank adapter parameters. `rank` is required; optional fields
include `alpha_scale` (the LoRA update scale, default `1.0`), `target_modules`,
and `target_block_count` for final-block-only adaptation. Set `target_value_head` / `target_policy_head` to also wrap the
critic and actor heads (set `target_modules` to `[]` to adapt only the heads).
Set `roundtrip_quantization` to a supported checkpoint quantization format to
quantize and dequantize the frozen base weights before adapter training, so
fresh LoRA fine-tuning sees the same base-weight numerics used after final
checkpoint quantization.
LoRA presets under `configs/model/lora/` can be selected with overrides such as
`-o model.lora=2p_200m_qv_r16`.
Checkpoint extraction and Kaggle submission packaging accept separate base-model
and LoRA adapter quantization formats. When base quantization is enabled and no
LoRA format is provided, adapter tensors default to fp16. Packaged LoRA adapters
are folded into the base model before inference int8 quantization/emulation.
Recurrent models do not support LoRA. Fresh LoRA launches can use
`--load-model-weights` with a
non-LoRA base checkpoint; missing LoRA adapter tensors are initialized from the
config while base tensors are loaded from the checkpoint. Fresh LoRA launches
must use `--load-model-weights-mode model_only`; resume existing LoRA runs to
restore optimizer state. `teacher_mode: last_best` also works with LoRA: the
self-play opponent is built with the student's adapter architecture and seeded
from the (possibly non-LoRA) `teacher_init` checkpoint, so it can be refreshed
in place each time the student wins.
Optimizer configs may set `lr_schedule.schedule` to
`linear_warmup_cosine_decay` for warmup followed by cosine decay, or `cosine`
for a repeating LambdaLR multiplier that moves from `1.0` to `lr_min_ratio`
halfway through `full_cycle_steps` optimizer steps, then back to `1.0` at the
end of the cycle. The
schedule name selects the accepted scheduler fields; unrelated scheduler fields
are rejected.
Training `EnvConfig.n_envs` must be even. PPO updates run
`rl.ppo_epochs` full-shuffle passes over rollout segments, grouped by
`rl.segments_per_minibatch`; set `rl.gradient_accumulation_steps` above `1` to
accumulate multiple minibatches before each optimizer step. `EnvConfig.n_envs`
must be divisible by
`rl.segments_per_minibatch * rl.gradient_accumulation_steps`. In distributed PPO
launches, `EnvConfig.n_envs`, rollout horizon, minibatch segment width, and
gradient accumulation are per GPU. Checkpoint cadence, `--max-env-steps`, W&B
step values, and `train/env_steps` are counted across all ranks. Resume launches
with a different GPU count derive an equivalent per-rank config by scaling
`env.n_envs` and
`rl.segments_per_minibatch * rl.gradient_accumulation_steps` by
`saved_gpus / current_gpus`. The derived config keeps
`rl.segments_per_minibatch` at or below the saved value, so the per-minibatch
training batch does not increase; resume fails if the scaled values are
fractional or config-invalid.
When `env.reward_mode` is `win_only`, set `model.value_mode` to `win_only` so
critic values train against raw winner probabilities; other reward modes require
the default `win_loss` value mode.
`rl.value_loss` selects the critic objective. The default `mse` regresses the
scalar value toward the GAE return. `winner_ce` instead trains the
winner-probability softmax as a classifier, using the categorical cross-entropy
toward a distributional GAE(lambda) winner target (the same lambda-return
recursion carried on the per-player winner distribution, resolving to the
terminal winner distribution and bootstrapping the critic's distribution on
time-limit truncation). It requires `env.reward_mode: win_only` (hence
`model.value_mode: win_only`), `model.critic_mode: softmax`, `rl.gamma: 1.0`, and
`rl.vf_clip_coef: null`; see `configs/winner_ce_6m.yaml`.
When `rl.normalize_advantages` is enabled under distributed PPO, advantage mean
and variance are computed over the masked global minibatch across ranks.
`rl.eval_replay_games` must be no larger than `env.n_envs` because evaluation
samples replay games from the same vectorized eval batch.
`rl.ppo_clip_mode` defaults to `per_player`, which clips the summed per-player
joint action log-probability. Set it to `per_entity` to clip each controllable
action entity independently before summing those clipped policy-loss terms back
to the player-step.
PPO supports `pure`, `discrete_targets`, and `discrete_target_bins` action specs
when the `StatelessTransformerV1` actor discriminator matches the environment
action spec. The current discrete-target actor requires
`max_per_planet_launches: 1`; the target-bin actor requires matching `n_bins`.
Both discrete target specs default to `targeting_mode: full_mask`; set
`stop_bad_launch` or `anything_goes` to expose loose target masks while
controlling whether sun-crossing decoded launches are replaced with no-ops.
`RecurrentTransformerV1` supports only `discrete_targets` with
`launch_mode: binary` and `max_per_planet_launches: 1`.
Set `rl.teacher_mode` to `fixed` or `last_best` to add student-teacher
stabilization losses. `fixed` requires `rl.teacher_init`, while `last_best`
uses the current last-best snapshot. On randomly initialized fresh launches
with no `teacher_init`, the last-best teacher losses stay disabled until the
current model first replaces `checkpoint_last_best.pt`; fresh launches from
`--load-model-weights` use that starting checkpoint as the initial last-best
teacher. Fixed teachers do not seed `checkpoint_last_best.pt`; win-rate
evaluation against last-best follows the same checkpoint lifecycle as a run
without a teacher. `rl.teacher_init` points at a training checkpoint whose
adjacent `config.yaml` is used to construct the teacher model before loading
weights.
For a fixed teacher, the architecture may differ from the student. A last-best
teacher always uses the student's architecture so it can be refreshed in place.
Observation specs must match except for `max_entities`, where the teacher model
uses the student capacity for rollout tensors; action specs must match exactly. Actor
factorization details such as discrete-target launch mode or target-bin count
must be compatible. Teacher models must be stateless; recurrent teachers are
rejected because PPO teacher inference runs only from stored rollout segments.
The frozen teacher trunk runs once per iteration in a chunked `no_grad` pass
after rollout (chunk size
`rl.teacher_segments_per_minibatch`, default `32` segments); its distribution
targets are cached and each update minibatch consumes them without re-running
the teacher trunk. The cached action-KL path supports only the `discrete_targets`
actor without player-count adapters (a fixed teacher must also match the
student's launch mode). Value distillation does not use the actor KL path, but
the trainer still requires matching action specs and non-adapter models.
`rl.teacher_kl_coef` and `rl.teacher_value_coef` weight the action KL and
per-state winner-distribution cross-entropy stabilization losses; both default
to `0.001`. `rl.teacher_schedule.mode` defaults to `none`; set it to
`linear_decay` with `decay_steps` and `decay_min_ratio` to linearly decay both
teacher coefficients by optimizer step down to the configured minimum ratio.

Run a preset with:

```sh
uv run python scripts/run_ppo.py configs/baseline.yaml runs --log-mode debug --max-env-steps 16
```

Fresh launches accept `-o`/`--overrides field.path=value`; when provided, rank 0
prints the flattened override list before loading the config.
`rl.model_compile` defaults to `trunk`, which compiles the stateless
self-attention transformer trunk as one dynamic-shape callable after
FlashAttention packing and before unpacking, using
`rl.model_compile_mode: max-autotune-no-cudagraphs`. Set
`rl.model_compile=mlp` to compile each shared or per-player-count adapter
transformer-block MLP in place with `dynamic=True`, keeping attention packing
and flash-attn calls eager while allowing Inductor to optimize the FFN path. Set
`rl.model_compile=none` for short CPU smoke tests or compile-debugging runs.
The trunk mode rejects cross-attention observations, recurrent models, and
player-count adapter trunk blocks.

Fresh launches can also initialize the model from an existing full training
checkpoint without resuming the optimizer, scheduler, config, or W&B run:

```sh
uv run python scripts/run_ppo.py configs/baseline.yaml runs \
  --load-model-weights runs/20260505-120000/checkpoint_last_best.pt
```

This loads only `checkpoint["model"]` plus the `env_steps`,
`player_step_total`, `total_games_played`, and `total_active_entities` logging
counters. Optimizer steps, target-KL counters, optimizer state, scheduler state,
and checkpoint config are fresh for the new run.
Pass `--load-model-weights-mode model_and_optimizer` to additionally load the
checkpoint optimizer moment/momentum state. That mode still keeps optimizer
steps, target-KL counters, scheduler state, checkpoint config, and W&B run state
fresh; optimizer hyperparameters such as LR and weight decay come from the fresh
config, not from the checkpoint optimizer param groups.

PPO run directories save `config.yaml` alongside checkpoints. The saved config
includes `runtime.n_runtime_gpus`; resume uses it to keep the effective rollout
and optimizer-step batch shape equivalent when the current launch uses a
different number of ranks, and fails when no exact derived config exists.
Checkpoints save model, optimizer, scheduler, environment-step metadata,
optimizer-step metadata, player-step metadata, plus the W&B run ID used for
resume. Resume training by passing either a run directory or a checkpoint file
as the only positional path:

```sh
uv run python scripts/run_ppo.py runs/20260505-120000
uv run python scripts/run_ppo.py runs/20260505-120000/checkpoint_00_020_000_000.pt
```

Directory resume compares `checkpoint_final.pt` with the latest numbered
checkpoint when both exist, loads the one with more saved environment steps, and
never treats `checkpoint_last_best.pt` as the primary training checkpoint. When
`checkpoint_final.pt` is absent, directory resume loads the latest numbered
checkpoint. File resume loads `config.yaml` from the checkpoint's parent
directory. Both resume modes require the associated
`checkpoint_last_best.pt` and W&B logging so the saved run ID can be resumed.
Checkpoints do not save the Rust environment state or current observation, so
resumed runs continue from a fresh environment batch rather than acting as exact
simulator snapshots. Periodic checkpoint names use grouped zero-padded
environment-step labels such as `checkpoint_00_022_000_000.pt`. At each
periodic checkpoint, the current model is evaluated against the last-best
snapshot using sampled policy actions across `env.n_envs` games using the
configured `env.two_player_weight`, with current and last-best seats randomly
shuffled across active player slots for each eval game, and logs
`eval/win_rate_against_last_best` plus terminal environment metrics under
`eval/`. When the current model reaches at least 70% eval win rate, the
last-best snapshot is replaced and also saved as `checkpoint_last_best.pt`. If
the first periodic checkpoint finds no `checkpoint_last_best.pt`, the starting
last-best model is saved there first, using its starting environment-step count.
Set `rl.eval_replay_games` to a positive count to save random eval replay
samples from the weighted eval game set under
`eval_replays/<checkpoint-name>/` in the run directory. The sampled game
ordinals are selected up front rather than taking the first games to finish.
Each sampled eval game is written as its own JSONL file.

Training logs terminal environment metrics under `train/` when episodes finish
during a rollout, including game length, per-player win rates, launch density,
planet occupancy for 2-player and 4-player games, max-entity overflow counts,
terminal ship counts, completed game counts, planet captures, launch and fleet-size statistics,
neutral planet/comet undershot rates, full-length game rate, cumulative active
player-step totals, and fleet/ship losses in combat, the sun, or out of bounds.
Rollout observation mix is logged as `train/1p_rate`, `train/2p_rate`,
`train/3p_rate`, and `train/4p_rate` from `obs.still_playing` alive counts.
Planet occupancy is reported at terminal as
`train/terminal_planet_occupancy_rate_2p` and
`train/terminal_planet_occupancy_rate_4p`.
Policy logs include total entropy plus policy-specific component means such as
`policy/launch_entropy`, `policy/target_entropy`,
`policy/fleet_size_full_entropy`, and `policy/angle_and_size_entropy`.
Teacher runs additionally log `teacher/kl`, `teacher/value_cross_entropy`,
weighted loss terms, and per-action KL components such as
`teacher/launch_kl`, `teacher/target_kl`, or `teacher/fleet_size_full_kl`.
Teacher precompute timing is logged as `time/teacher_seconds` and
`perf/teacher_sps`; both are `0.0` when no teacher precompute runs.
Iteration throughput is logged as `perf/steps_per_second`, plus
`perf/tokens_per_second` for unmasked model tokens and
`perf/active_entities_per_second` for action-taking source entities. These
rates use total iteration time, including rollout, teacher precompute, and PPO
update time. The active-entity count is also accumulated as
`train/total_active_entities` and saved in checkpoints.

## Replay capture

`scripts/benchmark_checkpoints.py` can save replay JSONL samples with
`--save-replay-games N`, split across 2-player and 4-player benchmark games
according to `--two-player-weight`. Files are written under `--replay-dir`,
defaulting to `replays/benchmark_checkpoints`.
Each sampled benchmark game is written as its own JSONL file.
For GPU-friendly int8 quality checks, pass `--int8-emulation [none|a|b|both]` to
emulate x86 int8 quantization of non-output `nn.Linear` weights and activations
for one or both checkpoints while leaving final actor/critic output heads
unquantized. This emulates x86 int8 numeric degradation on `--device`; it does
not measure real int8 kernel throughput.
Open `tools/orbit_wars_replay_viewer.html` in a browser and choose
a saved `.jsonl` file or Kaggle episode replay `.json` file to play back a
game.

Replay rows contain raw Rust environment snapshots for one completed game:
board constants, step/config values, outer-slot owner IDs, player maps, action
entity slots, planets, fleets, comets, rewards, dones, and model assignments.
The Python replay recorder samples game ordinals randomly before rollout and
uses Rust terminal snapshots captured before vectorized env auto-reset.

## Orbit Wars replay parity

Replay parity tests use compact Kaggle episode transition fixtures. The
`replay-*.jsonl` files are intentionally ignored by Git because full episodes can
be large.

The current reference episodes are:

- `75930761` (2-player game)
- `75926553` (4-player game)

If fixture files are missing, download them directly into the test fixture
directory:

```sh
scripts/regenerate_test_fixtures.sh
```

The regeneration script requires Kaggle API credentials configured for the local
user.

### Replay parity workflow

The fixture shape is JSONL with one row per transition: episode id, player
count, step, normalized numeric player action triples from
`steps[t][player].action`, per-player Kaggle `status` and `reward`, the input
observation from `steps[t - 1][0].observation`, and the expected state from
`steps[t][0].observation`. `cargo test` discovers all `replay-*.jsonl` files in
the fixture directory and fails by default if none are present.

Supported test environment variables:

- `ORBIT_WARS_PARITY_FIXTURE_DIR`: directory containing extracted JSONL parity
  fixtures.
- `REQUIRE_PARITY_FIXTURES=0`: skip replay parity, and skip generation parity
  only when generation fixtures are missing. Missing fixtures fail by default.

When the upstream rules change without replacing the reference episode set,
keep the replay test code stable. When replacing episodes, download replacement
JSONL fixtures, update `REQUIRED_REPLAY_COVERAGE` in
`src/rules_engine/replay_tests.rs` with each episode's id, player count, and row
count, and update the episode lists in this README, `docs/rules-engine.md`, and
`docs/rules-parity-coverage.md` before running the parity tests.

## Generation parity

Map generation, reset/home assignment, comet path generation, and comet ship
sampling are checked against fixtures produced by the Python reference
implementation under recorded random streams. Regenerate those fixtures after
intentional upstream rule changes:

```sh
uv run python scripts/generate_reference_fixtures.py
```

The generated fixture is written to
`tests/fixtures/generation/reference_generation.json` and ignored by Git.

## Updating tests after Python rule changes

When the official Orbit Wars environment changes, update the Rust parity tests
in this order:

1. Update the installed `kaggle-environments` package to the latest version.
2. Regenerate all test fixtures. With no arguments, the script uses the current
   reference episodes listed above:

```sh
scripts/regenerate_test_fixtures.sh
```

To switch replay episodes, pass the replacement Kaggle episode IDs:

```sh
scripts/regenerate_test_fixtures.sh NEW_EPISODE_ID_1 NEW_EPISODE_ID_2
```

The script removes outdated `replay-*.jsonl` files before downloading the new
set, and rewrites `tests/fixtures/generation/reference_generation.json` from the
installed Python environment. Replay tests also validate the documented
reference episode player counts and row counts, so update the required coverage
in `src/rules_engine/replay_tests.rs` when replacing the episode set.

3. Update the documented episode IDs in this README, `docs/rules-engine.md`,
   and `docs/rules-parity-coverage.md`.

4. Run the full checks with the new fixtures present:

```sh
just prepare
```

5. Fix any failing Rust parity tests by matching the updated Python behavior,
   then rerun `just prepare`.

Generation and replay fixtures remain ignored by Git; keep only the episode IDs
and setup commands in source control.

kaggle-orbit-wars

kaggle-orbit-wars Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

kaggle-orbit-wars

kaggle-orbit-wars Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Download README