andylaurence wrote:Why are you simulating at 160kph? Are there lots of 160kph corners? The average speed for Loeb was about 145kph, despite clearly doing 250kph in places. That suggests that apex speeds are generally far lower. I'd wager 100kph would be more representative, although I have no data to back that up other than gut feel. 160kph is a lot of speed to be carrying through a corner - I've not cornered that fast all season.
That is a good point here Andy. I will explain why 160km/h:
1) As you said, Loeb's time was 145km/h average. I would think that it is possible to go faster, probably 150km/h average, but higher would be more difficult. So in that sense, 160 is too high. But then, I also wanted to have the car competitive in other hill climb races where average speeds are often higher than 160-170km/h.
2) I would say that Pikes Peak hasn't got a large variety of corners. It is either slow hairpin or fast corners, and we know that in slow hairpin the tyres are making more difference than pure aero. So it is not wrong to design the car for high speed corners.
3) I will also not "optimize" the car in the sense "trying to enhance the lift and drag". The aim of my project is to develop a Pikes Peak car, reach my objectives and then assess changes in aero performance depending on yaw and altitude. I also plan if I have time (which I think I will) to optimize the car for yaw condition, and of course that will be at 160km/h but it is not the main objective of the project (which again was to develop a Pikes Peak Subaru Impreza).
So yes, 160km/h might be a bit too high, I should have reduced it to probably 140km/h, but when I wrote the downforce objective, it looked like this: 1000lb @ 100mph which I found nice to present. Round numbers. If I really had to make for real a Pikes Peak car for sure I would adapt different things such as a limit on the downforce, lap time simulation to define aero parameters to achieve, etc.
Hope it helps