Dennis Román | Project Portfolio

Aircraft Icing

IPW Icing Verification Pipeline

End-to-end Fluent to FENSAP-ICE pipeline with Composer-style run generation, staged job control, and standardized post-processing artifacts for IPW-style verification studies.

ANSYS FluentFENSAP-ICEPythonSLURMMATLAB
IPW setup geometry screenshot

Domain and body layout used for the IPW verification workflow setup.

Problem framing

  • IPW icing workflows often lose repeatability between solver stages.
  • Manual stage handoff increases turnaround time and hidden setup drift.
  • This project enforces deterministic run structure and reviewable outputs across every stage.

Pipeline architecture

  • Fluent meshing and solve are launched from templated journals/sbatch scripts.
  • Flow state is transferred into FENSAP-ICE stages:
    • Flow
    • DROP3D
    • ICE3D
  • Post wrapper scripts process outputs into fixed artifact folders:
    • cuts_clean/, cuts_ice/
    • thickness/, mccs/
    • convergence/, logs/

IPW journals and runner architecture

IPW post-processing artifact flow map

Data view (from provided bundle)

Thickness summary

Span station y [m]Max thickness [m]Mean thickness [m]
0.45720.00971170.0018700
0.91440.01077110.0020506
1.37160.01005430.0022026

MCCS summary

Span station y [m]Max MCCSMean MCCS
0.45720.147640.02588
0.91440.161240.02516
1.37160.184950.02956

Final comparison package summary

DatasetCasesAgreement metric
MeanCCS 2D scan vs CFD trace6Best-aligned correlation = 0.996 to 1.000
MaxCCS 2D scan vs CFD trace6Included in full grid view
MinCCS 2D scan vs CFD trace6Included in full grid view

Grid-independence evidence (journal-defined sweep)

The chart below is built from ComposerV2/Run_L1T1 through Run_L5T1 journal defaults and shows the structured refinement schedule used in the study.

Grid-independence evidence from L1 to L5 journal parameters

Verification and reproducibility notes

  • ICE3D convergence outputs are captured as structured CSV (iceconv.dat.csv) for auditability.
  • Thickness and MCCS extraction are performed at fixed span stations for consistent A/B comparison.
  • Wrapper README and scripts define a repeatable sequence from conversion -> cuts -> metrics -> plots.
  • This project page now points directly to generated outputs, not just narrative claims.

Validation

  • Convergence indicators exported from ICE3D iterations

    pass

  • Final 2D scan vs CFD coordinate comparison package generated

    pass

Reproducibility

  • Composer/ComposerV2 templates

    Run folders and journals generated from templates to reduce setup drift.

  • Post wrapper layout

    ipw2_post_wrapper scripts produce consistent cut, thickness, mccs, and convergence artifacts.

  • Data traceability

    Key pipeline outputs mirrored into project media for direct review.