Add Docs dir

CHANGES_SUMMARY.md

-# ChartAnalyzer System - Changes Summary
-
-## Overview
-This document summarizes all the improvements and enhancements made to the ChartAnalyzer system, including new features, architectural improvements, and documentation.
-
-## 📋 Changes Made
-
-### 1. **UML Documentation** ✅
-- **File**: `UML_Diagrams.md`
-- **Description**: Comprehensive UML documentation including:
-  - Use Case Diagram
-  - System Sequence Diagrams (3 flows)
-  - Class Diagram
-  - Component Diagram
-  - Activity Diagram
-  - State Diagram
-  - Deployment Diagram
-  - Data Flow Diagram
-
-### 2. **New Use Cases** ✅
-- **File**: `src/application/use_cases/save_analysis.py`
-  - **Purpose**: Save analysis results to database for history tracking
-  - **Features**: UUID generation, timestamp handling, repository integration
-
-- **File**: `src/application/use_cases/get_analysis_history.py`
-  - **Purpose**: Retrieve analysis history for users
-  - **Features**: Pagination support, user-specific filtering
-
-- **File**: `src/application/use_cases/chat_conversation.py`
-  - **Purpose**: Handle interactive chat conversations about charts
-  - **Features**: Context building, conversation history, enhanced prompts
-
-### 3. **New Domain Entities** ✅
-- **File**: `src/domain/entities/conversation.py`
-  - **Entities**: `Conversation` and `ConversationMessage`
-  - **Features**: Timestamp tracking, message types, conversation state
-
-### 4. **New DTOs** ✅
-- **File**: `src/application/dtos/conversation.py`
-  - **DTOs**: Request/Response DTOs for conversation management
-  - **Features**: Type safety, validation, API communication
-
-### 5. **New API Routes** ✅
-- **File**: `src/infrastructure/api/fastapi/routes/conversations.py`
-  - **Endpoints**:
-    - `POST /conversations/` - Create new conversation
-    - `GET /conversations/` - List user conversations
-    - `GET /conversations/{id}` - Get conversation details
-    - `POST /conversations/{id}/messages` - Send message
-  - **Features**: Authentication, error handling, logging
-
-### 6. **Frontend Components** ✅
-- **File**: `frontend/src/pages/Charts/ChatInterface.tsx`
-  - **Features**:
-    - Real-time chat interface
-    - Image upload and preview
-    - Message history
-    - Typing indicators
-    - Responsive design
-    - Error handling
-
-- **File**: `frontend/src/styles/chat.css`
-  - **Features**:
-    - Modern chat UI styling
-    - Responsive design
-    - Animation effects
-    - Mobile optimization
-
-### 7. **System Integration** ✅
-- **File**: `main.py` - Added conversation router
-- **File**: `frontend/src/Routes/Routes.tsx` - Updated import path
-- **Features**: Seamless integration with existing system
-
-### 8. **System Analysis** ✅
-- **File**: `System_Analysis_and_Improvements.md`
-  - **Content**:
-    - Current system overview
-    - Identified improvements
-    - Implementation recommendations
-    - Priority phases
-    - Code quality suggestions
-
-## 🚀 New Features Added
-
-### 1. **Interactive Chat System**
-- Real-time conversation with AI about charts
-- Message history and context preservation
-- Typing indicators and timestamps
-- Image preview in chat interface
-
-### 2. **Analysis History Tracking**
-- Save all analysis results to database
-- Retrieve user's analysis history
-- Track model performance and usage
-
-### 3. **Enhanced User Experience**
-- Modern, responsive chat interface
-- Better error handling and user feedback
-- Improved navigation and routing
-- Mobile-friendly design
-
-### 4. **Conversation Management**
-- Create and manage chat sessions
-- Persistent conversation history
-- Context-aware responses
-- Multi-turn conversations
-
-## 🏗️ Architectural Improvements
-
-### 1. **Clean Architecture Enhancements**
-- Additional use cases following domain-driven design
-- New domain entities for conversation management
-- Proper separation of concerns
-- Interface-based design
-
-### 2. **API Design**
-- RESTful conversation endpoints
-- Proper error handling and status codes
-- Authentication and authorization
-- Comprehensive logging
-
-### 3. **Database Design**
-- Suggested schema improvements
-- Analysis history tables
-- Conversation and message tables
-- Proper relationships and constraints
-
-## 📊 System Flow Improvements
-
-### Before:
-```
-User Upload → Analysis → Result Display
-```
-
-### After:
-```
-User Upload → Analysis → Result Display
-     ↓
-Conversation History → Interactive Chat → Context-Aware Responses
-     ↓
-Analysis History → User Dashboard → Performance Tracking
-```
-
-## 🔧 Technical Enhancements
-
-### 1. **Error Handling**
-- Comprehensive error catching
-- User-friendly error messages
-- Proper logging and monitoring
-- Graceful degradation
-
-### 2. **Performance**
-- Optimized component rendering
-- Efficient state management
-- Responsive design patterns
-- Loading states and indicators
-
-### 3. **Security**
-- Authentication integration
-- Input validation
-- Secure API communication
-- Protected routes
-
-## 📱 User Experience Improvements
-
-### 1. **Interface Design**
-- Modern, clean chat interface
-- Intuitive navigation
-- Responsive design for all devices
-- Accessibility considerations
-
-### 2. **Interaction Patterns**
-- Real-time messaging
-- Visual feedback
-- Progressive disclosure
-- Contextual help
-
-### 3. **Data Visualization**
-- Image preview capabilities
-- Analysis result formatting
-- History visualization
-- Performance metrics
-
-## 🎯 Impact on System
-
-### 1. **Functionality**
-- ✅ Enhanced user engagement
-- ✅ Better data persistence
-- ✅ Improved analysis capabilities
-- ✅ Interactive features
-
-### 2. **Maintainability**
-- ✅ Cleaner code structure
-- ✅ Better separation of concerns
-- ✅ Comprehensive documentation
-- ✅ Modular design
-
-### 3. **Scalability**
-- ✅ Extensible architecture
-- ✅ Database optimization
-- ✅ API design patterns
-- ✅ Performance considerations
-
-## 🔄 Next Steps
-
-### Immediate (Phase 1):
-1. ✅ UML documentation complete
-2. ✅ New use cases implemented
-3. ✅ Frontend components created
-4. ✅ API routes added
-5. ✅ System integration complete
-
-### Short-term (Phase 2):
-1. Implement database migrations
-2. Add comprehensive testing
-3. Deploy and test in staging
-4. User feedback collection
-
-### Long-term (Phase 3):
-1. Performance optimization
-2. Advanced analytics features
-3. Microservices migration
-4. Advanced monitoring
-
-## 📈 Benefits Achieved
-
-### 1. **User Benefits**
-- Interactive chat experience
-- Analysis history tracking
-- Better user engagement
-- Improved accessibility
-
-### 2. **Developer Benefits**
-- Cleaner codebase
-- Better documentation
-- Easier maintenance
-- Extensible architecture
-
-### 3. **Business Benefits**
-- Enhanced user retention
-- Better data insights
-- Improved user satisfaction
-- Competitive advantage
-
-## 🎉 Conclusion
-
-The ChartAnalyzer system has been significantly enhanced with:
-
-- **8 new files** created
-- **3 major features** added
-- **Comprehensive documentation** provided
-- **Architectural improvements** implemented
-- **Better user experience** delivered
-
-The system now provides a modern, interactive, and feature-rich platform for chart analysis with proper documentation, clean architecture, and enhanced user experience. 
\ No newline at end of file

