[MVRC] Mantium Virtual Racecar Challenge 2022 (Grand Prix Cars)

[yinlad]

I think, they have to stay in their volume. But I kind of think, it could be possible.

Could you confirm that the floor fences are excluded from the trailing edge rule re 10mm thickness i.e. they should be 10mm from start to finish. Also how do rounded front/rear faces of the fences factor into this?

Also for car submission, the rules state 'RV_RR_WING_V02' should be in the high res folder, should 'RV_RR_WING_PROFILES_V01' also be included in high res?

[RicME85]

Previously rounded faces were fine as long as they weren't extremely thin

[AratzH]

I think someone might have mentioned this already, but using the latest MFlow (2007d) the car is offset from the ground, despite it being correctly located in CAD and blender.


Looking at the blockMeshDictionary, the Z coordinate of the floor seems to be wrong:
vertices
(
(-15 0 -0.315)
(45 0 -0.315)
(45 15 -0.315)
(-15 15 -0.315)
(-15 0 18)
(45 0 18)
(45 15 18)
(-15 15 18)
);
I would think -0.05 is the right number if 50mm ground clearance from plant to ground is needed.
Everything else seems fine, including wheel center calculation.

[LVDH]

I think, they have to stay in their volume. But I kind of think, it could be possible.

Could you confirm that the floor fences are excluded from the trailing edge rule re 10mm thickness i.e. they should be 10mm from start to finish. Also how do rounded front/rear faces of the fences factor into this?

I think Appendix 1. covers this. Most of your fence will be 10mm. It can be rounded at the front and reduce the thickness getting closer to the trailing edge.

Also for car submission, the rules state 'RV_RR_WING_V02' should be in the high res folder, should 'RV_RR_WING_PROFILES_V01' also be included in high res?

You are right. I also found another small mistake researching this. I will make a few modifications to the rules. I know, it is close to the first race and I do not like it. But some parts are a bit wrong. I will only change wordings with clear mistakes. They should not affect your designs, if you tried to read the rules with their intentions in mind.

[LVDH]

I think someone might have mentioned this already, but using the latest MFlow (2007d) the car is offset from the ground, despite it being correctly located in CAD and blender.
https://ibb.co/5xsZqfq

Looking at the blockMeshDictionary, the Z coordinate of the floor seems to be wrong:
vertices
(
(-15 0 -0.315)
(45 0 -0.315)
(45 15 -0.315)
(-15 15 -0.315)
(-15 0 18)
(45 0 18)
(45 15 18)
(-15 15 18)
);
I would think -0.05 is the right number if 50mm ground clearance from plant to ground is needed.
Everything else seems fine, including wheel center calculation.

Ohoh, this is not good... I will check it.

[yinlad]

You are right. I also found another small mistake researching this. I will make a few modifications to the rules. I know, it is close to the first race and I do not like it. But some parts are a bit wrong. I will only change wordings with clear mistakes. They should not affect your designs, if you tried to read the rules with their intentions in mind.

Now I'm scared can you let us know when they are updated?

[LVDH]

Rules are updated. I can also confirm the issue with the floating car. I have fixed it and as people have already submitted cars, I am running a case now. If everything works, I will release the fix tomorrow morning. For those interested running a simulations today, you have to fix the blockMeshDict file:

It should look like this:

vertices
(
(-15 0 -0.045)  
(45 0 -0.045)  
(45 15 -0.045)
(-15 15 -0.045)
(-15 0 17.955)
(45 0 17.955)
(45 15 17.955)
(-15 15 17.955)
);

There is a chance to delay Race 1 by two days. Not sure about that though.

[CAEdevice]

Rules are updated. I can also confirm the issue with the floating car. I have fixed it and as people have already submitted cars, I am running a case now. If everything works, I will release the fix tomorrow morning. For those interested running a simulations today, you have to fix the blockMeshDict file:

It should look like this:

vertices
(
(-15 0 -0.045)  
(45 0 -0.045)  
(45 15 -0.045)
(-15 15 -0.045)
(-15 0 17.955)
(45 0 17.955)
(45 15 17.955)
(-15 15 17.955)
);

There is a chance to delay Race 1 by two days. Not sure about that though.

Does the problem also occur with the Linux version? It seems to me that the car is properly aligned (I don't use the GUI, but the pictures produced after post processing look ok). Is it possible to check with the car I have already submitted (CAEdevice2022_Race01_Sub01)?

[G-raph]

You might also want to check the wheels rotation speeds.
I could not manage to run the entire car properly (because my computer keeps crashing), but on the few tests I did (albeit not on the very latest version), I spotted that the front wheels were over-rotating and the rear wheels were under-rotating.

[AratzH]

Good point,
Wheel speed seems to be wrong too...


Also, despite having manually updated the blockMeshDictionary, it seems like at run time it gets reverted back to the wrong values...

[JJR]

.. and force coefficients also in "z" dirrection are set to -0.315

[LVDH]

.. and force coefficients also in "z" dirrection are set to -0.315

I do not think that it would make a real difference, but I cannot confirm this finding. Are you sure, you used the newest MFlow?

[JJR]

.. and force coefficients also in "z" dirrection are set to -0.315

I do not think that it would make a real difference, but I cannot confirm this finding. Are you sure, you used the newest MFlow?

Yes , I was using "c" verion . In "e" version I just downloaded it is OK. Thank you Andre.

[CAEdevice]

Should I update the software if I am using the Linux version?

[AratzH]

New version seems to work regarding floor location and wheel rotation speeds are, at least, equal in the 0/U file.
I'll report on results in a few hours.