openpilot VS RESTinio

Now in that video above you can see there is some "ping ponging" where the car seems to constantly move back and forth not sticking to the center of the lane well. This is mostly mitigated by a fork of the Openpilot software. Twilsonco's fork of sunnypilot uses a neural network to calculate the "torque feed forward" settings. It's quite ingenious. You can get very in depth with the C3.

https://github.com/twilsonco/openpilot https://discord.gg/jPS879WZ

Improvements to the lateral controls code so it uses the torque it has properly. This is in my Sunny-torque-plus branch that adds lateral jerk error response and uses a lower error response in curves to let feedforward do the work. Some other cars have also had big improvements from this. installer.comma.ai/twilsonco/sunny-torque-plus

what's the difference if I use https://github.com/twilsonco/openpilot/tree/sunny-test-c3 vs. https://github.com/sunnyhaibin/sunnypilot/tree/test-c3

yes I use it in a '18 Chevy Volt running my own fork with tons or original features. Here's some driving footage of my car.

And '17 is the most supported by OpenPilot. It has auto resume for stop and go traffic. '18 doesn't auto resume. Other than that they're the same. My OpenPilot fork makes it magic.

If you're in a Volt, check out my fork! https://github.com/twilsonco/openpilot

In my past job, we used https://github.com/Stiffstream/restinio and absolutely loved it. It's not as active but it honestly didn't need much.

Here's a C++ REST framework for you to use too: https://github.com/Stiffstream/restinio

I had a good experience using restinio for a small ASIO HTTP server recently.

It uses restinio https://github.com/Stiffstream/restinio with great success ;)

For networking, pick a networking library. Restinio is a fair choice for HTTP. But, again, feel free to pick others.

You may find this worthwhile: https://github.com/Stiffstream/restinio/issues/101 FWIW, I used Restbed successfully for 3.5 years before switching personal projects to Restino. I've left the job that used Restbed, but I think they are still using it.

Contrary to the direction most people go, I've been writing REST APIs as C++ servers using two different fairly full featured C++ REST frameworks: first using https://github.com/Corvusoft/restbed and more lately using https://github.com/Stiffstream/restinio. These can be peers with any other server, while living on embedded and/or high compute devices for video encode/decode/analysis, deployed ML models, encryption for and remote process communications, model data collection and similar expensive or in-field processing. In both high compute and in-field-no-internet situations creating REST APIs in C++ enables speed and system controls not present in the majority of the mainstream REST frameworks. It's a big world, and here comes ubiquitous high compute...

If you need an embedded C++ HTTP server then there are plenty of libraries/frameworks (in random order): Crow, RESTinio, Boost.Beast, cpp-httplib, http_backend, Pistache, RestBed, served, proxygen, Simple-Web-Server, drogon, oat++.