Define Planning Output Metrics (click for notes)

[ethancoon]

Description

Document the output metrics needed for pre-race strategy planning.

Include:

• Finish SOC
• Minimum SOC
• Target SOC
• Laps completed
• Distance completed
• Average speed
• Whether the full race window was completed
• Whether minimum SOC was reached
• Energy margin relative to target SOC
• Feasibility status
• Planning warnings

Explain what each metric means and why it matters for race planning.

Acceptance Criteria

• A planning metrics document exists.
• The document defines each required planning metric.
• The document explains how energy margin should be interpreted.
• The document explains the difference between target SOC and minimum SOC.
• The document identifies which metrics are already available.
• The document identifies which metrics still need implementation.

Notes

Some planning metrics already exist in build_comparison_row(). This issue should document the expected final output before improving the report behavior.

References

• sim/planning/comparison.py
• sim/planning/sweep.py
• sim/planning/report.py
• sim/config.py

[Arti-Dev]

some notes for this:

i will not be making a google doc for this. i also don't have access to the drive atm

definitions

finish soc: state of charge at the end of a simulated run
minimum soc: isn't this a parameter, not an output? minimum soc that is acceptable when car is racing
target soc: this is also a parameter. target soc at the end of the race. should optimally be close to or equal to minimum soc
laps completed, distance completed, average speed: all self-explanatory
Whether the full race window was completed - if minimum soc is hit before end of race this is false
Whether minimum SOC was reached - (at the end of the race)
soc energy margin (soc error?) - error between actual and ideal soc at ANY point in the race.
an ideal soc curve is computed at the beginning of the race.

things missing:

distance completed is missing, but laps is probably enough
soc error isn't output at all in any capacity, nor do we have a way to really quantify it. i'm also struggling to understand the purpose of it
everything else is laid out in a decent table after it runs

[ethancoon]

i will not be making a google doc for this. i also don't have access to the drive atm

You should now have access to the shared drive, if you don't lmk. I was gonna suggest adding it to the README but I actually think it's probably fine left as a comment if that's good with you. Just as long as people understand for the future tickets these metrics.

distance completed is missing, but laps is probably enough soc error isn't output at all in any capacity, nor do we have a way to really quantify it. i'm also struggling to understand the purpose of it everything else is laid out in a decent table after it runs

I think I explained SOC error but if I didn't: Energy margin is finish_soc - target_soc, SoC tracking error is actual_soc(t) - desired_soc(t)