trl-internal-testing

tiny BloomForCausalLM

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

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.

FileTamanhoSHA-256OrigemBaixar
Weights
model.safetensors8.03 MB
ecb1065d…d456b9c1ecb1065d4b41859d9294ac0d73e8c5f1caafcf4c6ad5c8d97828b674d456b9c1
Download availability is being checked.File metadata
Tokenizer & config
config.json549 bytes
bac9d1b4…bd1aa5a1bac9d1b49be5a635ef7ec625fc18dcace1f1ea1db729f94c4e408057bd1aa5a1
Download availability is being checked.File metadata
generation_config.json116 bytes
fba968aa…21464c81fba968aa285a7ca422911d5ed0cca6499d03881c5c177893ce5d174e21464c81
Download availability is being checked.File metadata
special_tokens_map.json552 bytes
358c249e…880946c9358c249e2fb29060c6b73157d428853b0c48710deffc8ee670ab1013880946c9
Download availability is being checked.File metadata
tokenizer.json21.8 MB
d963066d…9a440e66d963066d6adae5034a1dc114c3ac444512de09928cf14ed4562ba94d9a440e66
Download availability is being checked.File metadata
tokenizer_config.json1.06 KB
9a5b1ee7…cf1cbb979a5b1ee7b43d7e8d3d2aedb08fa70a646594e101f8f937d51a0c76a7cf1cbb97
Download availability is being checked.File metadata
Docs
.gitattributes1.57 KB—Download availability is being checked.File metadata
README.md176 bytes—Download availability is being checked.File metadata

Verificar um download

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.