factcircuit
FactCircuit: an auditable claim-and-evidence verification loop with immutable provenance, staged checks, bounded retrieval, and reproducible evaluation.
Visualizations of data usage across the archive.
Translation pending
DataTypeScript · JavaScriptGitHub @dandiOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Loading the full README. The saved excerpt is shown below.
Visualizations of data usage across the archive.
When deploying a fork that points at a different data repository, update the
BASE_URL constant near the top of src/plots.js:Read the full README ↗Visualizations of data usage across the archive.
Main webpage: https://usage.dandiarchive.org
When deploying a fork that points at a different data repository, update the
BASE_URL constant near the top of src/plots.js:
const BASE_URL = "https://raw.githubusercontent.com/myorg/myrepo/main";
npm install
npm run dev
npm test # unit tests (Vitest, in jsdom)
npm run test:coverage # the same, with a coverage report
npm run test:e2e # integration tests (Playwright, in Chromium)
npm run test:visual # screenshot comparison of the map against committed baselines
The unit tests cover the page's entry module (src/plots.ts) as well as its
helpers: tests/unit/plots-harness.ts loads the page's markup into jsdom,
stands in for Plotly and for the network, and drives the page through its
controls. Coverage from both the unit and the integration tests is reported
to Codecov; to see what the integration tests exercise in the browser, run
npm run test:e2e:coverage and then npm run coverage:integration.
by_region.tsv, and how to regenerate the table it reads them
with.