Join the conversation

Join the community of Machine Learners and AI enthusiasts.

Sign Up
Twu31 
posted an update 15 days ago
Post
109
How far has each EEG dataset on the Hub been checked?

BCI Report's open register has 487 dataset rows and 48 rows for models and papers, each with the furthest of five steps checked; for datasets: listed, read, traced, run, in the matrix. All 293 Hub rows are at step 1 (listed) so far: none of their files has been opened yet.

From a snapshot of the Hub on 19 October:
- 1,922 listings for 28 search terms and 20 tags; 737 are EEGDash mirrors, kept as one row.
- 368 uploads marked as brain-signal data after a classifier pass and a re-check. 146 of them carry no licence tag.
- 28 rows match an existing dataset by metadata. In 27 of them, the stated terms differ from the source's own.
- 15 match corpora that require a signed agreement, a request or a registration; 10 of those can be downloaded from the Hub without a request.

Matches use metadata only: names, sizes, counts. None of the matched uploads' files is downloaded, an uploader may hold permissions the register cannot see, and every row has a correction route, open to uploaders and dataset authors.

Write-up: https://huggingface.co/blog/Twu31/what-we-found-listing-the-eeg-datasets-on-hugging
Register: https://bci.report/datasets/register/
Data: https://bci.report/data/open-register-20261028.json

All 278 single Hub rows say checked 2026-10-19. The release is dated 10-28. One of your findings expired in between.

I re-read those 278 rows in open-register-20261028.json against the live API today (18:30Z):

  • 277 still resolve. illusion-brain/primate-spike-20ms (r-hf-0194, cc-by-4.0, 2.4 GB) now returns 401, the same answer a made-up repo name gets, so gone or private, no way to tell from outside.
  • 4 moved off the recorded revision_sha.
  • 0 changed gating.
  • jatshi/CAS_EEG (r-hf-0234) is one of the 118 single rows flagged licence_tag_absent. Commit d146444c on 10-26, "Fix dataset card metadata", added license: apache-2.0. The 10-28 release still lists it as absent.

So 1 of 118 resolved itself before publication, without the correction route.
That's the outcome a register exists to cause, and the register can't see it.

Do you plan to re-poll step 1 before each release, or does a row only move when someone writes in?

·

You're right about the date gap. The 28 October file preserves the 19 October Hub snapshot, while the current CAS_EEG card declares Apache-2.0. That row is historical, not a current license check. Your example makes a good case for rechecking step-1 metadata at release time and publishing a dated diff while retaining the frozen snapshot. Relying only on corrections wouldn't reliably catch changes like this.

In this post