choco-conoz

TwinLlama 3.2 1B

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: apache-2.0SHA-256 recorded for 7 of 8 filessafetensors
Quick answer: compatibility and sources

Can I run TwinLlama-3.2-1B 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.

TwinLlama-3.2-1B 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: c2a42864e37254f8d4b8d8e9be2cf67e20b1769538709b8802ddea9c407ac81c. 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-choco-conoz-twinllama-3-2-1b.
  • Open /artifact/hf-model-choco-conoz-twinllama-3-2-1b/files for this exact filenames, availability and any recorded SHA-256.
  • Open /evidence/artifacts/hf-model-choco-conoz-twinllama-3-2-1b for run-readiness evidence tied to that record; absent receipts stay unmeasured.
  • Open /api/artifacts/hf-model-choco-conoz-twinllama-3-2-1b/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).

choco-conoz/TwinLlama-3.2-1B

Content controls: not assessed.

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

Download availability is being checked.

Hashes recorded. Date not recorded.

FileTailleSHA-256SourceTélécharger
Weights
model.safetensors2.47 GB
c2a42864…407ac81cc2a42864e37254f8d4b8d8e9be2cf67e20b1769538709b8802ddea9c407ac81c
Download availability is being checked.File metadata
Tokenizer & config
config.json922 bytes
4e339b2a…6b0e279c4e339b2a44b7acdb8cfdb541f5e603e837b2339fcc13d31728cbbf026b0e279c
Download availability is being checked.File metadata
generation_config.json230 bytes
514e53e1…c2df84aa514e53e1ff454605970b2c9a578780de3776ee70af311eb252094eb7c2df84aa
Download availability is being checked.File metadata
special_tokens_map.json459 bytes
32f404d6…bb94c9b132f404d626cf7b1b6eea36c241ae7cbd6ec29c777a8701ea48c0fe9ebb94c9b1
Download availability is being checked.File metadata
tokenizer.json17.2 MB
6b9e4e7f…be39537b6b9e4e7fb171f92fd137b777cc2714bf87d11576700a1dcd7a399e7bbe39537b
Download availability is being checked.File metadata
tokenizer_config.json50.6 KB
c4d9433c…ede798e0c4d9433c811cb815f64adceee36fd5dc732e446a3e5543c4a794546fede798e0
Download availability is being checked.File metadata
Docs
.gitattributes1.57 KB—Download availability is being checked.File metadata
README.md352 bytes
fe022045…139da809fe0220450415c6be72e73462224753d9e792ed96c8f6188af6ba0f9d139da809
Download availability is being checked.File metadata

Vérifier un téléchargement

In the folder where you saved README.md, run:

macOS
shasum -a 256 -- 'README.md'
Linux
sha256sum -- 'README.md'
Windows
Get-FileHash -LiteralPath 'README.md' -Algorithm SHA256

Compare the result with the recorded SHA-256.