trl-internal-testing

tiny GPTNeoXForCausalLM

Text generation

This receipt records checks for this exact file; it does not prove safety or that it will run on your device. Read the receipt

Model details
text generationLicense: unknownSHA-256 recorded for 6 of 8 filessafetensors
Quick answer: compatibility and sources

Can I run tiny-GPTNeoXForCausalLM on my computer?

It depends on your memory, processor, file format and runtime. A download is not confirmed by the current file evidence; inspect the file record before trying it. A file-size fit is an estimate, not a successful run or speed promise. Read the license before use.

tiny-GPTNeoXForCausalLM is an open-weights language model for text generation. Model weights are learned parameters; a runtime loads them. A hosted file is an individual file Hugging Bay can serve. SHA-256 identifies exact file bytes. The availability date above applies to this file record, not the upstream metadata update date.

As of the recorded file availability check on .

Recorded SHA-256 for model.safetensors: bcaeafe7054c6015848b3b28bdb1aa317a2031a9e90c5680581292b77a1abb2a. Exact file evidence · Machine-readable source facts · Run evidence and any recorded receipts. A checksum fingerprints only the named file bytes; it does not prove safety, quality, a complete multi-file selection or a successful run.

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

Model metadata: As of at the model source. Popularity counters are source-reported, not measured by Hugging Bay. Availability checked .

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 hf-model-trl-internal-testing-tiny-gptneoxforcausallm.
  • Open /artifact/hf-model-trl-internal-testing-tiny-gptneoxforcausallm/files for this exact filenames, availability and any recorded SHA-256.
  • Open /evidence/artifacts/hf-model-trl-internal-testing-tiny-gptneoxforcausallm for run-readiness evidence tied to that record; absent receipts stay unmeasured.
  • Open /api/artifacts/hf-model-trl-internal-testing-tiny-gptneoxforcausallm/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

  • File availability check:
  • 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.

Requirements and source record

Try browser chat with a small demo model (a separate model; device support is checked before loading).

trl-internal-testing/tiny-GPTNeoXForCausalLM

Content controls: not assessed.

The catalog lists this model for generating text. Catalog sources: task, cardMetadata.pipelineTag.

Download availability is being checked.

Hashes recorded. Date not recorded.

FileGrößeSHA-256QuelleHerunterladen
Weights
model.safetensors1.62 MB
bcaeafe7…7a1abb2abcaeafe7054c6015848b3b28bdb1aa317a2031a9e90c5680581292b77a1abb2a
Download availability is being checked.File metadata
Tokenizer & config
config.json773 bytes
67845017…ef65c705678450174f75ff50406c1cec01816d080d8d80e2a3b652b35347fc06ef65c705
Download availability is being checked.File metadata
generation_config.json111 bytes
4f79b99f…226758bc4f79b99f00243d2ad2da2ba43cd3366b205682a1f91e54c3218b5c63226758bc
Download availability is being checked.File metadata
special_tokens_map.json441 bytes
10b8c885…1d3e9c0c10b8c8852c1e1f70b54d9aff61728408c28971c0e97a6c5a7b2debbd1d3e9c0c
Download availability is being checked.File metadata
tokenizer.json3.56 MB
d4c0d99d…b0c2f825d4c0d99d84af59e9126913fafe5210822963e9a3065ee43e6833b358b0c2f825
Download availability is being checked.File metadata
tokenizer_config.json4.86 KB
127569e1…0428a436127569e128babd6d92f16d83ac0c440bb9803fffcc58e8590d91e3c90428a436
Download availability is being checked.File metadata
Docs
.gitattributes1.52 KB—Download availability is being checked.File metadata
README.md178 bytes—Download availability is being checked.File metadata

Einen Download prüfen

In the folder where you saved config.json, run:

macOS
shasum -a 256 -- 'config.json'
Linux
sha256sum -- 'config.json'
Windows
Get-FileHash -LiteralPath 'config.json' -Algorithm SHA256

Compare the result with the recorded SHA-256.