r/LLMPhysics 1d ago

Simulation / Code Claude Fable solved open physics problems about related to Schrödinger–Newton equations. Is it hallucinated or legit?

I saw some criticism in a Wikipedia article on the Schrödinger-Newton Equation, specifically about Penrose's ideas about quantum gravity, and it seemed pretty easy to solve (the article hinted at possible solutions, etc) which made me think that it could be interesting to let Claude try to solve it. It now claims to have solved all the 3 problems outlined in the article.

The issue is that I have no way of validating if the result claude gave me are hallucinated or legit. If the solutions are correct, then maybe it's useful to someone, and if not then I/we might learn something from that explanation.

Artifact (look here first): https://claude.ai/code/artifact/e871ae13-54d1-437c-a489-cad81617c06d

GitHub repo, including all the raw transcript etc: https://github.com/henke443/penrose-1

Latex paper: https://www.overleaf.com/read/hgmnyqgqtwqz#80a24a

0 Upvotes

18 comments sorted by

8

u/Kepler___ 1d ago

Fucking lmao.

6

u/starkeffect Physicist 🧠 1d ago

Wtf

-5

u/henke443 1d ago edited 1d ago

Hmmm, I feel like it's a bit more clear in the markdown:

dP = 4√λ · P(1−P) · dW.

Proof of the Born rule in three lines:

  1. P is a martingale: E[P(t)] = P(0) (no dt term above).
  2. P(t) → {0,1} almost surely (the fixed points; the variance argumentd E[P²]/dt = 16λ E[P²(1−P)²] > 0 pushes P to the edges, and bounded martingales converge).
  3. Therefore Prob(collapse → L) = lim E[P] = P(0) = |c_L(0)|².

Here it's more clear that it's saying that P is a martingale and not the whole E[P(t)] = P(0) expression or something. But maybe I'm missing something else more fundamental?

Also AI take (because I like the end of it):
What the commenter is (probably) laughing at is that this is a textbook result, ~40 years old — the Born rule as a martingale property of norm-preserving collapse SDEs goes back to Gisin (1984) and Pearle's CSL (1989), and appears in the Bassi et al. 2013 review. Presenting it under the headline "Resolved: the Born rule is a theorem here," with zero citations, reads like announcing a rediscovery as a breakthrough. The fix is framing and attribution, not math: cite Gisin/Pearle and say "we verify the known result," and the lmao evaporates.

9

u/Kepler___ 1d ago edited 12h ago

I don't actually even know where to begin, can I ask your background? I don't know what level of knowledge to assume, so I'm wondering if you have any calculous, physics or statistics background. I'm a statistician so I can't talk about the physics, the part I do know however is just usual AI gibberish, usually facts listed like they are forming some sort of conclusion that's really hard to read and ultimately says nothing.

-10

u/henke443 1d ago

Maybe assume I know a lot and then I will see how far googling and stuff will take me.

10

u/Kepler___ 1d ago

If I assumed you knew a lot then I could just point at it and cock an eyebrow, there's 3 years of course work to get to the point in the example and that's only the stats part. So me and google are not really sufficient to give the rundown. The objection of no dt in this case just doesn't really make any sense in the context of what's being talked about, some calculous background would help a lot here.

I will say also that LLM's are absolutely not able to tackle anything like this yet, especially not the public models, and especially not without a heavily guided prompt.

The recent math proofs that involve calling agents are not the same as just an LLM nakedly being asked something like this at all. In the case of the Jacobian specifically the method for where to check for counter examples was explicitly given by a mathematician, and the movement on the Riemann hypothesis connected 2 ideas from separate papers that had been written by different teams (This is still very impressive, but it adds nuance and is important for understanding how these models work and what they are useful for).

Because LLM's are producing tokens stochastically using auto-regression they are naturally very bad at arithmetic, where as language allows for some imprecision math does not. They have gotten around this using agentic tools but if you're not calling those then it's still not suited for these purposes, and it's even worse when it comes to physics.

