It’s not an exaggeration to say that in:Flux was conceived around one idea: automatic, adaptive meshing. Why?
Ask any CFD engineer about meshing and they will tell you it takes up most of their time. This is fine for small projects, but if the future of CFD lies in projects of several thousand simulations, then automatic meshing is the only option.
But it is not just a practical consideration. Meshing is a […]
Let me make a bold statement about CFD:
Simple models perform above expectations; the opposite is true of complex models.
By and large, this is my experience with models used for practical project work. Take turbulence models. There is nothing a CFD professional loves more than to explain why a Reynolds-Stress turbulence model (RSM) is better than an Eddy-Viscosity Model (EVM). Yet EVMs eclipse RSMs when it comes to industrial usage, reliability […]
I started writing my first CFD code in 2007. Back then, it seemed obvious to me that CFD codes should be general purpose, and written for skilled CFD practitioners. “If you can’t write down your wall functions,” I thought, “you really shouldn’t be using a CFD code.”
Things changed. Around 2009 I became interested in whether CFD codes designed with a single purpose could outperform general purpose CFD codes. I was […]
The most common request we get from our users is to add a fire modeling capability to in:Flux CFD.
Yet there are existing, established fire modeling CFD codes out there – so why is everyone looking for something new?
The truth is that fire modeling is an onerous task, and often a bottleneck delaying project completion. When designing in:Flux, our goal was to package the most modern CFD tech into a lightning-fast […]
Find us