F1technical.net

On the html report, it says the cop in all 3 directions. Is this the real cop?

Not sure what you are looking at but the report does not contain any numbers, so there is no CoP.

The post processing is great, congratulations to MantiumCAE!

On the other side, I am very disappointed about my car (it is not a matter of numbers).
It seems that some "extreme" details that worked with OCCFD settings doesn't work with the new evironemnt (and this is a good thing from the point of view of realism).

Can I ask LDVH wich are the main changes about settings, mesh and parameters between the case generated by WFlow and by OCCFD? I know... I could open the "System" directory, but OI am at home and I don't have any old simulation with me.

CAEdevice wrote: Can I ask LDVH wich are the main changes about settings, mesh and parameters between the case generated by WFlow and by OCCFD? I know... I could open the "System" directory, but OI am at home and I don't have any old simulation with me.

Well the mesh is similar to what you had in respect to mesh resolution. But now we have about 5 surface layers and for snappyHexMesh with a good coverage. These 5 extra layers help to resolve what is happening close to the walls much better. This means that esp. separation is now simulated better. My plan for next year is to switch to second order accurate equation solving. That will then make everything much more realistic. For now I left it at first order because I did not want to change too much from KVRC and because I did not exactly know what kind of CAD quality I could expect from you guys. But as the CAD quality was actually very good and the one car that had bigger problems will be much better next time I am very confident that we will be able to make that switch next season.

I'm referring to this in the html file

LVDH wrote:But now we have about 5 surface layers and for snappyHexMesh with a good coverage. These 5 extra layers help to resolve what is happening close to the walls much better. This means that esp. separation is now simulated better

Yes, it is exactly what I was talking about!

LVDH wrote:My plan for next year is to switch to second order accurate equation solving. That will then make everything much more realistic. For now I left it at first order because I did not want to change too much from KVRC and because I did not exactly know what kind of CAD quality I could expect from you guys. But as the CAD quality was actually very good and the one car that had bigger problems will be much better next time I am very confident that we will be able to make that switch next season.

If a general "tuning" of the simulation (inlcuding 2nd order) and less rules about the inlets/outles areas would proposed after the second race, I would completely agree!

Alonso Fan wrote:I'm referring to this in the html file

http://i68.tinypic.com/2en865z.png

It is a slice through the 3D filed in X-direction at x=-1.5m.
Cp is the dimensionless static pressure coefficient. There is no "o" between the "C" and the "p" by the way.
I hope you noticed that you can click on those small balls below the pictures.

CAEdevice wrote:
If a general "tuning" of the simulation (inlcuding 2nd order) and less rules about the inlets/outles areas would proposed after the second race, I would completely agree!

If too much stuff gets changed something that politicians call "unintended consequences" happens. So I will not change too many things. But for the low downforce races I see good chances of relaxing the cooling rules.

Is only my impression or the importance of efficiency is growing up race after race? (This would be a good question for Machin)

Thanks for explaining

I was wondering if the reports are generated using Paraview and surfaceLIC: I am still having problems with SurfaceLic and the latest release of Paraview. I would try with an older release, but before unistalling I would like to be sure that ising a "decomposed" case is not related with surfaceLIC crash.
Another point is: wich is the difference between "MPI" and "not MPI" release of Paraview?

What is the css file and what does it contain?

Alonso Fan wrote:What is the css file and what does it contain?

CSS = cascading style sheets

It is where the graphic settings of the html report are stored: nothing to do with the simulation.

Cool

Does anybody know how to produce, in Paraview, streamlines on the surface of the car?? ...and velocity field as well

Setting the "velocity" parameter directly on the car surface produces a uniform "zero velocity" surface (as it should be); also, the surface streamlines are not the required ones.
Offsetting the surface of the car by a few mm (or by a few mesh cells) should do the job, but I don't know how to do that in Paraview.

compliance check complete, only a couple of minor issues. waiting for the numbers now!