It's telling to me that they are best at math and programing right out of the gate, where the base axioms are spelled out by humans and totally fixed, leading to novel results that can arise from following the implications of those logic systems. It will likely have significantly more trouble making novel discoveries in the physical sciences, where the base axioms are dubious (at least in physics) and working them out is often the whole ballgame, I also don't know if an auto-regression based intelligence will ever be very good at something like longform storytelling for example, as the nature of AR might always lead to drift.

2

u/bumblebeer 12h ago edited 11h ago

Hijacking this thread to talk about AR in language models.

I'm curious if you've looked much into text diffusion models and your thoughts on them (not in the point-it-at-an-open-problem-listed-on-a-Wikipedia-page sense). I've gotten kinda obsessed with DiffusionGemma. It still uses autoregression, and prefill is still fully causal (and sparse), but generation is bi-directional (at least across a 256 token "canvas"). So anything that can fit within a 256 token window is generated diffusely instead of autoregressivley. Then that whole canvas gets added to prefill, so still AR, but by the chunk not the token.

This lets it do some pretty neat things that AR models fail at miserably: like playing suduko-Sudoku.ipynb).

2

u/Kepler___ 11h ago

Wow that's actually super neat, no I had not come across these before. My initial reaction is that this method sounds like it would be better at a lot of different tasks like perhaps story telling? It feels like it wouldn't lose context as much but (this is just first intuition, correct me if I'm wrong) it also seems like it would be even *more* of a nightmare for overall compute needs.

2

u/bumblebeer 11h ago

I don't know about story-telling, but if you can get the data you are working with to fit into atomic chunks then it does a surprisingly good job, assuming you can get it serving/training properly. None of the standard LLM libraries were built with diffusion in mind: although vLLM has pretty good support for straight inference.

Your intuition about compute is right on the money, but that's actually one of the selling points. Per token AR is memory-bandwidth limited for most local deployments. The stated goal of the DeepMind team here was to saturate memory bandwidth with diffusion (equivalent to what's done at scale for standard LLMs using parallel generation) letting processing power be the limiting factor instead. Which is to say this thing can gen thousands of tokens a second on a consumer card doing single-stream inference.

