Buy me a coffee if you like this project ;)

GGUF Format model files for This project.

GGUF is a format based on the existing GGJT, but makes a few changes to the format to make it more extensible and easier to use. The following features are desired:

Single-file deployment: they can be easily distributed and loaded, and do not require any external files for additional information. Extensible: new features can be added to GGML-based executors/new information can be added to GGUF models without breaking compatibility with existing models. mmap compatibility: models can be loaded using mmap for fast loading and saving. Easy to use: models can be easily loaded and saved using a small amount of code, with no need for external libraries, regardless of the language used. Full information: all information needed to load a model is contained in the model file, and no additional information needs to be provided by the user. The key difference between GGJT and GGUF is the use of a key-value structure for the hyperparameters (now referred to as metadata), rather than a list of untyped values. This allows for new metadata to be added without breaking compatibility with existing models, and to annotate the model with additional information that may be useful for inference or for identifying the model.

User: Tell me story about what is an quantization and what do we need to build. I'll try to give a layman-friendly explanation of quantization in the context of a hypothetical scenario for building a simple musical instrument. Imagine we want to create a device that produces different musical notes when interacting with it in a particular way, similar to striking a piano key. We'll call this our 'Quantized Note Generator'.

In a real piano, the precise frequency of a note produced depends on how hard you press a key (known as 'dynamic playing'), the exact spot on the key where contact occurs ('timbre variations'), and other nuances of performance. However, for