Super-squash history to reclaim storage

.gitattributes

@@ -0,0 +1,51 @@
+*.7z filter=lfs diff=lfs merge=lfs -text
+*.arrow filter=lfs diff=lfs merge=lfs -text
+*.bin filter=lfs diff=lfs merge=lfs -text
+*.bz2 filter=lfs diff=lfs merge=lfs -text
+*.ckpt filter=lfs diff=lfs merge=lfs -text
+*.ftz filter=lfs diff=lfs merge=lfs -text
+*.gz filter=lfs diff=lfs merge=lfs -text
+*.h5 filter=lfs diff=lfs merge=lfs -text
+*.joblib filter=lfs diff=lfs merge=lfs -text
+*.lfs.* filter=lfs diff=lfs merge=lfs -text
+*.mlmodel filter=lfs diff=lfs merge=lfs -text
+*.model filter=lfs diff=lfs merge=lfs -text
+*.msgpack filter=lfs diff=lfs merge=lfs -text
+*.npy filter=lfs diff=lfs merge=lfs -text
+*.npz filter=lfs diff=lfs merge=lfs -text
+*.onnx filter=lfs diff=lfs merge=lfs -text
+*.ot filter=lfs diff=lfs merge=lfs -text
+*.parquet filter=lfs diff=lfs merge=lfs -text
+*.pb filter=lfs diff=lfs merge=lfs -text
+*.pickle filter=lfs diff=lfs merge=lfs -text
+*.pkl filter=lfs diff=lfs merge=lfs -text
+*.pt filter=lfs diff=lfs merge=lfs -text
+*.pth filter=lfs diff=lfs merge=lfs -text
+*.rar filter=lfs diff=lfs merge=lfs -text
+*.safetensors filter=lfs diff=lfs merge=lfs -text
+saved_model/**/* filter=lfs diff=lfs merge=lfs -text
+*.tar.* filter=lfs diff=lfs merge=lfs -text
+*.tar filter=lfs diff=lfs merge=lfs -text
+*.tflite filter=lfs diff=lfs merge=lfs -text
+*.tgz filter=lfs diff=lfs merge=lfs -text
+*.wasm filter=lfs diff=lfs merge=lfs -text
+*.xz filter=lfs diff=lfs merge=lfs -text
+*.zip filter=lfs diff=lfs merge=lfs -text
+*.zst filter=lfs diff=lfs merge=lfs -text
+*tfevents* filter=lfs diff=lfs merge=lfs -text
+gemma-3-12b-it-qat-q4_0-q2_k_l.gguf filter=lfs diff=lfs merge=lfs -text
+gemma-3-12b-it-qat-q4_0-q3_k_l.gguf filter=lfs diff=lfs merge=lfs -text
+gemma-3-12b-it-qat-q4_0-q2_k_s.gguf filter=lfs diff=lfs merge=lfs -text
+gemma-3-12b-it-qat-q4_0-q3_k_m.gguf filter=lfs diff=lfs merge=lfs -text
+gemma-3-12b-it-qat-q4_0-q3_k_s.gguf filter=lfs diff=lfs merge=lfs -text
+gemma-3-12b-it-qat-q4_0-iq1_s.gguf filter=lfs diff=lfs merge=lfs -text
+gemma-3-12b-it-qat-q4_0-iq1_m.gguf filter=lfs diff=lfs merge=lfs -text
+gemma-3-12b-it-qat-q4_0-iq2_xs.gguf filter=lfs diff=lfs merge=lfs -text
+gemma-3-12b-it-qat-q4_0-iq2_xxs.gguf filter=lfs diff=lfs merge=lfs -text
+gemma-3-12b-it-qat-q4_0-iq2_s.gguf filter=lfs diff=lfs merge=lfs -text
+gemma-3-12b-it-qat-q4_0-iq2_m.gguf filter=lfs diff=lfs merge=lfs -text
+gemma-3-12b-it-qat-q4_0-iq3_xs.gguf filter=lfs diff=lfs merge=lfs -text
+gemma-3-12b-it-qat-q4_0-iq3_xxs.gguf filter=lfs diff=lfs merge=lfs -text
+gemma-3-12b-it-qat-q4_0-iq3_s.gguf filter=lfs diff=lfs merge=lfs -text
+gemma-3-12b-it-qat-q4_0-iq3_m.gguf filter=lfs diff=lfs merge=lfs -text
+gemma-3-12b-it-qat-q4_0.imatrix filter=lfs diff=lfs merge=lfs -text

