* card: create pedal pressed event (#32393)
* move pedalPressed to card
* rm
* needs to be a builder
* move these
* clean up
* reader later
* Update ref_commit
* moved to card
* Adding demo version for acceleration only
* Adding, plot any event
* Adding dynamic blueprint creation and menu to choose what to plot
* Adding, pool of processes for faster data visualization
* Adding, install rerun if not present
* Adding. thumbnail support
* Refactoring, minor cleanup
* -Use rerun pre-release
-Remove json as a middle format
-Replace recursion with stack-based approach
* Refactoring, using services from cereal instead of hardcoding them
* Use of lr.run_across_segments instead of pool,
Use of python dict instead of capnp objs - better performance
Use LogReader syntax
* Enable logging of liveTracks, pandaStates
* Use of plotjuggler user experience
* Fixing bug in log_msg function
* cleanup
---------
Co-authored-by: savojovic <jovo.savic00@gmail.com>
Co-authored-by: savojovic <74861870+savojovic@users.noreply.github.com>
* move stateless, common car events to car interface
* try to reduce process replay diff a bit
* Revert "try to reduce process replay diff a bit"
This reverts commit b12798deabea67c5a636d6e70e80a3c21c7225ff.
* update refs
* VW: Steer to zero, for large values of zero
* ah, the joy of floating point
* comment, style
* actually fix floating point issue
* follow PlatformConfig refactor
* this check is not useful after PlatformConfig
* don't really need that
* work around docs assert
* little better
* one comment
* update refs
---------
Co-authored-by: Shane Smiskol <shane@smiskol.com>
* Ford: use platform codes to fuzzy fingerprint
TODO: write scripts/tests (print platform codes and version ranges etc.)
May close#31052
* get_platform_codes: fix return type
* add print_platform_codes.py script
* print_platform_codes: sort versions
* match_fw_to_car_fuzzy: use set comprehension, and fix typo
* Ford: add missing Mach-E fw
From the route 83a4e056c7072678/2023-11-13--16-51-33 (which is already
in selfdrive/car/tests/routes.py, added in #30691).
* add ford_fuzzy_fingerprint.ipynb notebook
* get_platform_codes: use regex to parse firmware
* test_ford: test_platform_codes_fuzzy_fw
* test_ford: use get_platform_codes in test_fw_versions
* match_fw_to_car_fuzzy: improve comments
* test_ford: add test_platform_codes_spot_check
* test_ford: add test_match_fw_fuzzy
* remove comment from notebook
* TestFordFW: remove engine ECU FW
* update print_platform_codes.py
* remove part number (unecessary)
* platform codes can just use platform hint and model year - software revision not useful
* fuzzy FP on the platform hint and model year hint range
* fix platform codes test
* update notebook
* add notebook
* explain model year hint better
* test part numbers again
* cleanup notebooks
* remove notebook
* cleanup match_fw_to_car_fuzzy and add comments
* update comment
* .
* Revert "remove notebook"
This reverts commit 5d4ca202f2a23601d5c829204119f36a58f2b451.
* add notebook back
* remove PSCM from PLATFORM_CODE_ECUS
ABS and IPMA are the best for uniquely matching, and the radar is always required
* Revert "remove PSCM from PLATFORM_CODE_ECUS"
This reverts commit b7baeac19c18b5aa0c31da52f12054f4bae6e1ff.
* fix from merge
* more fixes
revert
* FW_RE -> FW_PATTERN
* this can actually be set
* conventions
* just add
* convention
* refactor matcher, this brings it more in line with Hyundai. IMPORTANT NOTE:
NOTE THAT WE remove the separation for the different platform code model year hint ranges, I don't see that being a problem
* better/smaller test
* add test to catch overlapping platform codes
* remove nb
* not now
---------
Co-authored-by: Shane Smiskol <shane@smiskol.com>
