Skip to content

Address the archive's pre-namespace rows at the namespace they live at - #293

Open
borgr wants to merge 1 commit into
mainfrom
fix/hfopenllm-v2-legacy-namespace
Open

borgr wants to merge 1 commit into
mainfrom
fix/hfopenllm-v2-legacy-namespace

Conversation

@borgr

@borgr borgr commented Sep 10, 2026

Copy link
Copy Markdown
Collaborator

Two of the 4,576 HF Open LLM Leaderboard v2 archive rows carry a bare gpt2 with no publishing namespace. The org/model check rejected them, so raise_if_incomplete fired and the adapter produced nothing at all — 4,574 convertible rows lost to two bad names.

They are not junk rows. All four gpt2 rows in the archive report sha 607a30d783df, so the bare pair is the same weights as the openai-community/gpt2 pair beside it, but submitted separately and scoring differently (6.3910 against 6.5108 at bfloat16). Dropping them would lose two real measurements.

The repository those weights live at is namespaced now, and the datastore already holds data/hfopenllm_v2/openai-community/gpt2, so they are addressed there. The map is applied in both places the identity is derived, since convert_model and convert_models build the id and the directory independently and disagreeing would trip the path warning.

SourceRecordExclusion would have been the wrong mechanism. It records a source row that is not an evaluation, and these are evaluations.

gpt2 is the only org-less name in all 4,576 rows, so the map has one entry rather than a heuristic.

Two of the 4,576 archive rows carry a bare `gpt2` with no publishing
namespace, so the `org/model` check rejected them and the adapter raised on
incomplete conversion. That is a correct refusal, and it blocked the whole
backfill over two rows.

They are not junk rows. Both report sha 607a30d783df, the same weights as the
`openai-community/gpt2` rows beside them, submitted separately and scoring
differently, so dropping them would lose two real measurements. The
repository those weights live at is namespaced now, and the datastore already
holds `data/hfopenllm_v2/openai-community/gpt2`, so they are addressed there.

An exclusion would have been the wrong mechanism. That records a row which is
not an evaluation, and these are evaluations.
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