Problem:
It is common when comparing experimental and CFD results to use time-averaged fields, this usually includes mean-velocity, velocity fluctuation, and resolved stresses. But others may be beneficial.
Workaround:
This can be done post process, however, with there being a data limit to result files it is simply implausible to get quality average data from the number of timesteps we can get from a moderate mesh, further to this the download file is usually large.
Feature request:
Creating time-averaged results made available from the result controls would allow time-averaged results based upon every solved timestep without needing to save every timestep.
Thanks for reading,
Darren