119 karma · joined October 15, 2019
Where I see models having a huge impact is in simulation code development.
One blocker for years now has been the adoption of GPUs. LLMs can fairly successfully and very quickly port to GPU and suggest/implement useful optimisations. Once it's verified, a code can go from anywhere between 2x to 1000x faster (mainly because CPU codes are so poorly optimised). Some science can reach much greater problem sizes, while some can run the same problems in hours rather than months and both can be revolutionary. Even more than that, LLMs seem to be finding fundamental performance bugs in both open and closed source core libraries so there's a bit of a whole-ecosystem uplift.
Can't comment on the more theoretical, less computational applied maths impacts!
In saying that, in the spirit of a good faith argument, is there value in temporarily deprioritising pure research in (current) times of funding drought?
Loved the (possibly not deliberately ironic) use of the LLM'S favourite analogy, load-bearing.
Nice wee article though. I particularly agree with "Don’t take all of the model’s copyediting advice." I've been using LLMs to review teaching material and often it just doesn't get the point of teaching. It's good for prompting reflection on your writing but it's still an idiot savant.
In saying that there are some novel and very clever algorithms that continue on without seemingly necessary boundary data, that then self correct when the data comes through, thus completely hiding the latency at the cost (in both accuracy and time) of running a correction process.
Your point on goods isn't... Good. Services is the majority but goods still make up ~1/3rd of exports, and don't forget we still have to import goods. Brexit affected that too.
truth of this unfortunately depends on the analysis of others, thus when those analyses . The data cannot itself show whether the
But then, I can also imagine a world where nobody cares enough about writing code and instead we have "human designed software" just as we currently have human designed cars and fridges but few made by hand (and no market for them). Then, handwritten software becomes an impressive curiosity like Chris Sawyer's original Rollercoaster Tycoon written entirely in ASM.
It's not the only option but jupyter notebooks are excellent for (at least) quick prototyping, data visualisation, literate programming and exploring ideas. I write plenty of Fortran and C++ and I still reach for notebooks when appropriate. In discussing with a non-technical, scientist friend, she pointed out that existing notebooks can be used and edited by folk even if they don't know python that well.
At the very least I see this particular tech as enabling more science by removing the operational challenge of running a jupyter server.
These tools take nothing from those who want to write fortran to do their science but make computation more accessible to those who don't.
That's a big reason I like developing games with frameworks. It allows reusibility and access to clever code, while still remaining flexible enough to support weird mechanics.
You critique the approach as brittle and yet the approach you propose doesn't solve the thorny problem gp described of a growing ball of reserved keywords.
I'd love to read a blog post or something on what you've discovered on good software patterns for AI. I'm only now getting into using LLMs and beyond the purely technical aspect of what LLM is "best" it seems like there's a wealth of learned experience in how to structure and write code to work well with them.
I've heard good arguments for using Rust with LLMs because the compiler keeps the LLM from making silly mistakes. What languages have you been developing in?
Similarly, there are a number of things that would be incredibly meaningful to all of society (eradication of disease, nuclear fusion, etc) that we choose to deprioritise to instead eat fois gras and fight.
Sorry to jump down your throat on this, we're on the same side, I think BI is inevitable and worthwhile. But it's worth pointing out that BI enables more than just the meaningless things.
That's a very nice rule of thumb. I've often overabstracted when two pieces of code look similar at one point in time and then they diverge.
That's less of a different model and more a different way to rewrite the equations to make them easier to analyse or simulate.
We might be talking at slightly different angles here. There's a strong difference in the equations between compressibity of the fluid due to compression and changes in density due to temperature, chemical concentration, etc. The term compressibility usually refers to the first usage, and modelling it leads to sound waves in the system and has major implications for how the system is simulated, I mean it's an entirely different class of algorithms. The second, where density still changes but not due to compression, so no sound waves, that can be easily modelled without including full compressibility. This allows (generally simpler) incompressible models to still incorporate useful thermal physics where important, like in climate and weather. Also, the smaller the scale of the system the more compressibility matters so I wouldn't be surprised if compressibility starts to matter for e.g. Tornados. But I'm not certain on that...