Skip to content

refactor: follow the common vocabulary of core and unified - #2669

Open
KartikP wants to merge 33 commits into
unified-model-interface-v2from
refactor/common-vocabulary
Open

KartikP wants to merge 33 commits into
unified-model-interface-v2from
refactor/common-vocabulary

Conversation

@KartikP

@KartikP KartikP commented Nov 13, 2026

Copy link
Copy Markdown
Collaborator

What changes

  • The vision adapter and its tests use the session arguments source, outputs and task.
  • The CLIP and Qwen registrations name the tower of each region, because a model with several extractors must name the extractor of each region.
  • The pins name the unified and core branch tips. They are temporary.

Why

Core and unified now use one vocabulary for sessions, tasks and declarations. This repository follows it, so a vision model runs the same experiments as every other model.

Scores

No score changes. Thirteen model and benchmark pairs gave identical scores on a cloud machine before the last Friends changes. The same check on the final commits is running. Its result will be added to this pull request.

Verification

CI installs core and unified at the branch tips, so the four branches are tested together.

Merge order

  1. core, then vision and language (squash).
  2. unified (merge commit).
  3. A pull request in each repository that replaces the temporary pins with the merged commits.

Do not merge before the owner approves. The pins in this branch are temporary.

The three arguments had three naming styles from three periods:
source, requested_output_channels and task_context. The session and
its two builders now take source, outputs and task, and the session
has the attributes outputs and task. The declarations on a benchmark
and on a subject do not change.
The pins name the tips of the refactor/common-vocabulary branches of unified and core so that the checks run against the four branches together. They are temporary.
The adapter makes, for each requested region in order, the calls of a
session for that region alone. A session with behavior and a region is
still refused.
in_channels and required_channels replace supported_modalities and
required_modalities; policy_in_channels and policy_out_channels
replace policy_inputs and policy_outputs. The word modality stays
only as an extractor key.
@KartikP

KartikP commented Nov 14, 2026

Copy link
Copy Markdown
Collaborator Author

retest this please

A refusal during the run, such as the legacy model refusing behavior
with a region in one look_at, now raises with a plain message.
…registers

The unified package registers clip-vit-b-32 and qwen2.5-vl-3b, and
brainscore.load_model loads those. The copies here were older versions
of the same registrations.
The majajhong2015 plugin folder is again as on master. The four -unified
identifiers are registered by the unified package, which imports the
data, metric and ceiling from this plugin.
A benchmark that left an intervention active was not caught here. The
entry point now calls the core release check before it returns.
The task key holds id() of the fitting set. Without a reference, a new
set at a freed address could match and skip the legacy refit.
The adapter refuses a session that asks for behavior with a region
before any look_at; this is an error of the run, not a declaration
mismatch.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant