funes-recall-session
Collection
agentcap: paired HTTP captures + native session traces. Join on run_id. • 4 items • Updated
Pi traces preview
Wed, Jul 1
One of the procedural-data patterns we relied on was Dyck sequences. Why did we include them, and what did they do for the model's long-context recall? 1
message 2
tools We added an output-embedding centering step (OEC) to stabilize training. Which variant did we choose — μ-centering or μ-loss — and what was the reasoning? 1
message 6
tools Earlier in this project we experimented with front-loading procedural data before the main pretraining run. What proportion did we settle on, and what did it buy us over standard pretraining? 1
message 11
tools One of the procedural-data patterns we relied on was Dyck sequences. Why did we include them, and what did they do for the model's long-context recall? 1
message 1
tool We added an output-embedding centering step (OEC) to stabilize training. Which variant did we choose — μ-centering or μ-loss — and what was the reasoning? 1
message 1
tool Earlier in this project we experimented with front-loading procedural data before the main pretraining run. What proportion did we settle on, and what did it buy us over standard pretraining? 1
message 1
tool dacorvo/funes-recall-session-pi-traces
pi coding-agent session traces produced by
agentcap runs. Each run
contributes one folder under data/<run_id>/; inside, one file per
session in pi's native export format.
The on-the-wire HTTP captures for these same runs live in
dacorvo/funes-recall-session-captures.
Both belong to the
funes-recall-session Collection
— join on run_id to align captures with traces.
- Downloads last month
- 77