Ok, updated...
You do not have rerun the simulation to post-process it. Just load it in the GUI and then hit the post-process button.
I wonder that too.CAEdevice wrote: ↑02 Oct 2018, 17:02Hi, I have a question (not related to the recent software update).
How are the numbers in the HTML computed? Are they an average of the values calculated in the last iterations? I find a lot of difference between the average of the last 10-50 iterations and the results.
Ok, problem solved: it was my fault. I used the new post processor with OpenFoam case created with an old version of WFlow. Anyway, I am still curious about the way the "avereged values" are computed during the post processing.CAEdevice wrote: ↑02 Oct 2018, 17:02Hi, I have a question (not related to the recent software update).
How are the numbers in the HTML computed? Are they an average of the values calculated in the last iterations? I find a lot of difference between the average of the last 10-50 iterations and the results.
Please get this over to the MFlow Q&A sections as there could be many reasons for this. I hope it is not the dot in your user name. You could right away upload the case, so I can check it.TalnoRacing wrote: ↑03 Oct 2018, 07:24I managed to get MantiumFlow working, it seems I had a "write access" security problem.
However, I installed the updated post-processing file, but now have the following error:
http://s284.photobucket.com/user/TalnoR ... c.jpg.html
The results are averaged over quite a period. Certain tests in the past have shown that even when I change meaningful parameters for the simulation, the results do not get affected enough to have an impact on your lap times. However you guys have started getting so close that I want to change the procedure of getting to the final results. I will not have time next week but will get some initial work on this started very soon and hope to have it ready for the next race.CAEdevice wrote: ↑03 Oct 2018, 09:38Ok, problem solved: it was my fault. I used the new post processor with OpenFoam case created with an old version of WFlow. Anyway, I am still curious about the way the "avereged values" are computed during the post processing.CAEdevice wrote: ↑02 Oct 2018, 17:02Hi, I have a question (not related to the recent software update).
How are the numbers in the HTML computed? Are they an average of the values calculated in the last iterations? I find a lot of difference between the average of the last 10-50 iterations and the results.
Considering that we are going to completaley change the cars after the last "efficiency" track, I think that any significative change should be delayed after race 3 (except arrow heat exchangers beacuse I have a solution ready since last year... I am kidding of course)
After the disappointing results of the last race (not the postion but the CFD numbers) I was tempted to design a new car, but the time is not enough because I am too busy with my job, so I will go on with refinement.
I wish we can race togheter with LDVH and Chris (and Variante, JJR, TF, ...). Maybe a "single race" event, an "All Star game" with better mesh refinement, transient simulations etc?