# blilet/pricer_basic architecture

> Architecture diagram of the GitHub repository blilet/pricer_basic, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2025-03-29). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/blilet/pricer_basic
- Repository: https://github.com/blilet/pricer_basic

## Overview

##### Main Components
- GUI Component ("gui.py"): Acts as the user interface where users interact with the options pricer. This module is responsible for displaying input fields, outputs, and potentially integrating the option pricing results.
- Pricing Calculation Module ("ModuleBlackScholes(2).py"): Contains the Black-Scholes formula and related computations to price options. It is the core computational engine that the GUI will invoke.
- Data Extraction Component ("extraction.py"): Likely responsible for fetching or processing external data, which could be used as inputs or for analysis in pricing.
- External Utilities ("commun" folder): Contains executable files (chromedriver.exe and chromedriver1.exe), which suggest automated web interactions (possibly for scraping market data or performing browser-based automation for data input).

##### Relationships and Interactions
- The GUI component triggers events that:
– Call the Pricing Calculation Module to compute option prices.
– Interact with the Data Extraction Module to fetch or update market data.
- The Pricing Calculation Component accepts input parameters, performs calculations, and returns pricing outputs back to the GUI for display.
- The Data Extraction Module may communicate with external services or websites using the drivers in the “commun” folder. The extracted data feeds into the pricing module or is displayed on the GUI.

##### Technologies, Frameworks, and Libraries (as inferred)
- Python as the base programming language.
- Likely use of a GUI framework (Tkinter, PyQt, etc.) in gui.py.
- Custom implementation of Black-Scholes in the pricing module.
- Automation libraries (Selenium or similar) likely orchestrate operations using the Chrome drivers.

## Diagram (Mermaid)

```mermaid
flowchart TD
    GUI["GUI (gui.py)"]:::gui
    Pricing["Pricing Engine (ModuleBlackScholes)"]:::pricing
    Extraction["Data Extraction (extraction.py)"]:::extraction

    GUI -->|"triggerPricing"| Pricing
    GUI -->|"triggerExtraction"| Extraction
    Pricing -->|"pricingResults"| GUI
    Extraction -->|"extractedData"| GUI

    subgraph "External Utilities"
        Commun["Commun Folder"]:::external
        Chrome1["chromedriver.exe"]:::external
        Chrome2["chromedriver1.exe"]:::external
        Commun --- Chrome1
        Commun --- Chrome2
    end

    Extraction -->|"usesDriver"| Commun

    click GUI "https://github.com/blilet/pricer_basic/blob/main/gui.py"
    click Pricing "https://github.com/blilet/pricer_basic/blob/main/ModuleBlackScholes(2).py"
    click Extraction "https://github.com/blilet/pricer_basic/blob/main/extraction.py"
    click Commun "https://github.com/blilet/pricer_basic/tree/main/commun"
    click Chrome1 "https://github.com/blilet/pricer_basic/blob/main/commun/chromedriver.exe"
    click Chrome2 "https://github.com/blilet/pricer_basic/blob/main/commun/chromedriver1.exe"

    classDef gui fill:#ffcccc,stroke:#333,stroke-width:2px;
    classDef pricing fill:#ccffcc,stroke:#333,stroke-width:2px;
    classDef extraction fill:#ccccff,stroke:#333,stroke-width:2px;
    classDef external fill:#ffffcc,stroke:#333,stroke-width:2px;
```
