I am pretty sure this is not AI in the sense of what passes for AI in the last 3 years.
“The algorithm” here is probably not more than a meduim complexity excel sheet, only running in real time and not on Excel.
My friend, the problem in question is not 'the quantum' (rate/duration) of charge/discharge , but the 'timing' of it => 'how-much' is not the issue, 'when' is the issue. The throttle pedal is a 'suggestion' now, rather than the 'command' it used to be before. The timing is decided by a computer based on how it 'senses' the position of the car on track (GPS ? distance covered ? custom positioning signal ? I'm not sure, but whatever it is, it's based on some 'learning' from previously fed data, in tandem with actual data collected during practice).spokes wrote: ↑23 Jul 2026, 19:53Just putting my boring solution to all these "algorithm" "ai" deployment issues into the ether...here's to hoping someone at the FIA makes this the rule![]()
I think this should, and could, be solved by having power modes that are closely related to the driver's throttle pedal position, and limit the amount of modes allowed (let's say 10). This way, engineers can work on developing deployment modes specific to tracks, but the driver controls which mode he uses.
For example, you have power modes 1-10, mode 1 deploys the least amount of energy, but inversely, harvests the most. therefore focuses on harvesting. Mode "5" delivers a balanced amount of energy deployment, and recharges an equal amount, allowing drivers to charge up what the same amount they use in a lap. Mode 10 would provide the most power, but not to exceed what the driver's right foot requests.
If the driver is giving 100% throttle he's getting 100% battery deployment, or if the driver is giving 50% throttle he's giving 50% of the battery deployment etc.
In this way, engineers can setup the modes specific to the track conditions, and drivers can get dependable output, allowing them to change modes when they need something from the battery/power unit.
I love the way you put it! a suggestion versus a command.venkyhere wrote: ↑23 Jul 2026, 20:53My friend, the problem in question is not 'the quantum' (rate/duration) of charge/discharge , but the 'timing' of it => 'how-much' is not the issue, 'when' is the issue. The throttle pedal is a 'suggestion' now, rather than the 'command' it used to be before. The timing is decided by a computer based on how it 'senses' the position of the car on track (GPS ? distance covered ? custom positioning signal ? I'm not sure, but whatever it is, it's based on some 'learning' from previously fed data, in tandem with actual data collected during practice).
Its the most f****ed-up way to implement ANY RACING series.