How do you automate experimentation? Doubtlessly, AI can iterate at superhuman speeds in the domains of thought and design: Software, mathematical proofs, literature search. But in the realm of experiment? Alas it is the lack of a body that constrains it. Rather than transcendence what AI requires is immanence. In the human flesh may we find the godhead living among men. Let the laboratories, warehouses, and factorie…
Discovery Loop
111–120 of 625 posts
Re: Discovery Loop
#112Re: Discovery Loop
#113How do you automate experimentation? Doubtlessly, AI can iterate at superhuman speeds in the domains of thought and design: Software, mathematical proofs, literature search. But in the realm of experiment? Alas it is the lack of a body that constrains it. Rather than transcendence what AI requires is immanence. In the human flesh may we find the godhead living among men. Let the laboratories, warehouses, and factorie…
You can use simulators. However the problem is that if you're for example running material science experiments, those simulations will consume a lot of compute and take weeks, so spamming different approaches in the way an agent tends to work might not work quite as well.
Re: Discovery Loop
#114I wonder if Jeff Dean facts [1] (I hope people remember the reference) will carry over to the new startup. [1] https://github.com/LRitzdorf/TheJeffDeanFacts
Those are all fake, part of an internal Google narrative that overstates individual contribution, and obscures the work of large engineering teams. Here are some Jeff Dean well sourced facts: - Already part of engineering of Google indexing systems that lacked basic checksums and ran on non-ECC hardware, allowing silent data corruption. - One of the authors of LevelDB a database with so many documented crash-consiste…
Re: Discovery Loop
#115Re: Discovery Loop
#116Earlier quoted context omitted.
Those are all fake, part of an internal Google narrative that overstates individual contribution, and obscures the work of large engineering teams. Here are some Jeff Dean well sourced facts: - Already part of engineering of Google indexing systems that lacked basic checksums and ran on non-ECC hardware, allowing silent data corruption. - One of the authors of LevelDB a database with so many documented crash-consiste…
You sound like you're quite jealous of him.
Re: Discovery Loop
#117Earlier quoted context omitted.
Those are all fake, part of an internal Google narrative that overstates individual contribution, and obscures the work of large engineering teams. Here are some Jeff Dean well sourced facts: - Already part of engineering of Google indexing systems that lacked basic checksums and ran on non-ECC hardware, allowing silent data corruption. - One of the authors of LevelDB a database with so many documented crash-consiste…
You sound like you're quite jealous of him.
Re: Discovery Loop
#118Re: Discovery Loop
#119From Jeff's twitter post: > Our general approach is to automate the experimental loop. We think this approach is broadly applicable across many different fields of science and engineering. We’ll initially focus on ML research and engineering, but believe the approach can help with important subproblems in nearly every one of the fourteen NAE Grand Challenge problems. We think doing this well requires strong expertise…