It kicked me out of Fable 5 and switched to Opus 4.8 for this prompt:
"csetibius water clock why two stage gear system why not just one stage"
which has nothing to do with cyber security or biology/chemistry
HN user
It kicked me out of Fable 5 and switched to Opus 4.8 for this prompt:
"csetibius water clock why two stage gear system why not just one stage"
which has nothing to do with cyber security or biology/chemistry
I don't know. How could I check that?
Thanks, didn't know that she had a contact form. I just did.
Are Robert Linn and Linn Smart Computing related?
Can't find any link between them. Maybe they are eponyms?
Not sure if I follow here. Whenever I used PWAs, it was just another tab in my browser.
How do PWAs preclude using tabs?
The Kalman filter code does need floats, though. So here we did indeed need a conversion.
The prediction quantities were indeed zero, as they get discretized by multiplying with the sampling time. You're right that some discretized part of the update quantities were also zero, resulting in an identity 'A' matrix. I'll correct it, thanks!
Granted it was 2013, don't sweat yourself.
Don't worry, I don't. Funnily, recently something very similar happened.
At work, there was this C++ class that had a 'void reset()' member function. Of course, at some point it was used with std::unique_ptr and we got some SIGSEGV. Took me a while to figure out that the '.reset()' was called instead of the '->reset()'.
I think these 'omg that's so dumb' bugs are just part of programming.
Out of curiosity: were you taught how to program properly in university? I'm grappling with the question if colleges should, or if it should be left to 'the school of life'.
I'm grateful for the more theoretical courses that I attended instead.
Right, sorry! Corrected now.
Never worked with Swift before, but this checks out: https://swiftfiddle.com/mt5uptmbynbt7bi4jot7m5laum
Careful though, if you don't have :Float on ts it still gives 0.
Totally. Luckily, these #defines are often easy to grep for.
Author here, totally agree with you. Changing the preprocessor directive was just the way I fixed it way back when.
Of course, the real fix is to use a proper constant.
Thanks for your comment.
The blog post was written with C++ in mind, but I just learned that C now also has constexpr: https://en.cppreference.com/w/c/language/constexpr.
Time to update those books (: