Author: lechuck park

AI Infrastructure Architect & Technical Visualizer "Complex Systems, Simplified. I translate massive AI infrastructure into visual intelligence." I love to learn computer tech and help people by the digital.

CFD + AI/ML for Digital Twin 2

Posted on by lechuck park

Digital Twin System Using CFD and AI/ML

This diagram illustrates the complete lifecycle of a digital twin system, showing how CFD (Computational Fluid Dynamics) and AI/ML play crucial roles at different stages.

Key Stages

  1. Design:
    • CFD plays a critical role at this stage
    • Establishes the foundation through geometric modeling, physical property definition, and boundary condition setup
    • Accurate physical simulation at this stage forms the basis for future predictions
  2. Build:
    • Implementation stage for the designed model
    • Integration of both CFD models and AI/ML models
  3. Operate:
    • AI/ML plays a critical role at this stage
    • System performance prediction and optimization based on real-time data
    • Continuous model improvement by learning from operational data

Technology Integration Process

  • CFD Track:
    • Provides accurate physical modeling during the design phase
    • Defines geometry, physics, and boundary conditions to establish the basic structure
    • Verifies model accuracy through validation processes
    • Updates the model according to changes during operation
  • AI/ML Track:
    • Configures learning data and defines metrics
    • Sets up data lists and resolution
    • Provides predictive models using real-time data during the operation phase
    • Continuously improves prediction accuracy by learning from operational data

Cyclical Improvement System

The key to this system is that physical modeling (CFD) at the design stage and data-driven prediction (AI/ML) at the operation stage work complementarily to form a continuous improvement cycle. Real data collected during operation is used to update the AI/ML models, which in turn contributes to improving the accuracy of the CFD models.

With Claude

Home LLM

Posted on by lechuck park

This image shows the architecture of a “Home LLM” system, illustrating an innovative change in how home appliances are used.

Key points:

  1. Evolution from Traditional Approach: While traditional electronics came as ‘product + paper manual’ packages, this new system replaces manuals with small LLM models.
  2. Home Foundation Model: Homes are equipped with a main LLM model (“Home Foundation LLM Model”) that learns from environmental data.
  3. Knowledge Exchange: Product-specific small LLM models and the home foundation model exchange data and learning outcomes with each other.
  4. User Interface: Users can easily interact through the LLM by asking questions and giving commands, making product usage much more intuitive and convenient.
  5. AI Agent Control: Additionally, AI agents automatically optimize the control of these products, increasing efficiency.

This system presents a smart home architecture that fundamentally improves the user experience of electronic products by integrating AI and LLM technologies in the home environment.

With Claude

Power Flow

Posted on by lechuck park

Power Flow Diagram Analysis

This image illustrates a power flow diagram for a data center or server room, showing the sequential path of electricity from external power sources to the final server equipment.

Main Components:

  1. Intake: External power supply at 154 kV / 22.9 kV with 100MW(MVA) capacity
  2. Transformer: Performs voltage conversion (step down) to make power easier to handle
  3. Generator: Provides backup power during outages, connected to a fuel tank
  4. Transformer #2: Second voltage conversion, bringing power closer to usable voltage (220/380V)
  5. UPS/Battery: Uninterruptible Power Supply with battery backup for blackout protection, showing capacity (KVA) and backup time
  6. PDU/TOB: Power Distribution Unit for connecting to servers
  7. Server: Final power consumption equipment

Key Features:

  • Red circles indicate power switching/distribution points
  • Dotted lines show backup power connections
  • The bottom section details the characteristics of each component:
    • Intake power specifications
    • Voltage conversion information
    • Blackout readiness status
    • Server connection details
    • Power usage status

Summary:

This diagram represents the complete power infrastructure of a data center, illustrating how electricity flows from the grid through multiple transformation and backup systems before reaching the servers. It demonstrates the redundancy measures implemented to ensure continuous operation during power outages, including generators and UPS systems. The power path includes necessary voltage step-down transformations to convert high-voltage grid power to server-appropriate voltages, with switching and distribution points throughout the system. This comprehensive power flow design ensures reliable, uninterrupted power delivery critical for data center operations.

With Claude

OOM Killer

Posted on by lechuck park

OOM (Out-of-Memory) Killer

This diagram explains the Linux OOM Killer mechanism:

  1. Memory Request Process:
    • A process requests memory allocation from the operating system.
    • It receives a handler for the allocated memory.
  2. Memory Management System:
    • The operating system manages virtual memory.
    • Virtual memory utilizes physical memory and disk swap space.
    • Linux allows memory overcommitment.
  3. OOM Killer Operation:
    • When physical memory becomes scarce, the OOM Killer is initiated.
    • The OOM Killer selects and terminates “less important” processes based on factors such as memory usage and process priority.
    • This mechanism maintains the overall stability of the system.

Linux OOM Killer is a mechanism that automatically activates when physical memory becomes scarce. It maintains system stability by selecting and terminating less important processes based on memory usage and priority.

With Claude

There’s such thing as ‘impossible’.

Posted on by lechuck park

This infographic illustrates a software development philosophy titled “There’s such thing as ‘impossible’.” It emphasizes that there are real limitations in development:

  1. Development process flow:
    • “Machine Code” (represented by binary digits)
    • “Software Dev” (showing code editor)
    • “Application” (showing mobile interface)
    • Arrow pointing to infinity symbol labeled “Unbounded” with a warning sign
  2. Practical constraints:
    • “Reality has no ∞ button. Choose.” (emphasizing limitations exist)
    • Icons representing people and money (resource management)
    • “Everything requires a load” (showing resources are needed)
    • “Energy” and “Time” with cycling arrows (demonstrating finite resources)
  3. Keys to successful development:
    • Clear problem definition (“Clear Definition”)
    • Setting priorities (“Priorities”)
    • Target goals

The overall message highlights that impossibility does exist in software development due to real-world constraints of time, energy, and resources. It emphasizes the importance of acknowledging these limitations and addressing them through clear problem definition and priority setting for effective development.

With Claude