How cocktailpeanut/llamacpp.pinokio works
Main Components
a. Installation Layer
• Two sub-components:
• Model Installer (connecting to install/models)
• Binary Installer (connecting to install/bin)
b. Model Management Layer
• Different model categories:
• LLaMa Models
• Falcon Models
• Vicuna Models
• Orca Models
c. Integration Layer
• Pinokio Integration component (connected to pinokio.js)
• Script Execution Engine (connected to index.js)
Component Relationships
• User Interface → Installation Manager
• Installation Manager → Model Registry
• Model Registry → LLaMa.cpp Runtime
• Pinokio Integration → Script Execution Engine
• Script Execution Engine → Model Registry
Important Details
a. File System Integration:
• How the install directory structure maps to the system
• Where model files are stored and accessed
b. Configuration Flow:
• How install.json and model configuration files interact
• Uninstallation path (uninstall.js)
1. User Interface Layer (top)
2. Core System Layer (middle)
3. Model Storage Layer (bottom)
Technical Notes
Annotations for:
• Supported model types and their configurations
• Installation flow sequence
• Script execution pathway
• Model loading and unloading processes
This design should effectively communicate how the system manages LLaMa.cpp models within the Pinokio ecosystem while maintaining clarity about the installation and execution processes.