[MVRC] Mantium Virtual Racecar Challenge 2017

[Alonso Fan]

Thanks LDVH, may Chris summarize the rule update?

I am getting crazy with the first race model: I only changed two small things (minor legality issues) and now it stops after meshing (successfully) when solving the first iteration.
Tommorw I will try with MFlow v2017.7.

Same issue here

[LVDH]

2017.7 could indeed help. Please try it and let the others know what happened.

[CAEdevice]

2017.7 could indeed help. Please try it and let the others know what happened.

I sent you the logs: I can only find that the solver crashed during first iteration. The mesh seems to have been completed.

[cdsavage]

Thanks LDVH, may Chris summarize the rule update?

The changes should all be highlighted in yellow. There are only two things worth mentioning:

• We are adding the once-per-season deadline waiver. You can extend the deadline by two days but you must ask to do it before the deadline passes.
• The wording was changed in K1.4 to make it clear that the left and right parts for special_bc, monitoring_surfaces and porous_media must be submitted as separate STLs. This was a common problem in round 1.

[rjsa]

About the crashes, I had an odd one - I can't remember in exactly which phase - that was caused by a rogue binary STL.

[CAEdevice]

Update: with MFlow 2017.7 the "first iteration" has been solved (the first test, with a geometry that failed with 2017.6 has been successful). Thanks!

[Alonso Fan]

Update: with MFlow 2017.7 the "first iteration" has been solved (the first test, with a geometry that failed with 2017.6 has been successful). Thanks!

Oooh this is good news. I will try a simulation today and confirm if the issue is also fixed on my side

[rjsa]

Hi guys,
sorry I was so quiet lately. I was simply working like crazy. I have made some small improvements to the software. You can now download version 2017.7. It seems to solve some issues you guys had with solver stability. I say "seems" because I did not have very much time to check it extensively. Maybe some people can test it and esp. rsja can possibly confirm that his simulations are now a bit more stable, we should go for using this version for the next race which seems to be next week already.
Also there is an update to the rule book. I did not have a look yet but also there the changes should be minimal.

I'm re-running my last interaction on it.

This you get to look into the windows/linux report issue?

[Alonso Fan]

Update: with MFlow 2017.7 the "first iteration" has been solved (the first test, with a geometry that failed with 2017.6 has been successful). Thanks!

Oooh this is good news. I will try a simulation today and confirm if the issue is also fixed on my side

issue seems to be fixed. simulation is currently on iteration 540 or so

Although issues with my car don't seem to be fixed at all...

[CAEdevice]

Completed first run: dr and df changed slightly, but cooling flow is now much lower.
The post processing issue still happens (I get only a few images).

[rjsa]

I'm still running it but the intake flow that I had fixed went craaaaaaazy.

[CAEdevice]

I'm still running it but the intake flow that I had fixed went craaaaaaazy.

Same for me now... luckily it oscillates (a lot) into a valid range.

[rjsa]

I'm still running it but the intake flow that I had fixed went craaaaaaazy.

Same for me now... luckily it oscillates (a lot) into a valid range.

Yep, for me anything between -1 and 4. By the looks it'll average around 2

By the way, as the new guy I'm a bit lost with names. My name is Ricardo. I've caught a few names:

-Matteo
-LVDH is André, right?
-Chris

Who else?

[rjsa]

Yup, intake really bad, but positive. HX flow wrnt below 1.5 and dropping solidly by the end of the run.

I'd like to know if it's going to be used as I have two very distinct development paths ahead of me.

[CAEdevice]

I have a reduced cooling flow too (-10%). No problem for this (high df) race, but I hope the solver remain the same in the last three races (efficiency).