How snodgrassryan/regen33 works
Main Components
a) Input Processing Layer
• Two possible input paths:
• File-based input (data.dat for Windows version)
• Standard input (for Linux version)
• Input_mod.f90 as the primary input handler
b) Core Computation Layer
• Center this as the main processing unit
• Following computational modules:
• compute_mod.f90
• dlinpk.f90 (likely linear algebra operations)
• dwtmeta.f90
• he3props.f90 (Helium-3 properties)
• he4props.f90 (Helium-4 properties)
• he4state.f90 (Helium-4 state calculations)
c) Global State Management
• Globmod.f90 as a cross-cutting concern
• Interaction with other modules
d) Output Processing Layer
• Output_mod.f90
• System output paths
┌─────────────────────────────────────────────┐
• Platform Selection │
• (header.f90 / headerpc.f90) │
• ┘
• ↓
┌─────────────────────────────────────────────┐
• Input Processing Layer │
• (main.f90/main_win.f90 → input_mod.f90) │
• ┘
• ↓
┌─────────────────────────────────────────────┐
• Global State Management │
• (globmod.f90) │
• ┘
• ↓
┌─────────────────────────────────────────────┐
• Core Computation Layer │
• [Show all computational modules here] │
• ┘
• ↓
┌─────────────────────────────────────────────┐
• Output Processing Layer │
• (output_mod.f90) │
• ┘
Notes Section
A notes section explaining:
• Build requirements
• Input file format requirements
• Platform-specific considerations
• Execution flow differences between platforms
• Clear hierarchical representation
• Text annotations
• Export to high-resolution formats
Remember to maintain a balance between showing enough detail to understand the system's architecture while keeping it clean and readable. The focus should be on the interaction between components rather than internal implementation details.