flynfrog wrote:why not put a speed limit in corner then skip right to your end goal. teams could use a pit road speed limiter set for each corner.
You are not being serious, are you?
flynfrog wrote:Let me use the example of Eau Rouge how you plan to separate the vectors out for down force in that corner? You have a massive G spike do to the rise an fall of the track that to the sensors on the wheel hub is going to look like a spike in DF. You could do a reference back to an accelerometer on the chassis run it through a filter in the code of some kind but its still just a shot in the dark as to what your are measuring.
I don't understand why you come back to that point. There is no secrete to digital data processing. Let's assume the values of the vertical wheel force component and the vertical acceleration are measured every 100 micro seconds. The mass of the car and the driver is also evaluated from an algorithm, from start values and integration of fuel consumption at the same time interval. The weight, the inertial forces (even in extreme spike conditions) and the sum of all vertical wheel forces are determined again within the loop interval in real time. Another algorithm detracts the resulting vertical inertial force and the weight from the all wheel force again in real time. What you get in the end is the downforce 10.000 times per second as a physical value. This computer program would run on every car's SECU in exactly the same way. You can run a car through a roller coaster upside down and you would still get several exact downforce figures for every foot of the track.
flynfrog wrote:Also DF is highest at the end of the strait not the corner so setting a max level for the track might not directly affect corner speed. Your rule fails to take into account the root cause of the "problem" you think F1 has. I think breaking bumps of a poorly maintained track would go farther in limiting corning speeds then your proposed rule.
No, sorry but you are wrong on both counts. I don't mind that max downforce could happen on forward and backward acceleration and not lateral. First, you can analyse the direction of acceleration and disregard peaks that go rearward. Those data could be used to regulate breaks if there ever are issues of safety which require addressing those. Second, a poorly maintained track with bumps would result to inertial force peaks. Those would be eliminated automatically from the wheel forces and would not show up in the downforce trace.
flynfrog wrote:your rule will have no affect on cost and it sure as hell wont be equal for all. Even setting strict cost rules wouldn't do that.
Of course it would be equal for all. I have already explained that above, because the ECU would run the same program for all cars with the same sensors. I don't quite understand why you still think that keeping very wide and stable geometric rules would not save cost. Of course it would! Every time you change the geometric rules you have to run through an optimization phase which costs a billion dollars. This would be prevented by my rule proposal. Teams would continue to optimize drag reduction and they may even try occasionally to change the total approach and try a different configuration. But every one of the possible configurations leads to the same downforce. Only the drag changes over different tracks. Some teams may focus on a config for middle downforce, some for low downforce and some for high downforce. But all those configs would be known after a short time and only incremental improvements in drag reduction will be possible. The law of diminishing returns would discourage teams at one stage to continue very high aero budgets and the limited money would be spend on other research areas increasingly.