* single longitudinal toggle for e2e and disable radar
* write disable radar param
* rename
* better param name
* clean that up
* update refs
* update translations
* not live for experimental
* write it out
* vanish
* Add params for lead and danger
* fix long params
* E2e passes simple maneuver tests
* Make tests run with e2e long mode
* Slightly more error allowed in e2e mode
* FCW back and populate long source field
* Fix planner name
* FCW still doesnt work
* Slightly less aggressive
* Doesn't need to simulate from stop
* refactor
* Add planer modes to support offline, acc, and blended
* add acceleration
* Fix index
* Update model ref
* Read in model outputs
* Add model msg
* Add e2e logic
* Add source
* see if this works at all
* can revert this
* think adding a no entry conditionally is nicer
* then we can revert this
* 0 makes more sense
* Revert "0 makes more sense"
This reverts commit efc89e8a23.
* gm CC uses > 70
* bump cereal
* comment
* test on Honda
* whoops
* works
* add exception with todo
* moved button enable events to controlsd
* get rid of that
get rid of that
* different values for now
* car interfaces add enable event, controlsd can block it
* Regen and update refs
* delete if not set
* One place
one place
* regen routes are uninitialized first few frames
* Trim start of segment so it's like original segment
* stash
* regen
* not working
* clean up
* more cleanup
* revert
* bump ceral
* actually check resume button
* whoops
* pcmCruise cars don't use setSpeed, so we're good
* engage correctly in sim
* Update ref_commit
* Update refs
* push
* do process replay
* commit
* update refs
* clean up
* clean up controlsd
* clean up controlsd
* Add assert
* debubuggier param name
* can be peristent
* Revert "can be peristent"
This reverts commit 6e6d3f6423.
* Update selfdrive/test/process_replay/process_replay.py
* Don't set lane change events if we're not able to steer.
* more specific variable name
* update process replay socket config
Co-authored-by: Adeeb Shihadeh <adeebshihadeh@gmail.com>
* sensor flag in paramsd
* increase lateral acc err alert threshold
* add invalid sensor alert from paramsd
* update ref, bool before adding to msg
* account for sign difference in locationd and paramsd
* revert ref
* always log leads, we hide them in ui
* only spam resume when future is > vEgoStarting
* do rest but vw
* vw
* remove comments
* rename to resume
* maintain original button msg rate
* mazda: ensure no resume if cancelling
* same for non-HDA2
* Always run planner if not opLong
* try 0.2
* 0.1 should be pretty safe
* add test for resuming
* fix test
* stricter test, speeds[-1] is 0.14 when starting here
* no walrus
* fixup mazda cc
* remove extra import
* get_fw_versions returns all fw versions with request's brand
* keep track of everything received
* debug
* need to regen or write a hack in build_fw_dict
* to be safe, still replace old responses within same brands (hyundai responds to two queries, can fix later)
to be safe, still replace old responses within same brands (hyundai responds to two queries, can fix later)
* update test_fw_query_on_routes
* clean up
* better name
* slightly cleaner
* fix test_startup unit test
del
* fix imports
* fix test_fw_fingerprint
fix test_fw_fingerprint
fix
* fingerprint on all FW_VERSIONS, not just brands with requests
* support old routes in test_fw_query_on_routes
* regen and update refs
* similar function style to before
* better comment
* space
switch name
* try to exact match first
* useless else
* fix debug script
* simpler dictionary
* bump cereal to master
* update names + notes for MPC outputs
"current_curvature" is not the correct description of what the MPC is outputting in it's curvature_ego state.
The MPC is integrating it's free variable, curvature_rate, such that curvature[0] is actually the desired_curvature before any delay.
inversely: the curvature_rate_desired is the desired rate of change to the setpoint and not the actual curvature rate.
If we were to set the initial curvature = measured curvature in the MPC initiation these names would be correct.
This was possibly how it was initially set up but the nomenclature here is now confusing.
* more notes
* match
* Clarify #1
* Set good torque using torque controller tuning
* should be equal to
* save lateral accel to car params
* use maxLateralAccel
* always
* same convention
* nan will always evaluate to false
* The great good torque purge
* adjust default friction
* Add data for more cars
* adjust name
* Welcome back, guys. Only adjust good torque if maxLatAccel is set
* Update refs (1.7 is 1.7000001...)
Adeeb Shihadeh
Shane Smiskol
Cameron Clough
HaraldSchafer
Chris Souers
Robbe Derks
Vivek Aithal
Willem Melching
grekiki
ClockeNessMnstr