Qwen3.8-27B IQ3_XXS wrote a correct multilayer TMM on a 16 GB Quadro — after 100 minutes, 3 compactions, and 108k output tokens
Mirrored from r/LocalLLaMA for archival readability. Support the source by reading on the original site.
| I wanted to see whether a heavily quantized 27B model running entirely on an older 16 GB workstation GPU could do more than the usual coding demos. FFT felt too easy, so I asked it to implement the coherent optical transfer-matrix method (TMM) for absorbing multilayer films from scratch. TL;DR: the implementation was correct long before the model believed it. It then spent most of the remaining hour debugging its own broken validators. Hardware
Model and serving stack
The agent UI was DeepSeek Harness The taskThe prompt required a pure Python implementation using only
The 100-minute reasoning sagaThe complete agent turn lasted 99 minutes 53 seconds. The session log contains 22 model steps, 21 tool calls, and 107,594 model output tokens. The first model call alone produced 43,033 output tokens and took about 27 minutes before it finally wrote There were three context-compaction attempts. The first two each spent almost six minutes generating a checkpoint and then failed because the summary itself hit its token cap. Only the third compaction succeeded. Total time spent compacting was almost 18 minutes. Watching the chain of thought was honestly painful. Qwen repeatedly re-derived the same field conventions, lost track of which direction its matrices propagated, found a contradiction, announced that everything was verified, and then invented another validation method that contradicted it again. The branch/sign problem was interesting. For the requested passive In other words: calculate one square-root branch and simply flip it if the normal wavevector would grow instead of decay in the forward direction. No complex-arcsine heroics. That is correct for the passive positive-index materials in this test. It is not a completely general branch selector: it lacks a tolerance and a forward-Poynting tie-break when The other funny part was the apparently "reversed" algorithm. The implementation uses a characteristic matrix whose giving Ironically, Qwen later forgot its own convention in an external validator, used It spent most of the run debugging its refereesTwo supposedly independent validation approaches were repeatedly broken by the model:
It also briefly rejected a quarter-wave antireflection test because its validator used the wrong expected refractive index. It corrected that to The definitive internal check was a completely independent 6x6 linear solve for all forward and backward amplitudes in the two-film stack. That matched the TMM result to about External resultI then compared the generated solver against Steven Byrnes' established For
I also tested three thick, weakly absorbing dielectric films to generate lots of Fabry-Perot fringes:
That spectrum contained 38 resolved maxima for s and 29 for p. Maximum disagreement with Byrnes was So yes: a roughly 3-bit 27B model on an older 16 GB Turing GPU produced a genuinely correct niche numerical-physics implementation from scratch. The quantization did not prevent it from getting the final mathematics right. But the agent behavior was equally instructive. More autonomous validation was not monotonically better. Once the initial implementation and analytical limits were correct, the model spent over an hour creating bugs in its own "independent" checks and then reasoning in circles about the contradictions. The implementation was right long before the model believed it. It spent most of the hour debugging its own referees. Has anyone else seen this pattern with local reasoning models—good primary solution, followed by a validation death spiral? I would also be interested in comparing the same task across IQ3, Q4, and higher reasoning-effort settings, although I am not eager to watch another 108k-token derivation immediately. EDIT: Formatting [link] [comments] |
Discussion (0)
Sign in to join the discussion. Free account, 30 seconds — email code or GitHub.
Sign in →No comments yet. Sign in and be the first to say something.