optimum-intel-internal-testing

tiny random deepseek ocr 2

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

Can I run tiny-random-deepseek-ocr-2 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-deepseek-ocr-2 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: df345f5a7b420af9c6bcfb1ee00fa28f2102f5544a20dc33ef8b8fad2ca83191. 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-deepseek-ocr-2.
  • Open /artifact/hf-model-optimum-intel-internal-testing-tiny-random-deepseek-ocr-2/files for this exact filenames, availability and any recorded SHA-256.
  • Open /evidence/artifacts/hf-model-optimum-intel-internal-testing-tiny-random-deepseek-ocr-2 for run-readiness evidence tied to that record; absent receipts stay unmeasured.
  • Open /api/artifacts/hf-model-optimum-intel-internal-testing-tiny-random-deepseek-ocr-2/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-deepseek-ocr-2

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.safetensors137.9 MB
df345f5a…2ca83191df345f5a7b420af9c6bcfb1ee00fa28f2102f5544a20dc33ef8b8fad2ca83191
Download availability is being checked.File metadata
Tokenizer & config
config.json3.66 KB
8ae6f5de…c838d1138ae6f5deb22d42e23e0e921b6a185a621ea42f906ae32a6e9a8a4eeac838d113
Download availability is being checked.File metadata
generation_config.json195 bytes
f35ec224…479ee45bf35ec2245fcb8cf4e0685d1e49b6788ea042c11953300807a6d9b494479ee45b
Download availability is being checked.File metadata
processor_config.json682 bytes
ae108469…6363cee7ae1084691a2c43b02101b0987ef77f5c927b6996ea0f704d8e47fbd56363cee7
Download availability is being checked.File metadata
tokenizer.json9.98 MB
a02f8fd5…0b55a8b4a02f8fd5228c90256bb4f6554c34a579d48f909e5beb232dc4afad870b55a8b4
Download availability is being checked.File metadata
tokenizer_config.json499 bytes
b88547a0…ebb796efb88547a05cd0565e21482a54c0dce9d9a3a80871d74f115c02ba251cebb796ef
Download availability is being checked.File metadata
Docs
.gitattributes1.52 KB—Download availability is being checked.File metadata
README.md3.22 KB—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.