Going to test it overnight.
Just one thing: in MVRC template lref = 3.4, however in MVRC_Long lref = 1.0... which one is correct? I would guess 3.4...?
EDiT: version 2003 (Windows) still pops-up "cannot run runFile"
Thanks!
Going to test it overnight.
Thanks!
I don't know if was specific to one run or not, but I've noticed for my latest test the HX volume flow at the top of the report seems correct, but in the Virtual Stopwatch section at the bottom of the report it's outputting '6' as the flow value. Definitely not double the value at the top fwiw
Can confirm, my value at the bottom is also '6', meanwhile the value for heat ex flow rate at the top is definitely not '6'yinlad wrote: ↑Mon Apr 06, 2020 12:07 pmI don't know if was specific to one run or not, but I've noticed for my latest test the HX volume flow at the top of the report seems correct, but in the Virtual Stopwatch section at the bottom of the report it's outputting '6' as the flow value. Definitely not double the value at the top fwiw
Overlooked this here. The one is actually correct. I compensate for the correct wheelbase way later in the post-processing.
So lref = 1.0 is correct. Okay.LVDH wrote: ↑Mon Apr 06, 2020 6:00 pmOverlooked this here. The one is actually correct. I compensate for the correct wheelbase way later in the post-processing.
I am now on this strange windows issue. I hope I can somehow replicate it. It is so frustrating that it affects so many of you, but so far it passes my tests.
When the first submission gets close, you should take care of verifying if this approach is OK.
Yes, at some point I set a better looking color map as default, if you like the old one, you can always go back.
I think that might be not needed as new MFlow runs now. We'll see tomorrow if everthing goes well.
I meant Cp slices. For the rest it's definitely better.
Streamlines and the surface visualizations take the longest. The iso surfaces are pretty fast, deactivating them will not change much. The streamlines are faster, the fewer triangles the monitoring surface contains, but as you have all hopefully learned, you should then not trust the measured value if you do not have enough triangles:wb92 wrote: ↑Mon Apr 06, 2020 9:29 pmI meant Cp slices. For the rest it's definitely better.
Meanwhile I disabled some post-pro options (streamlines, isosurfaces, etc.) and that gave huge time reduction to see what's going on with the car. However I increased drastically number of pictures to generate, still seems quicker than last year.
I also got the out of space error, but I don't actually think I was out of space, so not sure what was going on therejjn9128 wrote: ↑Tue Apr 07, 2020 8:39 pmHow do we change what images are output? e.g. I'm getting an "out of space" error because I'm outputting 50 X slices, but all I'm really interested in is CpTot - can I deactivate Ux, Cp...etc? Similarly I'm not interested in the +/- 0.5 on the surface Cp contour.