So it's software to write firmware, not software to design hardware. Not sure how ambiguous that was to others but I got the wrong impression from the title.
Are the 50 for loops truly necessary in the manual C code example of a Kalman filter? At least introduce a few functions (that could be inlined and loop-fused) for some matrix operations?
This is my project/blog post and yes, I've gotten that feedback a couple of times. I mostly work in control systems and probably reflexively think narrowly about that context. But it's definitely tailored to controls - I wasn't intentionally trying to oversell it or anything.
It’s the title of the blog post and I didn’t want to change it. But yes, it seems to focus on the specific subset of hardware engineering that’s control systems.
I just revised Matlab to do some work involving a simulation and Kalman filter, and after years of using python I found the experience so annoying that I really welcome this library.
(Side note: While running Python itself on a microcontroller is growing in popularity for educational and hobby applications, there’s no real future for pure Python in real-time mission-critical deployments.)
Bridging the two could be a real win for people using hardware like the M5Stack ecosystem, which has a wealth of peripherals and a robust Python stack.
Given the name I was hoping this would be something specific to Arm hardware.
Oh well I guess the Archimedes wasn’t that we’ll known.
So it's software to write firmware, not software to design hardware. Not sure how ambiguous that was to others but I got the wrong impression from the title.
I was under that impression too, like an alternative to PYNQ https://github.com/Xilinx/PYNQ
Are the 50 for loops truly necessary in the manual C code example of a Kalman filter? At least introduce a few functions (that could be inlined and loop-fused) for some matrix operations?
Its specifically meant for control systems no?
hardware engineering is a very broad field and the title is misleading
This is my project/blog post and yes, I've gotten that feedback a couple of times. I mostly work in control systems and probably reflexively think narrowly about that context. But it's definitely tailored to controls - I wasn't intentionally trying to oversell it or anything.
It’s the title of the blog post and I didn’t want to change it. But yes, it seems to focus on the specific subset of hardware engineering that’s control systems.
It's C codegen using casadi under the hood. Most embedded systems can compile some form of C.
What's the relationship between this and Model Based Systems Engineering, if any?
What are the similitudes?
Good luck displacing MATLAB, it's great there's an OSS alternative here.
Well, they need to a vibe code a drag-and-drop Nocode UI first if they want to compete with Simulink.
https://www.mathworks.com/products/simulink.html
(There's also Julia and Modelica)
https://discourse.julialang.org/t/simulink-alternative-in-ju...
https://modelica.org/
Pathsim is a block diagram-based simulator written in Python and seems to be getting very regular commits https://github.com/pathsim/pathsim
I just revised Matlab to do some work involving a simulation and Kalman filter, and after years of using python I found the experience so annoying that I really welcome this library.
(Side note: While running Python itself on a microcontroller is growing in popularity for educational and hobby applications, there’s no real future for pure Python in real-time mission-critical deployments.)
Bridging the two could be a real win for people using hardware like the M5Stack ecosystem, which has a wealth of peripherals and a robust Python stack.