To calculate the Oscillatory Shear Index (OSI) in ANSYS Fluent without using a User Defined Function (UDF), you can use the available post-processing capabilities of Fluent, although it may not be as straightforward as in some other software. The OSI quantifies the unsteady or oscillatory nature of the shear stress in a flow and is often used in studies of turbulence and flow behavior.
τmax\tau_{max}τmax and τmin\tau_{min}τmin are the maximum and minimum shear stress values over a period of time.
Steps to compute OSI in Fluent:
Set Up Transient Simulation:Make sure your simulation is transient and is capturing the necessary unsteady flow characteristics that result in oscillations in shear stress.
Monitor Shear Stress:In Fluent, go to Surface Monitors or Data Sampling to monitor shear stress (τ\tauτ) on the surface of interest (typically the wall or other boundaries where shear stress is of concern). Set the type of quantity you want to track as Wall Shear Stress (or similar). Set up a monitor for Wall Shear Stress Magnitude to track the variation of shear stress over time.
Extract Time Data:After running the simulation for a sufficient time (to capture several oscillation cycles), export the time-series data for wall shear stress from Fluent. This data will give you the oscillations in shear stress as a function of time.
Post-Processing:Export the time history data (shear stress vs. time) to a file. Use a tool like Excel or MATLAB to process the data:Identify the maximum and minimum shear stress values over a suitable time period. Apply the OSI formula to the time-averaged maximum and minimum shear stress values.
Visualize and Calculate:In your chosen post-processing tool, you can calculate the mean, maximum, and minimum values of shear stress over the data set. Compute the OSI using the formula above.
While Fluent doesn’t provide a direct built-in method to compute OSI in the post-processing stage without using a UDF, using its surface monitor tools and exporting time data allows you to calculate OSI externally. If you'd prefer more automation, using a UDF or a scripting approach within Fluent would be more efficient, but this method works as a practical workaround.