284 karma · joined November 26, 2013
Often some tweaks from the standard formula are necessary to account for real-world non-linearities, and some creative design work is required to define states in such a way that the Gaussian noise assumption can hold well enough.
https://www.e-hike.net/tr/content/wrightspeed-unveils-new-turbine-range-extender-medium-and-heavy-duty-electric-powertrains-30
With a range-extender hybrid system, you can keep the turbine closer to its peak-efficiency operating point, since it only has to handle steady-state load while the battery takes up the spikes. Not sure how it would do up a long grade, but I imagine they designed for that.Edit: sorry, my comment may have sounded snarky, which was not my intention. World-wide vaccinations do carry a risk. It’s just that such a risk clearly pales in comparison to the very known downsides of the current situation. I am in no way a vaccine expert and cannot comment intelligently on why long-term risks are considered to be low.
I would love to see slow-motion breakdowns, but that might only be interesting to fans who play seriously. Then again, maybe that’s most fans since it is a more obscure sport?
I’m just glad they finally figured out that dark blue courts and a white ball is the only combination that gives people a hope of seeing the ball on TV. High def viewing helps too, of course, but the old color schemes used before 8-10 years ago made it impossible to see the ball.
I blocked CNN from my phone because checking it repeatedly all day gave me high blood pressure.
Unit testing was traditionally considered impractical for embedded systems, because the code is so closely tied to the hardware. However, with proper architecture and unit test frameworks that simplify your life, it's quite feasible, and indeed enjoyable.
You write unit tests that exercise your embedded code, compiled for the PC, not the target. This ensures your code is portable.
I use the Unity/CMock/Ceedling framework when I'm writing in C, and CppUTest when I'm writing in C++.
I HIGHLY recommend the video courses taught by the guys at ThrowTheSwitch.org (the authors of Unity/CMock/Ceedling). See https://www.throwtheswitch.org/dr-surlys-school
I read and enjoyed James Grenning's book, Test Driven Development for Embedded C, but it didn't really click for me until I took the video courses mentioned above. In the second course, you code an entire simple but realistic embedded project in TDD fashion.
Location: Orange County, CA
Remote: Yes
Relocate: No
Technologies: C, C++, Python, RTOS, Bare-metal, ISO 26262, IEC 62304, understanding and interfacing with all kinds of hardware and electronics
Résumé/CV: https://www.linkedin.com/in/jeff-gable/
Email: jeff@jeffgable.com
However, it suffers from a problem common to these types of sites — namely, there is no obvious organization of the content. Say that I’m a new user who is interested in Linux. Where do I start? The index, the commands, the how-tos... they are all alphabetical. Just like man pages! It’s great that documentation is comprehensive, but that doesn’t make it usable.
Knowledge doesn’t always fit neatly into a hierarchical tree. Sometimes it makes more sense to represent it as a graph. But an alphabetical list only makes sense for people who already know what they are looking for.
Not trying to crap on this project, really, I’m not. But, if your goal is to educate people about the advantages of Linux, you’ve got to give them a foothold and a map of the terrain.
Speaking of EtaGen (your third link), two of the founders, Shannon Miller and Matt Svrcek, are from Chris Edwards's group at Stanford. I worked with Matt quite a bit during undergrad. I knew Shannon but didn't work with her much directly. They are doing some very cool stuff. Their generator been in development a long time -- I hope it can go to production soon.