159 karma · joined July 5, 2023
1.) How you compensate for anode consumption/geometry changes over the lifetime of the anode. For instance, does the center get worn away or do you try to uniformly use each "pixel".
2.) More details on anode "pixel" geometry and minimum feature size.
3.) Can you talk about the development process? Did you have in situ measurement, or post build analysis of the part and anode.
4.) Typical surface finish?
https://patents.google.com/patent/US10724146B1/en
Edit: I wonder what compensation for anode consumption looks like. Model based? I assume in-situ measurement/process control is hard.
As the poster below mentions, neighboring actuator coupling/disturbance rejection is very much a performance consideration (even between neighboring HDDs) and then to package all that additional complexity into the same form factor is really something.
It'll be interesting to see if this sticks around, or the added complexity makes it short lived.
The company didn't go anywhere because it turns out that business is hard when you don't like to self promote, but I am incredibly proud of the end result. It has high bandwidth, <100nm RMS jitter, a nice network interface, and incorporates reinforcement learning-based controller tuning
Check it out here if you'd like: https://www.rockymountainservo.com
Recently, a friend and I were joking about ways to ignore unpleasant voices at a family BBQ. A quick look at current speech detection methods led down a rabbit-hole (of course), and resulted in this fun proof of concept.
I was surprised at how well speaker embedding performed (and also acknowledge the sparse, subjective nature of my results).
It was a fun weekend project, and I hope you enjoy the write up!