README.md

@@ -0,0 +1,448 @@
+---
+license: gemma
+pipeline_tag: image-text-to-text
+extra_gated_heading: Access Gemma on Hugging Face
+extra_gated_prompt: >-
+  To access Gemma on Hugging Face, you’re required to review and agree to
+  Google’s usage license. To do this, please ensure you’re logged in to Hugging
+  Face and click below. Requests are processed immediately.
+extra_gated_button_content: Acknowledge license
+base_model: google/gemma-3-12b-it
+tags:
+- gemma
+- gemma3
+---
+
+
+
+# <span style="color: #7FFF7F;">Gemma-3 12B Instruct GGUF Models</span>
+> [!Note]
+> Experimetal requantization!! I wanted to test if the QAT model requantized performs better than the bf16 model quantized to the same bit level.
+>
+> I have created a imatrix files from the google original QAT Q4_0 quantized model. This imatrix is then used to recompress the model to lower bit quants
+>
+> Please leave feedback.
+>
+> I tested with  the 4b model quantized from bf16 and one requantized from the QAT Q4_0 model. Both quantized with same tensor quants
+
+My results :
+
+```
+python3 ~/code/GGUFModelBuilder/perp_test_2_files.py ./gemma-3-4b-it-qat-q4_0-q3_k_l.gguf ./google_gemma-3-4b-it-q3_k_l.gguf 
+
+Testing model: gemma-3-4b-it-qat-q4_0-q3_k_l.gguf
+Running: llama.cpp/llama-perplexity -m gemma-3-4b-it-qat-q4_0-q3_k_l.gguf -f perplexity_test_data.txt --ctx-size 256 --ppl-stride 32 --chunks 1 --threads 4
+[✓] Perplexity: 4.0963 (Time: 284.70s)
+
+Testing model: google_gemma-3-4b-it-q3_k_l.gguf
+Running: llama.cpp/llama-perplexity -m google_gemma-3-4b-it-q3_k_l.gguf -f perplexity_test_data.txt --ctx-size 256 --ppl-stride 32 --chunks 1 --threads 4
+[✓] Perplexity: 4.5557 (Time: 287.15s)
+
+=== Comparison Results ===
+Model 1: gemma-3-4b-it-qat-q4_0-q3_k_l.gguf - Perplexity: 4.10 (Time: 284.70s)
+Model 2: google_gemma-3-4b-it-q3_k_l.gguf - Perplexity: 4.56 (Time: 287.15s)
+
+Winner: gemma-3-4b-it-qat-q4_0-q3_k_l.gguf (Difference: 0.46)
+```
+
+A different test :
+
+Asking both models to :  write some .net code to test if a website is using quantum safe encryption
+
+And then asking Deepseek-R1 to evaluate :
+
+Evaluation of the Two Models' Outputs
+
+Both models attempted to solve the problem of detecting quantum-safe encryption, but the QAT q4_0 model's code is significantly better for the following reasons:
+1. Technical Accuracy
+
+    QAT q4_0 Model:
+
+        Checks both TLS version and cipher suites, which are critical for assessing quantum resistance. While the implementation has flaws (e.g., assuming TLS version is exposed in HTTP headers), the approach aligns with security best practices.
+
+        Explicitly acknowledges limitations (e.g., "not a definitive test") and avoids overpromising.
+
+    BF16 Model:
+
+        Relies on checking for a non-standard TLS/1.3 header, which does not exist in HTTP responses. TLS version is part of the SSL/TLS handshake and cannot be retrieved via HttpClient headers.
+
+        Contains incorrect logic (e.g., client.GetAwaiter().GetResult(null) is nonsensical and throws runtime errors).
+
+2. Code Quality
+
+    QAT q4_0 Model:
+
+        Uses modern async/await patterns for non-blocking I/O.
+
+        Separates concerns into methods (CheckTLSVersionAsync, CheckCipherSuiteAsync).
+
+        Includes robust error handling and logging.
+
+    BF16 Model:
+
+        Uses blocking synchronous code (GetAwaiter().GetResult()), which violates .NET best practices and risks deadlocks.
+
+        Poorly structured (e.g., redundant using blocks, unclear variable names like result).
+
+3. Security Relevance
+
+    QAT q4_0 Model:
+
+        Focuses on cipher suites, which are closer to the actual indicators of quantum resistance (e.g., AES-256-GCM). While not truly quantum-safe, these are stronger than outdated algorithms.
+
+        Mentions the need to update cipher lists based on NIST guidelines.
+
+    BF16 Model:
+
+        Misleadingly claims to check for "AES-256-CBC" (a deprecated cipher mode) but never implements it.
+
+        Fails to address cipher suites entirely, rendering the check meaningless.
+
+4. Realism
+
+    QAT q4_0 Model:
+
+        Acknowledges the complexity of quantum-safe detection and clarifies that HTTP-based checks are insufficient. This aligns with real-world security practices.
+
+    BF16 Model:
+
+        Implies that checking for TLS 1.3 guarantees quantum safety, which is false. TLS 1.3 uses classical cryptography and is not inherently quantum-resistant.
+
+5. Usability
+
+    QAT q4_0 Model:
+
+        Provides clear console output (e.g., "No quantum-resistant cipher suites detected").
+
+        Includes a working Main method with an example URL.
+
+    BF16 Model:
+
+        Fails to compile due to syntax errors (e.g., client.GetAwaiter().GetResult(null) is invalid).
+
+        Lacks meaningful output (e.g., no details about why a site is deemed insecure).
+
+Critical Flaws in Both Models
+
+    Header Misuse: Both models incorrectly assume TLS version and cipher suites are exposed in HTTP headers (e.g., Sec-Cipher). In reality, this data is part of the SSL/TLS handshake and requires low-level inspection (e.g., using SslStream or libraries like BouncyCastle).
+
+    Quantum-Safe Misunderstanding: Neither code checks for post-quantum algorithms (e.g., CRYSTALS-Kyber). Current TLS 1.3 cipher suites are not quantum-safe, so both models provide false positives.
+
+Final Verdict
+
+The QAT q4_0 model's code is superior because it:
+
+    Follows better coding practices (async/await, error handling).
+
+    Attempts a more relevant security analysis (TLS + cipher suites).
+
+    Explicitly acknowledges limitations.
+
+However, both models fail to solve the original problem due to fundamental misunderstandings of TLS/SSL mechanics. For a production-grade solution, direct inspection of the TLS handshake (e.g., via SslStream) and support for post-quantum algorithms would be required.
+
+
+Overall the perp difference was small (my test set was also small) and running the Deepseek test produced different results on subsequent runs . So I can not come to a definite conclusion. But I would say is worth investigating further.
+
+
+
+
+# Gemma 3 model card
+
+**Model Page**: [Gemma](https://ai.google.dev/gemma/docs/core)
+
+> [!Note]
+> This repository corresponds to the 12 **instruction-tuned** version of the Gemma 3 model in GGUF format using Quantization Aware Training (QAT).
+> The GGUF corresponds to Q4_0 quantization.
+>
+> Thanks to QAT, the model is able to preserve similar quality as `bfloat16` while significantly reducing the memory requirements
+> to load the model.
+>
+> You can find the half-precision version [here](https://huggingface.co/google/gemma-3-12b-it).
+
+
+**Resources and Technical Documentation**:
+
+* [Gemma 3 Technical Report][g3-tech-report]
+* [Responsible Generative AI Toolkit][rai-toolkit]
+* [Gemma on Kaggle][kaggle-gemma]
+* [Gemma on Vertex Model Garden][vertex-mg-gemma3]
+
+**Terms of Use**: [Terms][terms]
+
+**Authors**: Google DeepMind
+
+## Model Information
+
+Summary description and brief definition of inputs and outputs.
+
+### Description
+
+Gemma is a family of lightweight, state-of-the-art open models from Google,
+built from the same research and technology used to create the Gemini models.
+Gemma 3 models are multimodal, handling text and image input and generating text
+output, with open weights for both pre-trained variants and instruction-tuned
+variants. Gemma 3 has a large, 128K context window, multilingual support in over
+140 languages, and is available in more sizes than previous versions. Gemma 3
+models are well-suited for a variety of text generation and image understanding
+tasks, including question answering, summarization, and reasoning. Their
+relatively small size makes it possible to deploy them in environments with
+limited resources such as laptops, desktops or your own cloud infrastructure,
+democratizing access to state of the art AI models and helping foster innovation
+for everyone.
+
+### Inputs and outputs
+
+-   **Input:**
+    -  Text string, such as a question, a prompt, or a document to be summarized
+    -  Images, normalized to 896 x 896 resolution and encoded to 256 tokens
+       each
+    -  Total input context of 128K tokens for the 4B, 12B, and 27B sizes, and
+       32K tokens for the 1B size
+
+-   **Output:**
+    -   Generated text in response to the input, such as an answer to a
+        question, analysis of image content, or a summary of a document
+    -   Total output context of 8192 tokens
+
+### Usage
+
+Below, there are some code snippets on how to get quickly started with running the model.
+
+**llama.cpp (text-only)**
+
+```sh
+./llama-cli -hf google/gemma-3-27b-it-qat-q4_0-gguf -p "Write a poem about the Kraken."
+```
+
+**llama.cpp (image input)**
+
+```sh
+wget https://github.com/bebechien/gemma/blob/main/surprise.png?raw=true -O ~/Downloads/surprise.png
+./llama-gemma3-cli -hf google/gemma-3-12b-it-qat-q4_0-gguf -p "Describe this image." --image ~/Downloads/surprise.png
+```
+
+**ollama (text only)**
+
+Using GGUFs with Ollama via Hugging Face does not support image inputs at the moment. Please check the [docs on running gated repositories](https://huggingface.co/docs/hub/en/ollama#run-private-ggufs-from-the-hugging-face-hub).
+
+
+```sh
+ollama run hf.co/google/gemma-3-12b-it-qat-q4_0-gguf
+```
+
+### Citation
+
+```none
+@article{gemma_2025,
+    title={Gemma 3},
+    url={https://goo.gle/Gemma3Report},
+    publisher={Kaggle},
+    author={Gemma Team},
+    year={2025}
+}
+```
+
+## Model Data
+
+Data used for model training and how the data was processed.
+
+### Training Dataset
+
+These models were trained on a dataset of text data that includes a wide variety
+of sources.  the 12B model was
+trained with 12 trillion tokens, 4B model was trained with 4 trillion tokens and
+1B with 2 trillion tokens. Here are the key components:
+
+-   Web Documents: A diverse collection of web text ensures the model is
+    exposed to a broad range of linguistic styles, topics, and vocabulary. The
+    training dataset includes content in over 140 languages.
+-   Code: Exposing the model to code helps it to learn the syntax and
+    patterns of programming languages, which improves its ability to generate
+    code and understand code-related questions.
+-   Mathematics: Training on mathematical text helps the model learn logical
+    reasoning, symbolic representation, and to address mathematical queries.
+-   Images: A wide range of images enables the model to perform image
+    analysis and visual data extraction tasks.
+
+The combination of these diverse data sources is crucial for training a powerful
+multimodal model that can handle a wide variety of different tasks and data
+formats.
+
+### Data Preprocessing
+
+Here are the key data cleaning and filtering methods applied to the training
+data:
+
+-   CSAM Filtering: Rigorous CSAM (Child Sexual Abuse Material) filtering
+    was applied at multiple stages in the data preparation process to ensure
+    the exclusion of harmful and illegal content.
+-   Sensitive Data Filtering: As part of making Gemma pre-trained models
+    safe and reliable, automated techniques were used to filter out certain
+    personal information and other sensitive data from training sets.
+-   Additional methods: Filtering based on content quality and safety in
+    line with [our policies][safety-policies].
+
+## Implementation Information
+
+Details about the model internals.
+
+### Hardware
+
+Gemma was trained using [Tensor Processing Unit (TPU)][tpu] hardware (TPUv4p,
+TPUv5p and TPUv5e). Training vision-language models (VLMS) requires significant
+computational power. TPUs, designed specifically for matrix operations common in
+machine learning, offer several advantages in this domain:
+
+-   Performance: TPUs are specifically designed to handle the massive
+    computations involved in training VLMs. They can speed up training
+    considerably compared to CPUs.
+-   Memory: TPUs often come with large amounts of high-bandwidth memory,
+    allowing for the handling of large models and batch sizes during training.
+    This can lead to better model quality.
+-   Scalability: TPU Pods (large clusters of TPUs) provide a scalable
+    solution for handling the growing complexity of large foundation models.
+    You can distribute training across multiple TPU devices for faster and more
+    efficient processing.
+-   Cost-effectiveness: In many scenarios, TPUs can provide a more
+    cost-effective solution for training large models compared to CPU-based
+    infrastructure, especially when considering the time and resources saved
+    due to faster training.
+-   These advantages are aligned with
+    [Google's commitments to operate sustainably][sustainability].
+
+### Software
+
+Training was done using [JAX][jax] and [ML Pathways][ml-pathways].
+
+JAX allows researchers to take advantage of the latest generation of hardware,
+including TPUs, for faster and more efficient training of large models. ML
+Pathways is Google's latest effort to build artificially intelligent systems
+capable of generalizing across multiple tasks. This is specially suitable for
+foundation models, including large language models like these ones.
+
+Together, JAX and ML Pathways are used as described in the
+[paper about the Gemini family of models][gemini-2-paper]; *"the 'single
+controller' programming model of Jax and Pathways allows a single Python
+process to orchestrate the entire training run, dramatically simplifying the
+development workflow."*
+
+
+### Intended Usage
+
+Open vision-language models (VLMs) models have a wide range of applications
+across various industries and domains. The following list of potential uses is
+not comprehensive. The purpose of this list is to provide contextual information
+about the possible use-cases that the model creators considered as part of model
+training and development.
+
+-   Content Creation and Communication
+    -   Text Generation: These models can be used to generate creative text
+        formats such as poems, scripts, code, marketing copy, and email drafts.
+    -   Chatbots and Conversational AI: Power conversational interfaces
+        for customer service, virtual assistants, or interactive applications.
+    -   Text Summarization: Generate concise summaries of a text corpus,
+        research papers, or reports.
+    -   Image Data Extraction: These models can be used to extract,
+        interpret, and summarize visual data for text communications.
+-   Research and Education
+    -   Natural Language Processing (NLP) and VLM Research: These
+        models can serve as a foundation for researchers to experiment with VLM
+        and NLP techniques, develop algorithms, and contribute to the
+        advancement of the field.
+    -   Language Learning Tools: Support interactive language learning
+        experiences, aiding in grammar correction or providing writing practice.
+    -   Knowledge Exploration: Assist researchers in exploring large
+        bodies of text by generating summaries or answering questions about
+        specific topics.
+
+### Limitations
+
+-   Training Data
+    -   The quality and diversity of the training data significantly
+        influence the model's capabilities. Biases or gaps in the training data
+        can lead to limitations in the model's responses.
+    -   The scope of the training dataset determines the subject areas
+        the model can handle effectively.
+-   Context and Task Complexity
+    -   Models are better at tasks that can be framed with clear
+        prompts and instructions. Open-ended or highly complex tasks might be
+        challenging.
+    -   A model's performance can be influenced by the amount of context
+        provided (longer context generally leads to better outputs, up to a
+        certain point).
+-   Language Ambiguity and Nuance
+    -   Natural language is inherently complex. Models might struggle
+        to grasp subtle nuances, sarcasm, or figurative language.
+-   Factual Accuracy
+    -   Models generate responses based on information they learned
+        from their training datasets, but they are not knowledge bases. They
+        may generate incorrect or outdated factual statements.
+-   Common Sense
+    -   Models rely on statistical patterns in language. They might
+        lack the ability to apply common sense reasoning in certain situations.
+
+### Ethical Considerations and Risks
+
+The development of vision-language models (VLMs) raises several ethical
+concerns. In creating an open model, we have carefully considered the following:
+
+-   Bias and Fairness
+    -   VLMs trained on large-scale, real-world text and image data can
+        reflect socio-cultural biases embedded in the training material. These
+        models underwent careful scrutiny, input data pre-processing described
+        and posterior evaluations reported in this card.
+-   Misinformation and Misuse
+    -   VLMs can be misused to generate text that is false, misleading,
+        or harmful.
+    -   Guidelines are provided for responsible use with the model, see the
+        [Responsible Generative AI Toolkit][rai-toolkit].
+-   Transparency and Accountability:
+    -   This model card summarizes details on the models' architecture,
+        capabilities, limitations, and evaluation processes.
+    -   A responsibly developed open model offers the opportunity to
+        share innovation by making VLM technology accessible to developers and
+        researchers across the AI ecosystem.
+
+Risks identified and mitigations:
+
+-   **Perpetuation of biases**: It's encouraged to perform continuous
+    monitoring (using evaluation metrics, human review) and the exploration of
+    de-biasing techniques during model training, fine-tuning, and other use
+    cases.
+-   **Generation of harmful content**: Mechanisms and guidelines for content
+    safety are essential. Developers are encouraged to exercise caution and
+    implement appropriate content safety safeguards based on their specific
+    product policies and application use cases.
+-   **Misuse for malicious purposes**: Technical limitations and developer
+    and end-user education can help mitigate against malicious applications of
+    VLMs. Educational resources and reporting mechanisms for users to flag
+    misuse are provided. Prohibited uses of Gemma models are outlined in the
+    [Gemma Prohibited Use Policy][prohibited-use].
+-   **Privacy violations**: Models were trained on data filtered for removal
+    of certain personal information and other sensitive data. Developers are
+    encouraged to adhere to privacy regulations with privacy-preserving
+    techniques.
+
+### Benefits
+
+At the time of release, this family of models provides high-performance open
+vision-language model implementations designed from the ground up for
+responsible AI development compared to similarly sized models.
+
+Using the benchmark evaluation metrics described in this document, these models
+have shown to provide superior performance to other, comparably-sized open model
+alternatives.
+
+[g3-tech-report]: https://goo.gle/Gemma3Report
+[rai-toolkit]: https://ai.google.dev/responsible
+[kaggle-gemma]: https://www.kaggle.com/models/google/gemma-3
+[vertex-mg-gemma3]: https://console.cloud.google.com/vertex-ai/publishers/google/model-garden/gemma3
+[terms]: https://ai.google.dev/gemma/terms
+[safety-policies]: https://ai.google/static/documents/ai-responsibility-update-published-february-2025.pdf
+[prohibited-use]: https://ai.google.dev/gemma/prohibited_use_policy
+[tpu]: https://cloud.google.com/tpu/docs/intro-to-tpu
+[sustainability]: https://sustainability.google/operating-sustainably/
+[jax]: https://github.com/jax-ml/jax
+[ml-pathways]: https://blog.google/technology/ai/introducing-pathways-next-generation-ai-architecture/
+[sustainability]: https://sustainability.google/operating-sustainably/
+[gemini-2-paper]: https://arxiv.org/abs/2312.11805

gemma-3-12b-it-qat-q4_0-iq1_m.gguf

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:2b9f5cf15302deeb24ae7fdc5a6333887c11fe8afca5a9ec285d620a851f0e2f
+size 3613438688

gemma-3-12b-it-qat-q4_0-iq1_s.gguf

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f42431d0a2fc006dcc504a6e9c2c4b50c7c677d22e213270414cceff33dcb718
+size 3454186208

gemma-3-12b-it-qat-q4_0-iq2_m.gguf

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b1d6688f374eade2fd3383117c38ce5698d86250c16e82fc871884d0531df8f2
+size 4858704608

gemma-3-12b-it-qat-q4_0-iq2_s.gguf

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ced85007810538cfad8b21c47b01f2efdf3232e8c9e499a42938de09decc417a
+size 4646367968

gemma-3-12b-it-qat-q4_0-iq2_xs.gguf

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d1c1055f3121b1191e4666aa3143795fc3455bc2912d2bf1faa7fd88ba75e46e
+size 4114789088

gemma-3-12b-it-qat-q4_0-iq2_xxs.gguf

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4c077cf766bbaab2451b7d05ffda0e94fadb7e2bfd55dba1ed40389b19b66815
+size 3878859488

gemma-3-12b-it-qat-q4_0-iq3_m.gguf

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f9d64f4d448663f1e42184fd85ea95da3387de79ad4565cdf67d74ef93075917
+size 5655519968

gemma-3-12b-it-qat-q4_0-iq3_s.gguf

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dae1a6f1dd2b797ab95b7dd2b1f2a3f7491dc1525b1561f9e077d5e0bbec1996
+size 5458113248

gemma-3-12b-it-qat-q4_0-iq3_xs.gguf

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9772bc0c90bd2337fec4d75cac2d4b77031f1836b1868c0795eb1c2763f8fe17
+size 5205963488

gemma-3-12b-it-qat-q4_0-iq3_xxs.gguf

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ce0a1be735aabc4423ca586a606ac43e53748c1fbe46e6caf0449fb100c59680
+size 4918424288

gemma-3-12b-it-qat-q4_0-q2_k_s.gguf

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0a238297c6b4bb016cfb751090d410529f572ec2e5ed4d72a7368cb36930d71f
+size 4448408288

gemma-3-12b-it-qat-q4_0-q3_k_m.gguf

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a61126ab2f6dfdd0da1908f56b0df765b53d60bbeaa8d1e2421f457e216163de
+size 6008615648

gemma-3-12b-it-qat-q4_0-q3_k_s.gguf

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9914658fb5ccebe3c2a872ee660b0f660030a85b397086bdd3696a39a59aa48c
+size 5458113248

gemma-3-12b-it-qat-q4_0.imatrix

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cc2966da9eda17ebf183aa04927ff04dbdf1a8076b9bfd8686e3a3116ae16f9b
+size 7433132