optimum-intel-internal-testing

tiny random hunyuan v1 dense

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
generalLicense: apache-2.0Hashes recordedsafetensors
Quick answer: compatibility and sources

Can I run tiny-random-hunyuan-v1-dense 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-random-hunyuan-v1-dense is an open-weights language model for general. 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: df6c63542b7e3acf43eea5b29ccc38687ab6d2f2949210348eb725ac9f8a2325. 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-optimum-intel-internal-testing-tiny-random-hunyuan-v1-dense.
  • Open /artifact/hf-model-optimum-intel-internal-testing-tiny-random-hunyuan-v1-dense/files for this exact filenames, availability and any recorded SHA-256.
  • Open /evidence/artifacts/hf-model-optimum-intel-internal-testing-tiny-random-hunyuan-v1-dense for run-readiness evidence tied to that record; absent receipts stay unmeasured.
  • Open /api/artifacts/hf-model-optimum-intel-internal-testing-tiny-random-hunyuan-v1-dense/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
optimum-intel-internal-testing/tiny-random-hunyuan-v1-dense

Content controls: not assessed.

The catalog does not give enough information to describe what this model is for. Catalog sources: license, cardMetadata.license.

Download availability is being checked.

Hashes recorded. Date not recorded.

FileGrößeSHA-256QuelleHerunterladen
Weights
model.safetensors452.6 KB
df6c6354…9f8a2325df6c63542b7e3acf43eea5b29ccc38687ab6d2f2949210348eb725ac9f8a2325
Download availability is being checked.File metadata
Tokenizer & config
config.json703 bytes
3e867c77…a0246e2d3e867c77864921929de9c4f98ca282724f8d1140f6de1118b5097d87a0246e2d
Download availability is being checked.File metadata
generation_config.json132 bytes
ff76f419…eddfa21eff76f419b2696258be065ebc917218a15df2b13e8a1f5854b4323bd4eddfa21e
Download availability is being checked.File metadata
special_tokens_map.json95 bytes
0655d856…e03f7d4c0655d856e7dd462048486aac66d4247753e5cab12480baeb9f4e8f7fe03f7d4c
Download availability is being checked.File metadata
tokenizer_config.json238 bytes
88c706b5…8b11ae9e88c706b5df1ef8c56a070356eda8766033e35c24e80c2dbdc68893e48b11ae9e
Download availability is being checked.File metadata
tokenizer.json5.76 KB
17f27441…2ce1537417f274414c6d2c5132b8ce9d9e8456b5c5271c0589ecb3dfd3e7dbcf2ce15374
Download availability is being checked.File metadata
Docs
README.md1.59 KB
eec34125…2deb5b2aeec341254935b5950585d9b1be37ed0d38a7b3f16a5af37803eca4742deb5b2a
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.