Two to keep in mind with these kinds of things -

1. There’s some irreducible costs in terms of time and material in the physical world that are not amenable to the kind of optimization or parallelization or even just the raw speedup from Moore’s law or computational architecture improvements we’re used to with software. My experience is primarily in biology, where the examples here are things like “it takes 20 minutes for E. coli to replicate” - it has taken 20 minutes for E. coli to replicate for a billion years, and next year it will still take E. coli 20 minutes to replicate, no matter how good your software stack is. Similarly, it takes X amount of energy to grow enough E. coli to produce a meaningful result, and that energy costs money, whether it’s in the form of glycerine or heat or whatever you want, and that also won’t materially reduce in the same kinds of “orders of magnitude” sense we’re used to from software, which is what we’re usually expecting to make the economics of these things work out.

2. Complicating the above, physical systems are phenomenally multivariate - far, far more than you think, and biological systems especially are just unbelievably complex - which means the number of experiments and the length and duration of those experiments you need to run to get enough data to be reasonably confident you’re seeing genuine signal is Way higher than you think.

Combine those two things and what you get is a money furnace, even before you get to the AI model training part, which is Also a money furnace. There’s low hanging fruits in all this, there’s areas where automating the approach can be really valuable, but typically the moment you turn this machine on, you’re gonna start burning money at a rate that would embarrass a finance bro on a coke bender, and that’s effectively unavoidable because the real world is not amenable to software’s scaling laws.