I don’t see why the industry couldn’t move to providing this documentation/full source over a few years.
I notice too that it employs a different style of code where it often puts assignment on a different line, which looks like it's trying to maintain an ~80 character line limit, but does so in places where the entire line of code is only about 40 characters.
https://developer.apple.com/documentation/security/code-sign...
https://developer.apple.com/documentation/security/notarizin...
There are dedicated sections of the developer web forums:
https://developer.apple.com/forums/topics/code-signing-topic
https://developer.apple.com/forums/topics/code-signing-topic...
...and there's an apple developer support person, Quinn, who appears to be heavily if not solely dedicated to helping developers do binary signing/notarization/stapling correctly.
They have written a slew of Tech Notes about signing and notarization. Main TN is at https://developer.apple.com/documentation/technotes/tn3125-i...
Quinn also has their email address in their sig so people can just reach out via email without even needing an Apple account, or if they prefer more confidentiality.
I mean, come on.
Genuinely perplexing how they always try to show each multi-million earning engineer as some normal person and not someone that went to Exeter and Harvard
No, a state-based RL research like this is essentially an IK problem. Given a goal position in the world frame, you need to find out the motor configuration to move your EEF to that goal position.
> IK to my knowledge is well known in every setting I am aware of.
Really? When I was working in this field, I've actually never seen anyone who used numerical/analytical IK methods on real robots.
Granted that I was not a Robotics engineer (I was a Deep Learning engineer in the team), but my impression at the time was that no practical IK solution was available for a robot with 8 DOF, let alone a 20 DOF robot like Shadow Hand.
If you provide the 6DoF trajectory (+ gripper joints), a lot of robotics (manipulation in particular) is basically solved. The problem is, we don’t have these good trajectories.
Sure, joint space is commonly used for learned policies, but cartesian space isn’t uncommon either.
IK is really just not a major focus on the learning side of robotics because it’s not the problem. The problem is we don’t know what to do even at the slightly higher level.
More use cases for a single popular format makes this more likely.