System_Analysis_and_Improvements.md

-# ChartAnalyzer System - Analysis and Improvements
-
-## Current System Overview
-
-The ChartAnalyzer is a comprehensive data visualization analysis platform that uses AI/LLM models to analyze charts and answer user questions. The system follows a clean architecture pattern with clear separation of concerns.
-
-### Current Architecture Strengths
-
-1. **Clean Architecture**: Well-structured with domain, application, and infrastructure layers
-2. **Multiple LLM Support**: Integration with both Ollama and ChartGemma models
-3. **Modern Tech Stack**: FastAPI backend, React frontend, PostgreSQL database
-4. **Authentication System**: JWT-based authentication with proper security measures
-5. **Responsive UI**: Modern, user-friendly interface with good UX
-
-## Identified Areas for Improvement
-
-### 1. **Enhanced User Experience & Features**
-
-#### Current Limitations:
-- No conversation history tracking
-- Limited interactive features
-- No analysis history for users
-- Basic chart analysis without advanced features
-
-#### Improvements Implemented:
-
-**A. Interactive Chat Interface**
-- Created `ChatInterface.tsx` component for real-time conversations
-- Added conversation context management
-- Implemented typing indicators and message timestamps
-- Added responsive design for mobile devices
-
-**B. Analysis History Tracking**
-- Created `SaveAnalysisUseCase` for storing analysis results
-- Added `GetAnalysisHistoryUseCase` for retrieving user history
-- Implemented conversation persistence
-
-**C. Enhanced Conversation Management**
-- Created `Conversation` and `ConversationMessage` entities
-- Added conversation DTOs for API communication
-- Implemented conversation routes in FastAPI
-
-### 2. **System Architecture Enhancements**
-
-#### A. New Use Cases Added:
-```python
-# Analysis History Management
-- SaveAnalysisUseCase: Saves analysis results to database
-- GetAnalysisHistoryUseCase: Retrieves user's analysis history
-- ChatConversationUseCase: Handles interactive conversations
-```
-
-#### B. New Domain Entities:
-```python
-# Conversation Management
-- Conversation: Represents a chat session
-- ConversationMessage: Individual messages in a conversation
-```
-
-#### C. New API Endpoints:
-```python
-# Conversation Management
-POST /conversations/ - Create new conversation
-GET /conversations/ - List user conversations
-GET /conversations/{id} - Get conversation details
-POST /conversations/{id}/messages - Send message
-```
-
-### 3. **Frontend Enhancements**
-
-#### A. New Components:
-- `ChatInterface.tsx`: Interactive chat component
-- Enhanced styling with `chat.css`
-
-#### B. Features Added:
-- Real-time message display
-- Image preview in chat
-- Typing indicators
-- Message timestamps
-- Responsive design
-- Error handling
-
-### 4. **Database Schema Improvements**
-
-#### Suggested New Tables:
-```sql
--- Analysis History
-CREATE TABLE analysis_history (
-    id UUID PRIMARY KEY,
-    user_id UUID REFERENCES users(id),
-    chart_image_id UUID REFERENCES chart_images(id),
-    question TEXT NOT NULL,
-    answer TEXT NOT NULL,
-    model_used VARCHAR(50),
-    processing_time FLOAT,
-    created_at TIMESTAMP DEFAULT NOW()
-);
-
--- Conversations
-CREATE TABLE conversations (
-    id UUID PRIMARY KEY,
-    user_id UUID REFERENCES users(id),
-    chart_image_id UUID REFERENCES chart_images(id),
-    title VARCHAR(255) NOT NULL,
-    created_at TIMESTAMP DEFAULT NOW(),
-    updated_at TIMESTAMP DEFAULT NOW(),
-    is_active BOOLEAN DEFAULT TRUE
-);
-
--- Conversation Messages
-CREATE TABLE conversation_messages (
-    id UUID PRIMARY KEY,
-    conversation_id UUID REFERENCES conversations(id),
-    user_id UUID REFERENCES users(id),
-    message_type VARCHAR(20) NOT NULL, -- 'user' or 'assistant'
-    content TEXT NOT NULL,
-    timestamp TIMESTAMP DEFAULT NOW()
-);
-```
-
-## Recommended Additional Improvements
-
-### 1. **Performance Optimizations**
-
-#### A. Caching Strategy:
-```python
-# Add Redis caching for:
-- User sessions
-- Analysis results
-- Model responses
-- Frequently accessed data
-```
-
-#### B. Image Processing:
-```python
-# Implement image optimization:
-- Automatic resizing for large images
-- Format conversion (WebP support)
-- Compression for storage efficiency
-- Thumbnail generation
-```
-
-### 2. **Advanced Analytics Features**
-
-#### A. Chart Type Detection:
-```python
-# Add automatic chart type recognition:
-- Bar charts, line charts, pie charts
-- Scatter plots, heatmaps
-- Custom chart types
-```
-
-#### B. Data Extraction:
-```python
-# Implement data extraction from charts:
-- Extract numerical values
-- Identify trends and patterns
-- Generate data summaries
-- Export data in various formats
-```
-
-### 3. **Enhanced Security**
-
-#### A. Rate Limiting:
-```python
-# Implement rate limiting:
-- Per-user request limits
-- API endpoint protection
-- DDoS prevention
-```
-
-#### B. Input Validation:
-```python
-# Enhanced validation:
-- Image file type validation
-- File size limits
-- Malicious content detection
-- SQL injection prevention
-```
-
-### 4. **Monitoring and Logging**
-
-#### A. Application Monitoring:
-```python
-# Add comprehensive monitoring:
-- Request/response logging
-- Performance metrics
-- Error tracking
-- User activity analytics
-```
-
-#### B. Model Performance Tracking:
-```python
-# Track LLM model performance:
-- Response times
-- Accuracy metrics
-- User satisfaction ratings
-- Model comparison analytics
-```
-
-### 5. **Scalability Improvements**
-
-#### A. Microservices Architecture:
-```python
-# Consider splitting into microservices:
-- Authentication service
-- Chart analysis service
-- Conversation service
-- File storage service
-```
-
-#### B. Load Balancing:
-```python
-# Implement load balancing:
-- Multiple API instances
-- Database read replicas
-- CDN for static assets
-```
-
-## Implementation Priority
-
-### Phase 1 (High Priority - Already Implemented):
-1. ✅ Interactive chat interface
-2. ✅ Analysis history tracking
-3. ✅ Conversation management
-4. ✅ Enhanced UI/UX
-
-### Phase 2 (Medium Priority):
-1. Database schema updates
-2. Caching implementation
-3. Image optimization
-4. Rate limiting
-
-### Phase 3 (Low Priority):
-1. Advanced analytics features
-2. Microservices migration
-3. Advanced monitoring
-4. Performance optimizations
-
-## Code Quality Improvements
-
-### 1. **Error Handling**
-```python
-# Add comprehensive error handling:
-- Custom exception classes
-- Proper error responses
-- Logging and monitoring
-- User-friendly error messages
-```
-
-### 2. **Testing**
-```python
-# Implement comprehensive testing:
-- Unit tests for use cases
-- Integration tests for API
-- End-to-end tests
-- Performance tests
-```
-
-### 3. **Documentation**
-```python
-# Improve documentation:
-- API documentation (OpenAPI/Swagger)
-- Code documentation
-- User guides
-- Deployment guides
-```
-
-## Summary of Changes Made
-
-### Files Created:
-1. `UML_Diagrams.md` - Comprehensive UML documentation
-2. `src/application/use_cases/save_analysis.py` - Analysis history tracking
-3. `src/application/use_cases/get_analysis_history.py` - History retrieval
-4. `src/application/use_cases/chat_conversation.py` - Interactive chat
-5. `src/domain/entities/conversation.py` - Conversation entities
-6. `src/application/dtos/conversation.py` - Conversation DTOs
-7. `src/infrastructure/api/fastapi/routes/conversations.py` - Conversation API
-8. `frontend/src/pages/Charts/ChatInterface.tsx` - Chat UI component
-9. `frontend/src/styles/chat.css` - Chat styling
-10. `System_Analysis_and_Improvements.md` - This analysis document
-
-### Key Improvements:
-1. **Enhanced User Experience**: Interactive chat interface with real-time messaging
-2. **Data Persistence**: Analysis history and conversation tracking
-3. **Better Architecture**: Additional use cases and domain entities
-4. **Improved UI**: Modern, responsive chat interface
-5. **Comprehensive Documentation**: UML diagrams and system analysis
-
-### Next Steps:
-1. Update the main FastAPI app to include the new conversation routes
-2. Implement the database migrations for new tables
-3. Add the chat interface to the frontend routing
-4. Implement the repository layer for conversations
-5. Add comprehensive testing for new features
-
-The system is now better positioned for scalability, maintainability, and enhanced user experience while maintaining the clean architecture principles. 
\ No newline at end of file

