Development Notes

Design documents, implementation plans, and active task tracking.

Active Design Documents

These documents describe implemented or in-progress architecture:

• TODO
  • Miscellaneous
  • Primary Features
  • Supplementary Features
  • Build System
  • Refactoring
  • Unit Test
  • Python Integration — Package Restructure Plan
• MeshConnectivity Implementation Plan
  • 1. Scope
  • 2. Ownership Model
  • 3. Core Operations (DSL)
  • 4. MeshConnectivity Class Design
  • 5. Implementation Phases
  • 9. Periodic Face Deduplication: The Collaborating Check
  • 6. Boundary Entities in the Framework
  • 7. Testing Strategy
  • 8. File Layout
  • 9. Templatization of MeshConnectivity (Row-Size Parametric)
  • 10. Per-Adjacency Index State Tracking
• Unified Mesh Helper Design
  • Problem
  • Design
  • Composition examples
  • Migration plan
  • Resolved questions
• Multi-Layer Ghost Cell Support
  • Current State
  • Goal
  • Resolved decisions
  • Design
  • Implementation order
  • Files to modify
• Distributed Entity Reordering — Design Document (v2)
  • Table of Contents
  • Motivation
  • Scope
  • Concepts and Terminology
  • Entity Dependency Graph and Propagation
  • Adjacency Conversion Rules
  • PermutationTransfer Utility
  • ReorderEntities – Top-Level Algorithm
  • Companion Array Handling
  • Dynamic Reorder Registry (Decoupled from UnstructuredMesh)
  • Integration with AdjPairTracked and fillRegistry
  • Local-Only Fast Path
  • Concrete Use Cases
  • Implementation Plan
  • Appendix: Re-evaluation Notes (v1)
  • Implementation Notes
• UnstructuredMesh Refactoring Plan
  • 1. Current State
  • 2. Refactoring Phases
  • 3. Implementation Order and Risk Assessment
  • 4. Smooth Solver Variant Status
  • 5. Adj Conversion Method Summary
  • 6. Test Coverage After Refactoring
• CFV Module Refactoring Plan
  • 1. Current State
  • 2. Refactoring Phases
  • 3. Implementation Order and Risk Assessment
  • 4. Dependency Graph After Refactoring
  • 5. Typical VR Configurations (for Testing Reference)
  • 6. Final Summary
• Euler Module Refactoring Plan
  • 1. Current State
  • 2. Identified Refactoring Points
  • 3. Refactoring Phases
  • 4. EulerP Comparison Notes
  • 5. Completed Work Log
• Code Review: dev/harry_refac1 Branch
  • Table of Contents
  • 1. Executive Summary
  • 2. Refactoring Phases Overview
  • 3. Phase 1: Eliminate Duplication
  • 4. Phase 2: Method Decomposition
  • 5. Phase 3: Coupling & Organization
  • 6. Element Traits System
  • 7. Serializer Improvements
  • 8. Test Infrastructure
  • 9. Issues Found
  • 10. Recommendations
  • Appendix: Files Changed
  • 11. Actionable TODO List for Code Cleaning
  • Summary

Historical Notes and Benchmarks

The following files are preserved for reference but are not actively maintained. They contain early brainstorming, personal observations, and one-off benchmarks.

• DNDSR Ideas
  • Next Step:
  • About Periodic:
  • About Exporting Static Interfaces
  • About Increasing Performance:
  • mesh elevator
• Notes
  • on periodic boundary
  • Point communication race:
  • on running with bssct:
  • building hdf5 and cgns
  • On DLR and curve mesh:
  • On oneAPI on windows
  • intOrderVR
  • OMP
• CUDA Notes
  • About Eigen
  • Thread load
  • Compilation
  • Silent error
  • JIT
• EulerP Tests
  • Periodic shock box
• Initial Report