649 karma · joined August 28, 2020
Moreover, it’s very plausible (and expected) to use multiple clusters and GPU types for RL rollouts which could very well not be included in this count.
No part of this pipeline is fixed in stone.
Now this might not be the most cost effective (and may require a bit extra power), but you only need a datacenter for training or cost optimization.
In fact, OpenAI was founded largely with the direct goal of preventing Google from being the sole winner in AI...
More use cases for a single popular format makes this more likely.
I don’t see why the industry couldn’t move to providing this documentation/full source over a few years.
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.
See the Cuban missile crisis. It is an act of war but certainly not as escalatory as direct attack.
IK to my knowledge is well known in every setting I am aware of.
To me it’s sorta like CSS where the availability of templates is more important than the core language (at least for people lacking design abilities).
That being said, UV is great.
Things like pypi sources per dep are there finally.
I still find rough points (as many others pointed out, especially with non sandboxed installs), that are problematic, but on the whole it’s better than Mamba for my use.
I regularly use large clusters and even there docker/singularity are very helpful at times (very simple example, glibc requirements).
When you are talking about well-written code that only requires posix (and nothing beyond) and does not interface with hardware, etc. etc. then virtualization seems crazy.
> At least as long as you're running your own code on your own hardware
Assuming you keep a consistent env/OS across all nodes you will want to run said code. Which can be difficult, even just between two users on a single node.
Not to mention the fact that a lot of (most?) code needs to (A) interoperate with other people's code and (B) at least sometimes run on other hardware.
Also to be able to find photos in specific locations (if you integrate it with geotagged photos like google does).
It’s one of those things I don’t actively care a ton about in the short term but is useful data to have in the long term if it can persist without a lot of effort.
Edit: I think form is “irrelevant” as long as it’s well supported and can be useable in different services later on. Same thing with notes imo (and why I use markdown). Has enough features but importantly is and will be well supported.