flair-bio

amplify-120m

Fill-mask
What we checked

File: check availability in Files.

Memory: Fit unknown. File size needed to check fit.

Last recorded run: none for this selected file.

License BFiles CRuns F

Recorded checks do not guarantee safety or performance on your computer.

See file checks and sources
Fill in missing wordssafetensorsLicense label: mitNeeds its own code to run

Download availability is being checked.

Hashes recorded. Date not recorded.

FileSizeSHA-256SourceDownload
Weights
model.safetensors473.1 MB
223177aa…51908b87223177aa7f17498f8e5c2039c0aa0f05c8f735cd3bc12058574c903a51908b87
Download availability is being checked.File metadata
Tokenizer & config
amplify.py22.9 KB-Download availability is being checked.File metadata
config.json799 bytes
9e860f9c…4b0492329e860f9ca3a21080fa132a8ca511e128d189ef4b16e0657c71be353a4b049232
Download availability is being checked.File metadata
tokenizer.json2.69 KB
21d81eaf…77dcacb321d81eaf438722068b5366f51707121de6d148801b0206fc7e991f2b77dcacb3
Download availability is being checked.File metadata
tokenizer.py16.5 KB-Download availability is being checked.File metadata
tokenizer_config.json573 bytes
dfcf6b9a…764b4713dfcf6b9a0ec48662879c79d292c8c9226bb2e2058a855adc2fdb3b9f764b4713
Download availability is being checked.File metadata
Docs
.gitattributes1.52 KB-Download availability is being checked.File metadata
README.md5.59 KB-Download availability is being checked.File metadata

Check a download

In the folder where you saved model.safetensors, run:

macOS
shasum -a 256 -- 'model.safetensors'
Linux
sha256sum -- 'model.safetensors'
Windows
Get-FileHash -LiteralPath 'model.safetensors' -Algorithm SHA256

Compare the result with the recorded SHA-256.

Additional model information
Quick answer: compatibility and sources

Can I run amplify-120m 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.

amplify-120m is an open-weights language model for masked-language modeling. 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: 223177aa7f17498f8e5c2039c0aa0f05c8f735cd3bc12058574c903a51908b87. 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.

Page text updated .

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