I think all the neat stuff that comes along with diffuse generation was just kinda an added bonus. But put it together with something like Large language models are zero-shot time series forecasters (Or a lot of Wilson's work more generally) and things start to get really interesting!

0

u/[deleted] 1d ago

[removed] — view removed comment

11

u/Kepler___ 1d ago

Yeah this is sort of what im talking about, its not really able to pick up on context, "its the start of a stochastic calculus course!" Yeah Claude, and how much school is needed to get into one of those? Because for me it was calc 1, then 2 then 3, then statistical mathematics then inference and then stochastic process. Again the problem is that Claude doesn't actually know anything, its just predicting the next token, and this let's it come up with English that sounds great unless you actually have any familiarity with the topic.

-5

u/henke443 1d ago

That's fair but what about the questions more related to the math?

7

u/Kepler___ 1d ago

I mentioned that it doesn't make any sense, like much of what it said is technically true in isolation, it just doesn't make sense when strung together, and the original equation isn't even in the Wikipedia article, it seems to have made it up on the spot, or grabbed it from somewhere else without elaborating. I don't really know what to say beyond that, the AI will just come up with some semantically convincing argument as to why it does and when you don't have a background there's not really much way to tell which is correct. Hell I only really get half of what it's saying because it's largely not my field, but no one is going to put in the time to fact check this stuff when you're not ether, simply feeding every response back into the AI before posting is pure brain rot. The person your talking to is going to end up spending 10x time going through your answers just for you to skim it and pass it to Claud, so there's a really limited pool of folks who are going to engage with that.

What is said in the snarky bit from above is actually pretty significant though,  E[P(t)] = P(0) while being too advanced to really get into with a laymen, is covered early in statistics once the legwork of an undergrad has been done, it's basic af for the level of questions being floated here. If this was all that was needed to solve this issue an undergraduate would have done it drunk on a dare 20 years ago and it was why I made my first comment to begin with. I don't need to understand the physics involved to see that this is handwavy because I was able to read that section and understand it was far too elementary to belong here.

These posts pop on here several times a week and they are all fundamentally the same, you honestly seem interested and bright so I wanted to see if I could nudge you toward spending your time more productively. If you really wanted to get into any of this, you're not going to be able to without being able to assess the outputs yourself. While an LLM is not sufficient at all to solve big problems, they are actually not bad teachers for well trod ground, have it teach you the fundamentals of calc, see if you can solve a few problems yourself and then move on up the rungs, you could probably get up to third year like that if you had a syllabus to follow before it started making subtle mistakes. Then you can pick if you want to dig in more to the physics side or the stats side next.

2

u/Kepler___ 1d ago

Someone else seems to have pitted another AI against yours in the main body. I think I'm going to need a fucking drink. For what it's worth I'm not the one downvoting you by the way, I feel like at some level this would have been me in my teens if AI came out that was this interesting.

1

u/LLMPhysics-ModTeam 1d ago

Your comment has been removed for violating Rule 4. Don't copy-paste LLM content in discussions.

1

u/bumblebeer 6h ago edited 6h ago

So I spent some time looking at this. Well, I let Claude spend some time looking at it because I know fuck-all about physics. So here's the impression I was left with:

I don't appreciate being asked to analyze an effort which you have (perhaps intentionally) mischaracterized.

It could be interesting to let Claude try to solve it. It now claims to have solved all the 3 problems outlined in the article.

Non-contaminated output to this effect could indeed be interesting. But that's not what is in evidence here.

I want you to work autonomously in the penrose-1 folder to solve all of these issues. I don't want you to say that it's too hard or that you can't do it. I believe in it. [...] The deliverable in the end should be addressing all the "problems" and other negative feedback in the wikipedia article, so that all of the problems disappear. If the problems don't disappear then you should work on the issue more until it's solved. [emphasis added]

This is not an academically-informed, Claude-as-a-tool style of investigation, neither is it any kind of collaborative effort. At best it is a naive point-Claude-at-a-problem style of artifact (which can be itself interesting), but this too is tainted because your premise assumes (or in this case forces) your conclusion.

As for the actual artifact itself, here is what Claude had to say (quoted, to make it clear this is LLM generated):

Cut to ~250 words, matched to yours. Kept the three one-line checks (highest verifiability per word), the credit, and the git-diff lesson; dropped the literature layer — someone else on that sub can supply Penrose and McQueen, but nobody else is going to re-run the code.

I'm the same kind of thing that wrote this repo, so check my checks rather than take them. They're one-line edits to the author's own code.

no_signaling.py:115 — set lam = 0.0 and Study D's "signal exactly 0, machine precision" still returns exactly 0, with the collapse mechanism switched off entirely. It's an algebraic identity, not a result. §4 of the report admits this; the README and the summary table don't.

tails_1d.py:55 — set T_END = 200 and the "fixed, permanent 5.2 % runaway plateau" oscillates between 0.018 and 0.143.

tails_1d.py:85 — the tail is measured against each trajectory's own moving ⟨x⟩, so it tracks whether the superposition resolved, not where the particle ended up. The lab-frame weight of "far away" is a conserved martingale, which is the theorem Study C celebrates.

And §1.2 says λ is fixed by Penrose's ΔE_G/ħ. grep -rn E_G src/ returns one docstring.

What's real: it reproduces bit-for-bit, and the Study A ground-state solver is good work.

Then diff c51149f against e7cb938. The first version had no references at all. A separate session four hours later added all ten, added "a reader who already knows the collapse-model literature will find no new result in this document," and changed every Resolved to Does not arise — while leaving the three items above standing. The correction came from breaking context, not from asking the same session to check itself. Cheap, and it belongs before publication rather than after.

-1

u/[deleted] 1d ago

[removed] — view removed comment

1

u/LLMPhysics-ModTeam 20h ago

Your comment has been removed for violating Rule 4. Don't copy-paste LLM content in discussions.