Cool, but I like the arrow keys better since I can change the image at the rate I want to

.

.

.

.

.

Sooo, with much more thinking about how to use ORSI, I have come up with a realization

The ORSI moving average filter does a GREAT job at predicting a single result value of interest if the result values are oscillating about a stable value

The problem lies in the fact that simulations currently do not stop when all the results values are nearest to their current ORSI value… This means that when your simulation ends (however triggered), you could be saving the full solution set of result values at any stage of their oscillations…

Even at 3000 iterations, both of these meshes’ sim runs have result values oscillating over about a 10% range…

So while we can predict a good single filtered value with ORSI, the solution sets will not represent data that represents those ORSI values… This means that my U magnitude images (based on solution set values at exactly 3000 iterations) WILL NOT SHOW WHAT WE EXPECT and in this case perhaps only within ±5%

Here are those U magntude images at iteration 3000 (with the ORSI values at 3000i shown AND the percent variation from ORSI of the solution set data values at 3000 iterations…

.

**This is just a caution post for when images from solution set data is presented…**

.

.

.

.

**EDIT: And even more importantly, this justifies the need to have ORSI… By that I mean, in the past people are generally just using the result values from the last iteration in their solver log when they say for instance that the CD of my sim results was 0.5 (or whatever). They likely even say that the results were stable without really knowing whether they were or not… They do not realize that if they stopped their 3000 iteration run just 15 iterations earlier the solver log could report at CD of 0.45 from the same run… (not so good is it)…**