I understand that part. But not the one about the cruise car almost hitting you.
So: one lane street, person in front of you turning left, you pass them to the right in the space where there might be street parking which extends into the intersection. During that time, the car trying to turn left is finally able to do so and the car immediately behind it is the cruise car. Cruise-car is now able to go straight and almost hits you as you're both competing for that one lane?
Not entirely related, but the pain of the "paper cycle" as a "customer" of health-care is real.
It seems as if to avoid dealing with hipaa regulation it's all paper, fax machine, and come pick up your x-rays burnt on a cd during your work hours (cd that you have to buy).
Having not grown in the states, this type of practices seems very primitive to me. Amongst many other aspects of the American healthcare, but that's another debate.
Yes, precisely. exp() is the mapping from so(3) to SO(3), so you can use log to go the other way around.
Here is the relationship with the other representations [1]
Where it becomes interesting for our rigid-body transform application (or recovery of it, in the case of computer vision), is with Twist coordinates (6 element vector) which will map to a 4x4 Transform, again using the matrix exp() operator [2].
Quaternions are a useful tool for manipulating rotations in a lot of common applications. But that wasn't my point here. Also quaternions are hard to grasp by humans. I find axis-angle much more palatable in general.
Imaginary numbers can be represented with a 2x2 skew symmetric matrix with no stretch of the imagination at all. And 3x3 skew symmetric matrixes represent rotations most compactly with only 3 actual variables. Instead of 4 for quaternions, 9 for "classic rotation matrixes", or the need to tell which is the order of the angles if you're given 3 euler angles.
There are interesting applications of Lie Algebra on SO(3) [1], notably in computer vision where a global energy is minimized across two successive rgb-d "shots" in order to recover the infinitesimal rotation [2].
It's going to be easier to minimize energy on something that is most compactly defined, and always amounts to a valid rotation.
It's also fun to introduce e as a matrix operator for 3d rotations.
It's useful for kinematics and having compact representations for axis angle notations. It's a little far in my head but at some point it felt like a ha-ha moment with the Euler identity, in the "2d version".
I thought that too. Just finished a kaggle competition involving segmentation, like a lot of participant I used one form of U-net (my own implementation).
You can probably find a lot of u-net implementations from this contest.
One that performed really well [1]. It uses 'inception style' blocks feature extraction instead of vgg. But otherwise pretty similar.
I bought and assembled an ergodox some time ago. I found the key layout to be too esoteric for me to adapt my workflows to. The thumb cluster while a good thought is not as well positioned as on an Kinesis advantage to be extremely useful. I never ended finding a layout I liked.
It's been sitting in my parts drawer for a while, I'm not sure how to part ways with specialty items like that.
The kinesis freestyle + vip accessory was my daily driver for years but it's a bit mushy and the build quality is questionable (I went through 3 boards, including one DoA). My new one is the Matias Ergo pro. Quite similar, but better in almost every way, except price.
This is my daily driver and I really love it! It's mechanical, split and the layout is really not esoteric. The major upside from the UHK would be total firmware configurability, not an option on the Matias Ergo pro.
I would have to remap 'Mouse' though as this is the place for my 'Ctrl' key (I use Emacs a lot).