Execution attempt

Sign in with GitHub
← Experiment E10 · Does the end-to-end success gap between Bielik-11B-v3.0-Instruct and Bielik-PL-11B-v3.0-Instruct on multi-step tool-use tasks exceed the gap predicted from their one-shot per-step success rates?

Execution attempt · A98 · planned

Computes run 1's endpoints from the first grading.

Succeeded · Registered by @stw2 via agent. Reported and received times are kept apart; no computation or result is verified.

Pinned source and configuration

https://github.com/stw2/tokenizer-science-tax @ 03e30b6cecb9c899914b18931b1f8ee0bdc7d2f5

Reference checked 2026-09-14 13:17 UTC. Later commits, branches or plan changes do not retarget this attempt.

Command
python scripts/05_analyze.py
Working directory
experiments/E10-agentic-compounding
Configuration paths
None
Parameters
bootstrap resamples 2000; seed 20260707; Holm over H2 and H3
Environment
3.12.13 (uv 0.11.16); MLX bf16 on Metal, greedy decoding (temperature 0); Apple silicon, 128 GB unified memory
Output directory
Not recorded

Inputs

Materials the registrant named when registering this attempt, by content identity; obtainability is derived from their location reports. Nothing is fetched or verified.

Delivered events

  1. Registered

    #1

    Computes run 1's endpoints from the first grading.

    reported · received · @stw2 via agent · posted to the Thread

  2. Started

    #2

    Started.

    reported · received · @stw2 via agent · attempt only

  3. Succeeded

    #3

    Completed with exit code 0.

    Exit code 0.

    • analysis.json · Overwritten by the Amendment 1 re-grade before the results commit; not kept · unavailable

    reported · received · @stw2 via agent · posted to the Thread

Report an event

The registrant’s capture tool normally delivers start and outcome events. Reporting here is the same author report with the browser as the reported time; it does not observe the process.

This attempt has a delivered outcome. A new execution is a new attempt.