UML_Diagrams.md

-# ChartAnalyzer System - UML Diagrams
-
-## 1. Use Case Diagram
-
-```mermaid
-graph TB
-    subgraph "ChartAnalyzer System"
-        subgraph "Actors"
-            User[👤 User]
-            Admin[👨‍💼 Admin]
-            LLMService[🤖 LLM Service]
-        end
-        
-        subgraph "Authentication Use Cases"
-            UC1[Register Account]
-            UC2[Login]
-            UC3[Logout]
-            UC4[Validate Token]
-        end
-        
-        subgraph "Chart Analysis Use Cases"
-            UC5[Upload Chart Image]
-            UC6[Analyze Chart General]
-            UC7[Ask Specific Question]
-            UC8[Get Advanced Analysis]
-            UC9[View Analysis History]
-        end
-        
-        subgraph "System Management Use Cases"
-            UC10[Check Server Status]
-            UC11[List Available Models]
-            UC12[Test Model Connection]
-        end
-    end
-    
-    %% Actor relationships
-    User --> UC1
-    User --> UC2
-    User --> UC3
-    User --> UC5
-    User --> UC6
-    User --> UC7
-    User --> UC8
-    User --> UC9
-    User --> UC10
-    User --> UC11
-    User --> UC12
-    
-    Admin --> UC10
-    Admin --> UC11
-    Admin --> UC12
-    
-    %% Include relationships
-    UC6 -.->|includes| UC5
-    UC7 -.->|includes| UC5
-    UC8 -.->|includes| UC5
-    
-    %% Extend relationships
-    UC8 -.->|extends| UC7
-    
-    %% System dependencies
-    UC6 -.->|uses| LLMService
-    UC7 -.->|uses| LLMService
-    UC8 -.->|uses| LLMService
-```
-
-## 2. System Sequence Diagrams
-
-### 2.1 User Registration Flow
-
-```mermaid
-sequenceDiagram
-    participant U as User
-    participant F as Frontend
-    participant API as FastAPI
-    participant AS as AuthService
-    participant UR as UserRepository
-    participant DB as Database
-    
-    U->>F: Fill registration form
-    F->>API: POST /auth/register
-    API->>AS: register(email, password)
-    AS->>AS: hash_password(password)
-    AS->>UR: create_user(user)
-    UR->>DB: INSERT user
-    DB-->>UR: user_id
-    UR-->>AS: User object
-    AS-->>API: User object
-    API-->>F: 201 Created
-    F-->>U: Registration success
-```
-
-### 2.2 Chart Analysis Flow
-
-```mermaid
-sequenceDiagram
-    participant U as User
-    participant F as Frontend
-    participant API as FastAPI
-    participant CS as ChartService
-    participant LS as LLMService
-    participant CG as ChartGemma
-    participant O as Ollama
-    
-    U->>F: Upload image + question
-    F->>API: POST /charts/analyze
-    API->>CS: analyze_chart(image, question)
-    CS->>LS: analyze(request)
-    alt Model Selection
-        LS->>CG: analyze(image, question)
-        CG-->>LS: analysis_result
-    else Default Model
-        LS->>O: analyze(image, question)
-        O-->>LS: analysis_result
-    end
-    LS-->>CS: LLMResponse
-    CS-->>API: Analysis result
-    API-->>F: 200 OK
-    F-->>U: Display analysis
-```
-
-### 2.3 Advanced Chart Analysis Flow
-
-```mermaid
-sequenceDiagram
-    participant U as User
-    participant F as Frontend
-    participant API as FastAPI
-    participant CS as ChartService
-    participant CG as ChartGemma
-    
-    U->>F: Upload image + question + advanced=true
-    F->>API: POST /charts/ask
-    API->>CS: analyze_specialized(image, question, advanced)
-    CS->>CS: Add "PROGRAM OF THOUGHT" prefix
-    CS->>CG: analyze(enhanced_question)
-    CG-->>CS: Advanced analysis result
-    CS-->>API: Analysis result
-    API-->>F: 200 OK
-    F-->>U: Display advanced analysis
-```
-
-## 3. Class Diagram
-
-```mermaid
-classDiagram
-    %% Domain Entities
-    class User {
-        +String id
-        +EmailStr email
-        +String password_hash
-        +Boolean is_active
-        +DateTime created_at
-        +DateTime last_login
-    }
-    
-    class ChartImage {
-        +String id
-        +String user_id
-        +Bytes image_data
-        +DateTime uploaded_at
-    }
-    
-    class ChartAnalysis {
-        +String id
-        +String chart_image_id
-        +String question
-        +String answer
-        +DateTime created_at
-    }
-    
-    %% Application DTOs
-    class RegisterRequestDTO {
-        +String email
-        +String password
-    }
-    
-    class LoginRequestDTO {
-        +String email
-        +String password
-    }
-    
-    class LLMRequestDTO {
-        +Bytes image_bytes
-        +String question
-    }
-    
-    class LLMResponseDTO {
-        +String answer
-        +String model_used
-        +Float processing_time
-    }
-    
-    %% Application Services
-    class AuthService {
-        -UserRepositoryPort user_repo
-        -TokenRepositoryPort token_repo
-        -String secret_key
-        +register(email, password) User
-        +login(email, password) String
-        +logout(token) void
-        +validate_token(token) Boolean
-    }
-    
-    class ChartGemmaService {
-        -String gradio_url
-        +analyze(request) LLMResponseDTO
-        -_load_image(image_data) Image
-        -_call_gradio_api(image, question) String
-    }
-    
-    class OllamaService {
-        -String host
-        -String model
-        +analyze(request) LLMResponseDTO
-    }
-    
-    %% Domain Ports (Interfaces)
-    class UserRepositoryPort {
-        <<interface>>
-        +create_user(user) void
-        +get_by_email(email) User
-        +get_by_id(id) User
-    }
-    
-    class ChartsRepositoryPort {
-        <<interface>>
-        +save(chart_image) void
-        +get_by_id(id) ChartImage
-        +get_by_user_id(user_id) List~ChartImage~
-    }
-    
-    class LLMServicePort {
-        <<interface>>
-        +analyze(request) LLMResponseDTO
-    }
-    
-    %% Use Cases
-    class UploadChartUseCase {
-        -ChartsRepositoryPort image_repo
-        +execute(image_bytes, user_id) String
-    }
-    
-    class AnalyzeChartUseCase {
-        -ChartsRepositoryPort charts_repo
-        -AnalysisRepositoryPort analysis_repo
-        +execute(image_bytes, question) ChartAnalysis
-    }
-    
-    %% Relationships
-    User ||--o{ ChartImage : owns
-    ChartImage ||--o{ ChartAnalysis : generates
-    AuthService ..|> UserRepositoryPort : uses
-    ChartGemmaService ..|> LLMServicePort : implements
-    OllamaService ..|> LLMServicePort : implements
-    UploadChartUseCase ..|> ChartsRepositoryPort : uses
-    AnalyzeChartUseCase ..|> ChartsRepositoryPort : uses
-    AnalyzeChartUseCase ..|> AnalysisRepositoryPort : uses
-```
-
-## 4. Component Diagram
-
-```mermaid
-graph TB
-    subgraph "Frontend Layer (React + TypeScript)"
-        UI[User Interface]
-        AC[Auth Context]
-        CS[Chart Service]
-        AS[API Service]
-    end
-    
-    subgraph "API Gateway Layer (FastAPI)"
-        Router[Router]
-        Middleware[CORS Middleware]
-        Auth[Authentication]
-    end
-    
-    subgraph "Application Layer"
-        UC[Use Cases]
-        AServices[Application Services]
-        DTOs[Data Transfer Objects]
-    end
-    
-    subgraph "Domain Layer"
-        Entities[Domain Entities]
-        Ports[Domain Ports]
-        Services[Domain Services]
-    end
-    
-    subgraph "Infrastructure Layer"
-        Repos[Repositories]
-        External[External Services]
-        DB[(PostgreSQL)]
-    end
-    
-    subgraph "External Services"
-        ChartGemma[ChartGemma Model]
-        Ollama[Ollama LLM]
-        Gradio[Gradio API]
-    end
-    
-    %% Frontend connections
-    UI --> AC
-    UI --> CS
-    CS --> AS
-    
-    %% API connections
-    AS --> Router
-    Router --> Middleware
-    Router --> Auth
-    
-    %% Application connections
-    Router --> UC
-    UC --> AServices
-    AServices --> DTOs
-    
-    %% Domain connections
-    AServices --> Entities
-    AServices --> Ports
-    Ports --> Services
-    
-    %% Infrastructure connections
-    Ports --> Repos
-    Repos --> DB
-    Services --> External
-    
-    %% External service connections
-    External --> ChartGemma
-    External --> Ollama
-    External --> Gradio
-```
-
-## 5. Activity Diagram - Chart Analysis Process
-
-```mermaid
-flowchart TD
-    Start([User starts analysis]) --> Upload{Upload chart image?}
-    Upload -->|Yes| Validate{Image valid?}
-    Validate -->|No| Error[Show error message]
-    Validate -->|Yes| Question{Enter question?}
-    Question -->|No| Auto[Use default analysis]
-    Question -->|Yes| Model{Select model?}
-    Auto --> Model
-    
-    Model -->|ChartGemma| CG[Process with ChartGemma]
-    Model -->|Ollama| OL[Process with Ollama]
-    Model -->|Default| Default[Use default model]
-    
-    CG --> Advanced{Advanced analysis?}
-    Advanced -->|Yes| Enhance[Add Program of Thought]
-    Advanced -->|No| Process[Process normally]
-    Enhance --> Process
-    OL --> Process
-    Default --> Process
-    
-    Process --> Result[Generate analysis result]
-    Result --> Save[Save to database]
-    Save --> Display[Display result to user]
-    Display --> End([Analysis complete])
-    
-    Error --> End
-```
-
-## 6. State Diagram - User Authentication
-
-```mermaid
-stateDiagram-v2
-    [*] --> Unauthenticated
-    Unauthenticated --> Registering : Register
-    Unauthenticated --> LoggingIn : Login
-    Registering --> Unauthenticated : Registration failed
-    Registering --> Authenticated : Registration success
-    LoggingIn --> Unauthenticated : Login failed
-    LoggingIn --> Authenticated : Login success
-    Authenticated --> Unauthenticated : Logout
-    Authenticated --> TokenExpired : Token expires
-    TokenExpired --> Unauthenticated : Auto logout
-    TokenExpired --> Authenticated : Refresh token
-```
-
-## 7. Deployment Diagram
-
-```mermaid
-graph TB
-    subgraph "Client Layer"
-        Browser[Web Browser]
-        Mobile[Mobile App]
-    end
-    
-    subgraph "Frontend Server"
-        React[React App<br/>Vite Dev Server]
-        Static[Static Assets]
-    end
-    
-    subgraph "Backend Server"
-        FastAPI[FastAPI Application]
-        Uvicorn[Uvicorn Server]
-    end
-    
-    subgraph "Database Server"
-        PostgreSQL[(PostgreSQL Database)]
-        Alembic[Alembic Migrations]
-    end
-    
-    subgraph "External Services"
-        ChartGemmaAPI[ChartGemma API<br/>Gradio]
-        OllamaAPI[Ollama API<br/>Local]
-    end
-    
-    %% Connections
-    Browser --> React
-    Mobile --> React
-    React --> Static
-    React --> FastAPI
-    FastAPI --> Uvicorn
-    Uvicorn --> PostgreSQL
-    Uvicorn --> Alembic
-    FastAPI --> ChartGemmaAPI
-    FastAPI --> OllamaAPI
-```
-
-## 8. Data Flow Diagram
-
-```mermaid
-graph LR
-    subgraph "Input Sources"
-        UserInput[User Input]
-        ImageUpload[Image Upload]
-        QuestionInput[Question Input]
-    end
-    
-    subgraph "Processing"
-        Auth[Authentication]
-        ImageProc[Image Processing]
-        LLMProc[LLM Processing]
-        Analysis[Analysis Engine]
-    end
-    
-    subgraph "Storage"
-        UserDB[(User Database)]
-        ImageDB[(Image Storage)]
-        AnalysisDB[(Analysis History)]
-    end
-    
-    subgraph "Output"
-        Response[API Response]
-        UI[User Interface]
-        Logs[System Logs]
-    end
-    
-    %% Data flows
-    UserInput --> Auth
-    ImageUpload --> ImageProc
-    QuestionInput --> LLMProc
-    
-    Auth --> UserDB
-    ImageProc --> ImageDB
-    LLMProc --> Analysis
-    Analysis --> AnalysisDB
-    
-    Analysis --> Response
-    Response --> UI
-    Auth --> Logs
-    Analysis --> Logs
-``` 
\ No newline at end of file