Kalman VS coz

Since you mentioned C++ and Kalman filters, I author this Kalman filter library which helped me to get reacquainted to control theory, tries to be approachable, and lists a variety of sources to ease in the topic with examples.

Yes, and here's one for sanitizers. Other tools, documentation, and coverage in the neigbhorong files.

I've been learning FectContent as well with some successes and failures.

My goal with this Kalman filter for C++ is to solve your exact question.

I released a first version of a generic Kalman filter.

I use fmt and others in my project with CMake fetch and it's been a good experience so far: fetch, declare, link in a few lines. Hope this can be useful to someome.

Gratuitous French codebase self-promotion though. /s

Would you be open to exploring an implementation collaboration? I author a C++ Kalman library and would like to expand demonstrators.

A façade (example) included only for your GCC builds and with the fmt library would allow you to generically use the std::format support in your code. Avoiding the fmt:: and dependencies with MSVC. When the support lands in GCC, only that file would need to be deleted.

I use it with boilerplate similar to this: https://github.com/FrancoisCarouge/Kalman/blob/develop/benchmark/benchmark.cpp and run the executables with priority and pining: nice -n 20 tasker -- cpu-list 0

But let's take the guesswork out of profilers. Use Coz. It's a causal profiler that performs experiments to determine what code would see the greatest performance improvement of the whole program if made faster. There's a video in the link; I think the best demonstration they had was a program that saw the greatest improvement by optimizing a function that ranked #30 by a sampling profiler.

Coz. It's in a Debian package so you don't have to build it. Watch the video embedded in the page I linked; I;m all about profiling, but the devil is if you're not a statistician, you don't know how to read profiler results.

I think https://github.com/plasma-umass/coz solves most problems related to noise in benchmarks.

Perhaps you're thinking of the coz profiler (https://github.com/plasma-umass/coz)?

I was thinking of doing some kernel profiling, and stumbled upon this interesting repo: https://github.com/plasma-umass/coz

I'm pretty intrigued by the concept, and was wondering if anyone here tried out Coz.

https://github.com/plasma-umass/coz https://youtu.be/7g1Acy5eGbE

Could it be an issue of binary layout? Have a look at the coz profiler which has a rust port.