Adaption Labs: Gradient-Free Continual Learning — Sara Hooker, Adaption

AI Engineer · 20 min · 261 sentences · from YouTube's caption track

Each timecode opens YouTube at the start of that sentence. Line anchors (#s42) are the cue ids in the WebVTT, and every line carries its start and end seconds. All transcripts has every talk, and the whole corpus as one file.

  1. 00:01[music]
  2. 00:12Amazing.
  3. 00:13Um it is Oh, sorry.
  4. 00:14Pardon me.
  5. 00:17Um it is so lovely to be here.
  6. 00:19So, I wanted to share today uh some thoughts that I have around who gets to be at the frontier of discovery.
  7. 00:27So, modern computer science as a field has only existed for the last 77 years.
  8. 00:32It's kind of bizarre when you think about it.
  9. 00:34So, World War II, uh all the transistor technology that was developed for radio, we finally had our first versions of the computer.
  10. 00:42But, when you think about it, that's only two generations of people working on these tools.
  11. 00:46However, within that time, even for computer science, who and what and what topics we work on has dramatically changed.
  12. 00:56And I think it's an interesting setting because actually, if you look back across science as a whole, how we do discovery has been markedly different uh at different points in time.
  13. 01:06So, when we started, the whole idea of a researcher was what we call like a gentleman scientist, typically someone with adequate wealth to dabble in a discovery.
  14. 01:18And these were all individuals, independent researchers.
  15. 01:21Uh when we uh see like the first associations emerge with the Royal Society in the 1600s, the idea of being a scientist as a full-time job was very special.
  16. 01:32And these became the predominant spaces for discovery.
  17. 01:35Why am I talking about this?
  18. 01:37Because to be honest, like the professionalization of science uh led to what I would call, and you know, my good friend Rosanne Liu calls, the unreasonably narrow path.
  19. 01:48So, I'm an AI researcher.
  20. 01:50Uh this is Yans' actual career.
  21. 01:53Uh and it's interesting, if you were to be an AI researcher at the forefront, you basically had to follow this exact narrow path.
  22. 01:59You had to get into the right PhD program.
  23. 02:01You had to then go to the right industry lab.
  24. 02:03You had to do sufficiently interesting work, and then finally you got to contribute to the frontier.
  25. 02:08This was my story, too.
  26. 02:10So, a lot of my work has been on efficiency at scale.
  27. 02:13Uh I did my PhD and worked at DeepMind and a lot of different frontier labs, but this was in many ways um a very aggressively filtered system.
  28. 02:25If you did not make it or you were not curious about the right problem at the right time, you didn't have um a place to play at a frontier lab.
  29. 02:32And this is like the standard successful scientist.
  30. 02:36Like you have a famous advisor, hopefully.
  31. 02:39Uh you hopefully get one or two important internships.
  32. 02:42And what's interesting about this is computer science was really about representing the world, and it was like all the tools that do that.
  33. 02:49But the reason why most people got into computer science is the question at the end of it.
  34. 02:53Like if you can represent the world, what questions can you answer?
  35. 02:56So, today I'm going to talk about what I think is like one of the most profound and interesting topics, which is like why this is so important when computer science at this is changing.
  36. 03:06So, I'll also speak to this.
  37. 03:08It was double compounded in computer science because of the need for compute.
  38. 03:12So, this resulted in jokes.
  39. 03:14Um it's fun that Merve was here.
  40. 03:16This is her tweet about GPU poor versus GPU rich.
  41. 03:20Uh it led to barriers of entry on who can contribute frontier AI.
  42. 03:23So, I put here company A, company B, company C. But to be honest, if we pulled, I think there would be significant majority votes about who those companies are.
  43. 03:33But basically a handful of frontier labs have been able to build the technology we use.
  44. 03:38Um it's also determined who gets to participate in breakthroughs and who doesn't.
  45. 03:41So, uh this is a map of like what Stanford calls uh where statistically or significant breakthroughs have come through come from, and you can see the whole sections of the world are completely left out.
  46. 03:54And so for me, uh this is a very important question worth answering.
  47. 03:59Who gets to shape the frontier?
  48. 04:00Who gets to answer the questions at the end of the pursuit?
  49. 04:03We've seen that the shift has dramatically changed from academia to industry.
  50. 04:08And it's also meant that we ship the same model to everyone.
  51. 04:11Uh why that's particularly interesting is that most people intuitively understand that you shouldn't ship the same model to billions of people.
  52. 04:18And they also understand that it's not a particularly good use of compute, right?
  53. 04:22You're spending the same amount of compute on everything.
  54. 04:25And some problems are hard and some are very easy.
  55. 04:28So where does that leave us?
  56. 04:29What's my talk for today?
  57. 04:31Um I would like to say that we are ripe for a revolution.
  58. 04:34And we are ripe for a revolution in who gets to participate at the frontier of AI.
  59. 04:39Uh I'll tell you two reasons why I'm bullish on this.
  60. 04:42Um I'll definitely cover one, and then I'll actually see interest and timing cuz I want to leave plenty of time for questions.
  61. 04:48I think that's you know, unless you have a few questions and a bit of banter, these things can be kind of boring.
  62. 04:54So we'll see, but I'll cover one definitely that I'm actively thinking about.
  63. 04:58And this is what if we could allow anyone to build the same frontier intelligence um as that in labs.
  64. 05:05And I've been in a few labs.
  65. 05:06I've done my tour of duty.
  66. 05:07And this is the core question I care about now is like how do you build intelligence that continuously adapts and that builders everywhere can have more control.
  67. 05:15So instead of taking years of training to learn how to build the tools, scientists just skipped the questions.
  68. 05:21So a few weeks ago we released Auto Scientist.
  69. 05:24And Auto Scientist is really about how do you automate the training of models itself.
  70. 05:28Um I'll share a few things that are really interesting about this is that one it's um co-optimizes the entire loop.
  71. 05:34So it's like from data to alignment uh and it it chooses and self-evolves based upon the domain and the type of data.
  72. 05:44Um what's interesting as well is that it actually outperforms research staff.
  73. 05:48And mainly because like a lot of our research staff has experience with certain model types, and we're testing it across many different model architectures, different different size models, um as well as like dense and mixture of experts.
  74. 05:59And that search space is a lot broader.
  75. 06:01And so, exploiting it using like how do you how do you self-improve from experience and scale is very effective.
  76. 06:08Um I think this is very interesting.
  77. 06:10This only worked when we co-optimized the data.
  78. 06:13Uh so, there's a lot of auto research projects right now, which basically treat data as like um the agent is it decides whether to create data or not or what to do.
  79. 06:23Frankly, we did not get the returns for like how much you can squeeze out of performance until you control for data quality.
  80. 06:30So, we actually co-optimized based on all the adaptation we did with the data exactly what we would do with the model.
  81. 06:35And that was super interesting.
  82. 06:37It speaks to like the need to control the entire flow.
  83. 06:40Um What's fun about this is like really what auto scientists do and it's a combines all the knowledge it gained from the adaptive data component with also the knowledge of the domain and also the ability to self-improve for a domain and to learn from other components of that domain.
  84. 06:54Um What What is a cheeky fact and this is quite fun.
  85. 06:57You'll notice all these percentages for win rates are like 60 plus.
  86. 07:01Um that's because we put the budget stopping it stopping it above 60.
  87. 07:05So, like once it was above 60, the our our genetic flow could exit.
  88. 07:10But we since like removed that barrier and like you can see it just go up over time, which is super fascinating.
  89. 07:16Um and then I think what's interesting is like it changes a lot of the hyperparameters.
  90. 07:20Typically, that humans are much more wary about changing all at once.
  91. 07:24And so, you get massive exploitation of the search space.
  92. 07:27I see this is crucial for like how do you reduce the amount of compute you use for customization because you train with much more predictability.
  93. 07:35But also, how do you um leverage like your domain knowledge to really unlock how you build frontier AI.
  94. 07:42Um and this was fun.
  95. 07:43We we did uh we announced a beta like 4 weeks ago.
  96. 07:47The excitement is most acute for like medical and sciences.
  97. 07:50And that's largely I think and legal and and code as well.
  98. 07:53But these are like domains where typically current models fall short.
  99. 07:58And also domains where um in many ways like the degree of last mile customization is really acute.
  100. 08:04Um and this is the core point.
  101. 08:07I you know, I think this is fun.
  102. 08:08I think I might even have time to cover The other point I wanted to make about why now is very important for like changing who shapes.
  103. 08:15But this really the main factor that this does is it increases your innovation cycle.
  104. 08:21Like and it also increases the likelihood that when you train and spend compute you'll succeed.
  105. 08:26And those combined factors are super interesting.
  106. 08:28Like one thing that we're doing next is extending that.
  107. 08:31So even your test time compute should be adaptive based on your task.
  108. 08:34Um So this kind of brings me back to where I started.
  109. 08:39And like kind of the grumpy statement I said, which is like you know, we have this rarefied super narrow compounding issue of barriers to entry.
  110. 08:47One is like that you need to do this um very narrow funnel of who gets to build frontier AI.
  111. 08:52And the other is that um typically compute and cost really dominate.
  112. 08:57Um we want to change that.
  113. 08:59Like we decided okay, we're going to cover languages from day one, 242 languages.
  114. 09:04And also like a big interest for us is actually non-verifiable tasks.
  115. 09:07I think this is super interesting because um this is really the bulk of like everyday tasks that people do.
  116. 09:14And um it's really where the meat of like what is interesting for progress is going to be over the next year.
  117. 09:21Um and this leads me into our mandate.
  118. 09:23We care deeply about how do you accelerate learning in a way that models should be able to um learn from their environment.
  119. 09:31So right now we've moved from a era of like the the model is monolithic.
  120. 09:36You know, when I was at um different parts of my research career, basically a whole team would be around building a model.
  121. 09:42You give it to someone else to serve, and like you have someone else do the front end.
  122. 09:46And actually now, like the most important intelligence is a model who interacts.
  123. 09:50And so, this idea of how efficiently are you going to interact, how will you continuously learn from the environment, is pretty core.
  124. 09:56And um I think about it a lot.
  125. 09:58So, um let's see.
  126. 10:00I think I do have time, right?
  127. 10:02How are we doing for time?
  128. 10:03Oh, I do.
  129. 10:04I have plenty.
  130. 10:05This is lovely.
  131. 10:05So, we'll have time for questions, and I'll share a little bit about what I think um the next uh component is.
  132. 10:13I think core to this, so if we just did auto scientist, but it still took enormous compute to do frontier AI trainings, I think we'd be in a bit of a pickle, right?
  133. 10:22Like I'd be saying, "Oh great, you can use this agent, but don't worry, just bring your uh 10,000 GPUs with you."
  134. 10:28But, I think there's another trend, which I think makes this very important timing, and rooms like this probably much more optimistic than like have been in a few years ago about who can build frontier AI.
  135. 10:40Um and one of that is like the rules of like where you get rate of return for computer are totally changing.
  136. 10:45So, um I wrote a very paper about this called So Death of Scaling.
  137. 10:51Um but empirically, we do now know that um pre-training size in particular is not your most lucrative axis of scale.
  138. 10:59And what does this mean?
  139. 11:00Like if pre-training scale isn't going to dominate performance, it actually really greatly changes who can create the best recipes for innovation, because pre-training compute typically has to be co-located.
  140. 11:11Um it has to be uh in many ways large volume to accommodate for redundancy.
  141. 11:17Inference compute and other places where you actually apply compute, typically you can have much more like distributed.
  142. 11:23It's also much more higher return given the amount of flops.
  143. 11:27And so, it's interesting when we talk about what is the state of pre-training compute, we know it's not giving the same returns largely because our architecture is saturated.
  144. 11:35So, um we see much smaller models outperforming much larger ones.
  145. 11:39Uh this is like the Open LLM leaderboard, and this is like the daily submission of like the best small model under 13B versus all the larger models.
  146. 11:49Um and you can see over time that ratio totally flips.
  147. 11:53Um and also there's kind of the grumpy assessment that most recent models that have severely um played with just increasing model size haven't provided the same stepwise change um as their predecessors.
  148. 12:08And a lot of that is because where the most returns for performance are now are on a broader action space.
  149. 12:16Um and this is really what I was getting at when we move from an algorithm to we are expanding optimization space in new places.
  150. 12:24And what's the fun about that is that these are new places where um the barriers to entry are much more nimble, and where recipe and algorithm and research matters again.
  151. 12:36Um and things like how do you automate that discovery?
  152. 12:40Um and so this is what I'll state, and I think then we should open up for questions.
  153. 12:45Um and I would encourage good grumpy questions or fun positions.
  154. 12:48Let's make the use of the time.
  155. 12:50I know I was told earlier that almost no talks have time for questions.
  156. 12:53I find that so disappointing, so um so we'll need some brave people to start the conversation.
  157. 12:59Um but I will say this means we're better off, and I would say it's a very good time to be like working on intelligence because instead of just a handful of people getting to
  158. 13:09getting to create it, it's much more now about the question you want to answer at the end of the day.
  159. 13:14The reason why people did a computer science PhD was to learn the tools to get to the question, and now you can just get to the question, which is super meaningful.
  160. 13:23Um okay, let me open up.
  161. 13:25Where should we start?
  162. 13:26We um have an abundance.
  163. 13:28I hear there's no microphone.
  164. 13:29So, if you want to ask a question, you want to make a statement, I will indulge a statement if it's interesting.
  165. 13:36And yeah, go for it.
  166. 13:38Just raise your hand and I'll I'll repeat it afterwards.
  167. 13:40Let me just get to the end of this in case people want to reach me afterwards.
  168. 13:44Nice.
  169. 13:45Yes, go ahead.
  170. 13:46Gentleman in the fourth row.
  171. 13:47Go for it.
  172. 13:49You mentioned uh you know uh AI from here will be more democratized.
  173. 13:55Can you point to like how?
  174. 13:58So, I think how it's twofold.
  175. 14:00One is there's very few people who know how to train frontier models.
  176. 14:03I would say realistically probably less than 5,000 in the world at scale.
  177. 14:08I think that type of knowledge, that's a very exploitable search space.
  178. 14:11And actually as humans, all those configurations, we're not particularly good at.
  179. 14:15It's kind of like secret knowledge we pass as if, you know, we're apprentices.
  180. 14:20So, that's one.
  181. 14:21Like once you automate a lot of that knowledge, you just accelerate innovation cycles.
  182. 14:27Which means that you can explore and do more questions.
  183. 14:30Typically, what people I think often miss is that the cost of asking something informs what is asked.
  184. 14:38And if you make it cheaper to ask something, you change like the volume of things that are asked, which is super interesting.
  185. 14:43The other reason though, I do think it's very much a facet of like the changing nature of compute.
  186. 14:48So, agentic compute, post-training compute matters a significant amount for performance.
  187. 14:54That does not require the same type of um I dare I say hoarding of GPUs.
  188. 15:01[laughter]
  189. 15:01But like I think it it's very different compute purchasing dynamics.
  190. 15:05And again, it means that the person with the best idea has a higher chance of winning.
  191. 15:09Which is fun.
  192. 15:10Nice.
  193. 15:10What else?
  194. 15:11Who wants to go?
  195. 15:11I see Yeah, we can go up here and then I saw a hand back there.
  196. 15:15Okay, yes, I do see you.
  197. 15:16The glare is high, but you go first and then we'll come up here.
  198. 15:20So, Frontier Labs care a lot about safety.
  199. 15:23So, one of the challenges in safety
  200. 15:32Yeah, so the question I'll just repeat it so cuz I think there's probably people who want to know who are in the room.
  201. 15:37So the question was one of the I guess the counterpoints on some Frontier Labs about not enabling Frontier AI but outside is that is a safety question.
  202. 15:48So I think it would be I definitely am not one of those people who who says that open source doesn't carry any risk.
  203. 15:56So when you make a tool more readily available, there's a profile of risk associated with it.
  204. 16:01Um Auto Scientists is to be fair like it's about enabling people to customize their models.
  205. 16:06You can think of that as like a slightly different question from whether those are open source.
  206. 16:09It's giving people way more control.
  207. 16:11Whether that's local or private or within that company, it's about like how do they own their own intelligence?
  208. 16:18Um what do I think broadly about the impact of open source on safety?
  209. 16:25You can do so much the dynamic has often conflated like that real risk of like wider access with slight sense that that it it it restrains who can actually participate and I think that's a delicate balance.
  210. 16:41And I think you have to acknowledge risk by also navigating that and acknowledging that it limits who can participate.
  211. 16:46Yeah, so nuanced answer.
  212. 16:48So I I guess I should be more bombastic on that one but I I guess I have been in this discussion a few times and I find the binary views on other sides
  213. 16:56I feel like they miss a lot.
  214. 16:57But anyways, okay, go ahead.
  215. 17:08Oh, I think for for automating and speeding up learning, one of the core questions is how do you balance what you store in the parametric space and the non-parametric
  216. 17:17space?
  217. 17:17And actually, one of the most interesting things, I mentioned that this only work because we co-optimized data and model, um it will only work to do like an AutoScientist
  218. 17:28for harnesses if you also co-optimize it with a model.
  219. 17:31And so, it's interesting, it's actually a long horizon problem, and that's super fascinating to think about where you're optimizing the choices for each and co-training, which is cool.
  220. 17:39Nice.
  221. 17:39Uh I think we have time for maybe two more and then we can I'll pass on to the next speaker.
  222. 17:43Nice, go ahead.
  223. 17:44I have a question.
  224. 17:45We talked a little bit about this actually working on the post-training side of the models is actually cheaper than doing pre-training with public data.
  225. 17:53But like still, especially talking like really large models, like reinforcement learning, even fine-tuning is still pretty like GPU-intensive, so like you talked a little bit about like smaller models.
  226. 18:04But I still think that most like frontier smaller models still rely on like the bigger models to distill knowledge like downwards, not necessarily to be trained.
  227. 18:13So, how do you see this like like for the future, how to work like with these smaller models, how they can be start working without it being trained without depending on these larger models?
  228. 18:24Yeah, actually that's an excellent point.
  229. 18:26I think the question amounts to two points.
  230. 18:28One, are larger models necessary for distillation benefits?
  231. 18:31And then second, so frontier models are still pretty large.
  232. 18:35Um so, I think for the second one, frontier models are still pretty large, yes.
  233. 18:40I don't think I'm arguing that you um I I My argument is slightly different, and my argument is in no frontier AI lab is going to four exercise their model again for pre-training.
  234. 18:49So, it's almost like we know we're at an opposite for this architecture.
  235. 18:52If someone comes out with a new architecture, that's totally different, you can the architecture determines your ceiling, and I'm saying we are probably at the ceiling of size, which means that that's fine because it means
  236. 19:05okay, it's what you innovate within that.
  237. 19:07Um so, so size does matter.
  238. 19:09I I that's that's a very good point to bring up.
  239. 19:13Meaning I'm not advocating everyone use a 0.8B, but I am saying that we now have a more equal feeling for playing field at the the top.
  240. 19:20Second point is interesting, distillation like the impact certainly.
  241. 19:25So data quality in general means you use capacity a lot more.
  242. 19:28So you what you will see in pre-training is instead of the size people are just moving post-training further back, which is very fascinating and a bigger lever.
  243. 19:39So I agree distillation is helpful.
  244. 19:41It's just that again we've hit the ceiling and so it's almost like no one is going to supersize their model or if they do it's not clear it's beneficial
  245. 19:53except for small size of the distribution, which is very much the long tail and that's kind of interesting like where that trade-off is where worth that much pre-training compute.
  246. 20:01So very good question.
  247. 20:02One more and then I think we are done.
  248. 20:05Yes, go ahead.
  249. 20:10Yeah, it's actually in beta.
  250. 20:11So you can I shared here.
  251. 20:13You can try it in beta.
  252. 20:14So we actually are offering the GPUs for free.
  253. 20:17Okay, oh that's a nice question.
  254. 20:18[laughter]
  255. 20:20I promise I don't know this gentleman.
  256. 20:22But yes, I think actually we're trying to remove the compute hurdle and I think it's quite cool to see.
  257. 20:27So feel free to take a look at the beta.
  258. 20:30Nice, lovely.
  259. 20:30Thank you so much.
  260. 20:31Really nice.
  261. 20:32Thank you.