F1technical.net

I know why i got the penalty but that time (1.07) is funny. You guys could just gave me a one place penalty or something.

Thank you for the help guys, I appreciate the advice. I will review each comment and see if I can make noticeble improvements for the next round.

Ft5fTL wrote: ↑

28 Sep 2018, 20:42

I know why i got the penalty but that time (1.07) is funny. You guys could just gave me a one place penalty or something.

Andre knows how it is calculated... I believe it’s a percentage of the average lap time...

Ft5fTL wrote: ↑

28 Sep 2018, 20:42

I know why i got the penalty but that time (1.07) is funny. You guys could just gave me a one place penalty or something.

After looking into this, I see where this frustration comes from.
When putting everything into a table, I noticed that the cooling flow of Talno submitted to machin was wrong. With the correct values he had a much worse lap time.
The penalty time added to your lap time you guys get are calculated as follows: MIN(Average lap time, 107% of best lap time)*0.01. In this case the average lap time was the smaller one.
Unfortunately the new lap time of Talno increased the average lap time so much that you lost a position because of this. I am sorry for the mistake I made. It is a bit dumb that with all the work that goes into this, in the end copy-paste errors happen.

Ft5fTL wrote: ↑

24 Sep 2018, 16:01

By the way, i dont know it's an error or LVDH does some magic on the software for getting them, i don't have the surface lic type post proccessing that LVDH posted a couple of posts before this. Also that blue cp_tot looks cool.

SurfaceLIC can be enabled in Paraview by going to the toolbar: Tools -> Plugins -> SurfaceLIC and enabling that.
It's a hidden plugin that's disabled by default.

Ft5fTL wrote: ↑

29 Sep 2018, 18:12

Ft5fTL wrote: ↑

29 Sep 2018, 18:11

BlakjeKaas wrote: ↑

29 Sep 2018, 16:27

SurfaceLIC can be enabled in Paraview by going to the toolbar: Tools -> Plugins -> SurfaceLIC and enabling that.
It's a hidden plugin that's disabled by default.

I meant getting lic pics with MantiumFlow's post proccessing. I have some issues with paraview.

Sorry guys for the double post, my browser seems to have some issues with the edit button lol.

"Licence file seems to have expired" when launching Mantium Flow.

variante wrote: ↑

01 Oct 2018, 00:52

"Licence file seems to have expired" when launching Mantium Flow.

can confirm this is the same on 2018-7c and just tried 2018-9.

Cool start into a Monday. I will check and fix this.

New version is up.

Ft5fTL wrote: ↑

29 Sep 2018, 18:12

Ft5fTL wrote: ↑

29 Sep 2018, 18:12

Ft5fTL wrote: ↑

29 Sep 2018, 18:11

I meant getting lic pics with MantiumFlow's post proccessing. I have some issues with paraview.

Those surface lic visualizations were done in Paraview. They are currently not supported in MantiumFlow.

LVDH wrote: ↑

01 Oct 2018, 13:21

New version is up.

Awsome, thanks for the quick turn around.

Hi, next race is very far, so it is time to announce the prize for this season.

Last year I had many difficulties with the shipping (MVRC is a worldwide competition much more than I could imagine), that is why I decided to radically solve the problem.

The first prize will be a 100€ worth translation to a Bitcoin wallet (in ten years maybe your victory in MVRC will have additional positive consequences than glory) and a free consultancy by myself about setting-up a safe bitcoin wallet (my second job is about cryptocurrencies). In addition to that, the final winner will see its name eternally written into the Blockchain.

CAEdevice will be excluded by any prize as usual (but this year I think that it will not be necessary). Small special prizes will be possible, but they will be arbitrarily assigned (to be a MVRC journalist or media manager might be a good point).

LVDH wrote: ↑

01 Oct 2018, 13:21

New version is up.

just run a case with 2018-10 and it ran through ok but did not show the values for each part just the total. Also when I tried to Post Process I got a licence expired message too.

Ah, crap. I did not update the post-processor. The forces per part are only gone in the solver.log as it was just too much text. The post-processor later includes them into the report. Assuming it works...

I will try to get this fixed today.