Skip to content

Limitations

Jump to bottom
KFC edited this page Apr 25, 2025 · 1 revision

Limitations and Delimitations (Beta Version)

StructoPyre is currently in Beta development as a Minimum Viable Product (MVP). While it aims to provide valuable insights into structural fire resistance, it's essential to understand its current limitations and the intended scope of the project.

Scope & Standards

  • ACI 216.1M-14 Focus: The simulation logic for fire resistance is primarily based on the prescriptive methods (tables, figures, basic calculations) outlined in ACI 216.1M-14: Code Requirements for Determining Fire Resistance of Concrete and Masonry Construction Assemblies.
  • Concrete Structures Only: The current implementation focuses exclusively on concrete elements (slabs, beams, walls, columns). It does not include calculations or considerations for:
    • Structural steel framing (beyond concrete protection, which is also not yet implemented).
    • Timber construction.
    • Composite materials.
    • Masonry elements (even though covered in the ACI 216 standard, masonry checks are not yet implemented in the application).
  • Prescriptive Methods Only: The application utilizes the simpler, prescriptive methods (e.g., minimum thickness/cover tables like Table 4.2, 4.3.1.1, 4.5.1) from ACI 216.1M-14. The more complex Analytical Methods (Section 4.4), which involve calculating temperature distributions and reduced material strengths, are not implemented.
  • Protected Steel Columns: Analysis of steel columns protected by concrete or masonry (covered in ACI 216 Sections 4.6 and Appendices) is not included in the current scope.
  • Evacuation Dynamics: This module is a planned core component but is not yet implemented or is in very early stages.

Simulation & Analysis

  • Simplified Fire Model: The fire source placed using the X key is currently a visual placeholder (grey cube). It does not simulate:
    • Realistic heat release rates (HRR).
    • Heat transfer physics (conduction, convection, radiation) to surrounding elements.
    • Combustion details or fuel consumption.
  • Simplified Fire Spread: The mechanism for fire spreading between compartments is conceptual (based on barrier failure times) and *not based on fluid dynamics or detailed heat transfer
  • No Complex Structural Analysis: The application does not perform Finite Element Analysis (FEA) or calculate internal forces (moments, shears). "Failure" is determined by comparing an element's user-defined or default properties (cover, thickness, dimension) against the time-based requirements derived from ACI 216 prescriptive tables/figures. It does not assess actual load-bearing capacity reduction beyond these checks.
  • Limited Real-World Variables: The simulation does not account for many factors influencing real fires, including:
    • Ventilation conditions (natural or mechanical).
    • Specific fuel loads or arrangements within compartments.
    • Wind effects.
    • Sprinkler system activation or impact.
    • Detailed material behavior like specific spalling patterns (beyond general ACI assumptions).
  • Accuracy Dependent on User Input: The accuracy of the simulation results critically depends on the user providing correct material mappings and, crucially, accurate element-specific ACI parameters (cover, thickness, restraint, element type). Since the UI for inputting these parameters is still under development, current results rely heavily on potentially inaccurate default values.

User Interface & Experience

  • ACI Properties Input UI: The interface for users to select model elements and input specific ACI properties (cover, thickness, etc.) is currently missing or incomplete. The application uses hardcoded defaults, limiting practical accuracy.
  • Limited Settings: Options within the Settings menu (Hamburger icon) are currently limited or non-functional.
  • Basic Visualization: Visual feedback is limited to color changes (Green/Yellow/Red/Black) based on pass/fail checks against ACI requirements. It does not visualize temperature gradients or detailed stress patterns.

Performance & Technical

  • Potential Performance Lag: The application, especially with complex 3D models, may experience performance issues or lag ("Medyo lag pa") during navigation or simulation in the WebGL environment.
  • Browser Input Quirks: Users may occasionally experience conflicts or inconsistencies with WASD/Mouse navigation controls depending on their browser and operating system.
  • WebGL Constraints: Very large or complex models might exceed memory or processing limits within the WebGL environment.

Understanding these limitations is key to interpreting the results from the current Beta version of StructoPyre. Future development aims to address many of these points, particularly the implementation of the ACI Properties Input UI and the Evacuation Dynamics module.

Clone this wiki locally