unidepth-v2-vits14
lpiccinelliThis model has been pushed to the Hub using the PytorchModelHubMixin integration: - Library: https://github.com/lpiccinelli-eth/UniDepth - Docs: [More Information Needed]
From language to images, open weights to APIs. Understand capabilities and compare real costs.
Find the right engine for your next idea.
This model has been pushed to the Hub using the PytorchModelHubMixin integration: - Library: https://github.com/lpiccinelli-eth/UniDepth - Docs: [More Information Needed]
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
This model has been pushed to the Hub using the PytorchModelHubMixin integration: - Library: https://github.com/lpiccinelli-eth/UniK3D - Docs: [More Information Needed]
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
f2k_anything2real.safetensors is more 3D like version f2k_anything2real_a.safetensors based on f2k_anything2real.safetensors to adjust the realistic style I'm excited to share the new version of Anything2Real family, Anything2Real 2601 A. Anything2Real 2601 A is an adjusted version based on Anything2Real 2601 and remixed the layer weight of anything2real alpha. Anything2Real 2601 is kinda weak of eyes transformation and anything2real alpha is quite good at light and shadow but weak at color. Anything2Real 2601 A is a more balanced version between "respect to original" and "realistic environemnt" **Alpha Dataset**: lrzjason/Anything2Real_demo_dataset
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
LLäMmlein 1B is a German LLaMa model trained from scratch using our adapted Tinyllama codebase on the German portion of RedPajama V2. To enhance data quality, we additionally deduplicated the dataset on paragraph level and filtered it using a token-to-word ratio filter. The resulting dataset can be found here. You can use LLäMmlein with the `transformers` library. (Optional: install `flash-attn` to achieve highest efficiency.) In addition to the final model checkpoint, we publish intermediate checkpoints throughout the full training process as unique branches in this repository. A specific checkpoint can be loaded like this:
This is a German Tinyllama 1B language model trained from scratch using the Tinyllama codebase on the German portion of RedPajama V2. Find more details on our page and our preprint! We evaluated our results on the SuperGLEBer benchmark. Data Take Down
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
ModernGBERT 134M is a German ModernBERT language model with 134 million parameters and a native context length of up to 8,192 tokens. This model follows the same BERT-style architecture and training procedure as the ModernBERT codebase. ModernGBERT 134M has been pre-trained on 470 billion tokens from the German portion of RedPajama V2, a subset of the same training dataset used for our LLäMmlein decoder family. You can use ModernGBERT with the `transformers` library from version v4.48.0 onwards. (Optional: install `flash-attn` to achieve highest efficiency.) Since ModernGBERT 134M is a Masked Language Model (MLM), you can load it via `AutoModelForMaskedLM`. For downstream tasks such as classification, retrieval, or QA, fine-tune the model by following standard BERT fine-tuning recipes.
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
Experimental GGUF weights for running **GLM-5.3-Flash** on a normal PC with the LightTransport Strata fork: expert sidecars and a complete full model for a 128 GB host with a 16 GB NVIDIA GPU, a smaller REAP-224 model, and a complete REAP-50 model for a 64 GB host with a 16 GB AMD GPU. The sidecars requantize routed expert gate/up weights from IQ2_XS to Q2_K and down weights from IQ3_XXS to Q3_K; this changes weight values and is neither a lossless repack nor a fine-tune. REAP-224 keeps 224 of 288 routed experts per layer; REAP-50 keeps 144. Read the quality numbers below before choosing a model. Current measurements, setup for one and two GPUs, and context-length limits are in `docs/GLM53F_RELEASE.md` on the fork's `glm53f` branch; bringing it up on other hardware is described in `docs/GLM53F_NEW_HARDWARE.md`. The conversion recipe is `docs/GLM_RELEASE_Q2Q3.md`. **On a 128 GB machine use `GLM-5.3-Flash-Q23-FP8-assembled.gguf`** (or `experts-q23-fp8.gguf` with the Unsloth shards); **on a 64 GB machine use `reap50/GLM-5.3-Flash-REAP50-Q23-FP8-assembled.gguf`.** Their routed experts have the same types as Q23 (Q2_K gate/up, Q3_K down) but are quantized once, directly from the official FP8 weights, instead of from Unsloth's 2-bit experts (REAP-50: from its Q4_K_M experts). Measured against exact logits of the FP8 release on 16 held-out sequences (8,192 tokens):
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
基础档案已收录,详细介绍后续补充。可先查看厂商、分类与来源。
Basic profile indexed · More details to follow
Adjust provider, category or input/output filters. New models are added continuously.
Adjust monthly token usage to compare estimated API costs.
Uses collected, comparable USD-per-million-token rates. Snapshots exclude cache discounts, tiers, extra reasoning output and taxes. Check current source prices.
Separate input, output and cache rates, then estimate the same workload. Image, audio and video rates may use items, duration or resolution rather than tokens.
Not necessarily. Check each version’s license, commercial restrictions and policies. Self-hosting also incurs compute and maintenance costs.
Rankings depend on tasks, versions and methods. Compare accuracy, latency, reliability and costs on your own workload.