[MVRC] Mantium Virtual Racecar Challenge 2016

[LVDH]

Hi guys,
HP-Racing made me aware of an important bug. It should have affected anyone who properly reads the rules, so probably not Matteo.

I fixed it and uploaded the new version to the Challenge page:
http://mantiumchallenge.com/mvrc-the-rules/

You will have to wait a bit more for all the pretty picture post-processing as I am currently super busy getting something else done.

[CAEdevice]

You are right I actually did not notice it
What is the bug about?

[LVDH]

Nothing that special. When using "special_bc" like an engine inlet and you divide them by left and right, like the rules suggest, the OF case would monitor the left and right side. As the left side does not exist in the simulation it would crash. Now MantiumWFlow detects better if you have surfaces which should not be monitored. I also fixed some other small issues,

[CAEdevice]

Thanks! This happened only if I had two engine inlets? With the exhausts (two) I had no issues.

[LVDH]

Well I tested it. And I never had issues with having two surfaces for inlet or outlet either. Then HP-Racing reported it and was able to send me a case that confirmed it. But this was only on their second try. So somehow it did not necessary cause an issue. But when I looked into the code, the part that checks if a monitored surface is in the domain or not was missing for "special_bc" so a clear bug. Why it only affected some simulations remains a mystery to be solved, but not by me and not today or ever.

[HP-Racing]

Thanks! This happened only if I had two engine inlets? With the exhausts (two) I had no issues.

The issue only occurs when you put the left exhaust outlet surface into it's own stl. Having both left and right in one stl is fine.

[CAEdevice]

Thanks! This happened only if I had two engine inlets? With the exhausts (two) I had no issues.

The issue only occurs when you put the left exhaust outlet surface into it's own stl. Having both left and right in one stl is fine.

Thanks! Are you ready for the Green Hell?

[etsmc]

so I got in this morning to check my simulation and it has completed and am able to do the post processing on it to get the downforce, flow and CoP but opening the case.foam in ParaView I don't get the different mesh regions like the image below


all I get are the ones that start with auto and the internal mesh. could it be anything to do with the mvrc_fast option??
I am using ParaView 3.98.1 64bit

[CAEdevice]

The same for me with 3.98.1 (I use it only to show surfaceLIC). Try with Paraview 5.x.x (where the images are taken from).

[HP-Racing]

Thanks! This happened only if I had two engine inlets? With the exhausts (two) I had no issues.

The issue only occurs when you put the left exhaust outlet surface into it's own stl. Having both left and right in one stl is fine.

Thanks! Are you ready for the Green Hell?

No not yet. Trying to make a front diffuser work but we're not happy with the downforce levels we're achieving..

[LVDH]

Not being able to see the mesh regions is not a problem. They do not get displayed correctly in any Paraview version for decomposed cases. I suggest you load they case, select decomposed case option, click apply and then switch to the latest time step. Now you will be able to see the various mesh regions. I you want to load them separately you can do it now. Do not forget to hit the apply button once more after selecting.

[CAEdevice]

The issue only occurs when you put the left exhaust outlet surface into it's own stl. Having both left and right in one stl is fine.

Thanks! Are you ready for the Green Hell?

No not yet. Trying to make a front diffuser work but we're not happy with the downforce levels we're achieving..

For the the second race I will use last year car once again (MP004B), with minor updates. I will use the new one (MP005A) when (if), maybe for the faster tracks, the cooling inltes/outlets areas will be free.

[CAEdevice]

Not being able to see the mesh regions is not a problem. They do not get displayed correctly in any Paraview version for decomposed cases. I suggest you load they case, select decomposed case option, click apply and then switch to the latest time step. Now you will be able to see the various mesh regions. I you want to load them separately you can do it now. Do not forget to hit the apply button once more after selecting.

I tried with Praview 3.98.1 and I still don't see the mesh regions (I see them with 5.x.x), but I can use it with SurfaceLIC (that doesn't work with 5.x.x).

[LVDH]

For you it might be because you configured your Paraview to automatically switch to the latest time step. Try from there to deselect the mesh region or internal mesh, hit apply and reactivate it and hit apply once more.

[LETOUZE]

hello, I do not understand the column "power" (100; 73.0; 94.1; etc..... ) %

you can not use the engine at 100% if you degrade the aero?

welcome Patrick