rad chestct dataset 6406114
License: unknownModel record details
This model record is still being checked. A file download does not establish complete-model verification.
- Verification status
- pending
- Scan status
- pending
- License metadata
- unknown
- Artifact type
- dataset
- Recorded total
- not recorded
- Upstream source
- https://zenodo.org/records/6406114
Public metadata JSON Resolve this artifact
Complete-kit status and hardware fit require their own evidence.
Quick answer: compatibility and sources
What is rad chestct dataset 6406114, and can I use it on my computer?
It depends on the exact file, format, license and software you use. Read the metadata and file evidence below. A catalog record does not establish that Hugging Bay serves the files or that a runtime has been tested. Treat unknown availability or checks as unconfirmed.
Model weights are learned parameters; a runtime is the software that loads them. RAM is working memory, separate from disk space for downloaded files.
Page-copy provenance: the revision record names apps/web/server.mjs, apps/web/lib/aeo-page.mjs, apps/web/lib/api-status-contract.mjs, apps/web/lib/agent-readable.mjs, apps/web/lib/docs-hub-model.mjs, apps/web/lib/compare-pages.mjs and commit 8871bab84e1cf80aea1686a944ec335078a6c036. This identifies the text source; it is not a model test receipt. A SHA-256 checksum fingerprints file bytes, not safety or answer quality. See what file verification checks. Run receipts, when present, belong to a specific model file and setup; this page asserts no model test.
Updated · Page-copy source revision 8871bab84e1cf80aea1686a944ec335078a6c036 · Source files: apps/web/lib/model-page-template.mjs, apps/web/lib/model-page-v3.mjs, apps/web/lib/aeo-page.mjs · Full revision record
Key facts
- Catalog record
- Summarizes upstream metadata; it is not itself a download or run receipt.
- File evidence
- Lists exact filenames, availability and any recorded SHA-256 for individual files.
- Run evidence
- Reports measured results only when a receipt exists for named file bytes and a setup; otherwise unmeasured.
- Checksum scope
- SHA-256 fingerprints one file’s bytes; it does not prove safety, quality or a multi-file bundle.
Evidence you can inspect (plain text)
- This page’s quick answer names the file record for zenodo-6406114.
- Open /artifact/zenodo-6406114/files for this exact filenames, availability and any recorded SHA-256.
- Open /evidence/artifacts/zenodo-6406114 for run-readiness evidence tied to that record; absent receipts stay unmeasured.
- Open /api/artifacts/zenodo-6406114/card.md for machine-readable source facts (not a runtime test).
- A matching checksum on this page fingerprints only the named bytes shown in file evidence.
Unmeasured states are stated explicitly; this page does not invent run scores or compatibility guarantees.
Which date applies to which fact
- Committed page-copy sources:
- Upstream model metadata: Dates on artifact records when shown; not implied by page-copy revision
- Run receipts: Only on /evidence pages when recorded; otherwise unmeasured
Page-copy revision (Updated line above) identifies committed text sources, not upstream model edits or test outcomes.