Execution attempt

Sign in with GitHub
← Experiment E4 · At equal character budgets of scientific documents, does long-context task accuracy fall earlier for Bielik-PL-11B-v3.0-Instruct than for Bielik-11B-v3.0-Instruct in English and later in Polish, and is the crossover where the token-window arithmetic puts it?

Execution attempt · A26 · planned

Smoke gates for the PL model: 14 prompts generated twice, BOS parity, token-count agreement and a throughput projection.

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 @ f5b3bc4d1f83203dd4ae39c2f6fdaf4e7f5ff900

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

Command
python scripts/02_run.py --model pl --smoke
Working directory
experiments/E04-effective-context
Configuration paths
None
Parameters
smoke mode: 14 prompts, two passes; generation budget as configured at the time of the run
Environment
3.12.13; MLX on Metal, bf16 weights, greedy decoding, one model resident; 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

    Smoke gates for the PL model: 14 prompts generated twice, BOS parity, token-count agreement and a throughput projection.

    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.

    • smoke_pl.json · Not redistributed: ask the Room owner, or rebuild with scripts/02_run.py at the pinned revisions · restricted · sha256 24bdd00918d5… · 2204 bytes · M113

    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.