Whenever we start working on some project, at first everything we do, seems to be, and often is, very complicated. It is only with time, and with experience, we learn how to simplify our task, sometimes in an extraordinary way. We find shortcuts, we invent tricks, we learn from other experienced people whom we meet due to our unceasing efforts.
I asked AI to provide an example illustrating my preamble above, and here is the result:
"Historical Example: Richard Feynman and the Manhattan Project
![]() |
| Feynman simplified one group’s approach |
When Richard Feynman joined the Manhattan Project at Los Alamos during
World War II, he was of the
brightest minds of the century. At first, the work was incredibly
complicated: the project involved calculations of neutron diffusion,
nuclear reactions, and bomb design—concepts that were at the cutting
edge of physics, and far from straightforward.
Feynman found himself and others bogged down with repetitive,
error-prone hand calculations. Every problem seemed daunting. But over
time, through relentless experimentation and observation, Feynman began
finding clever shortcuts.
One breakthrough came when he noticed that some of the mathematical
tables used for calculations were riddled with mistakes. Instead of
doing everything manually, he started looking for patterns in the errors
and designed faster ways to check and simplify the calculations. He
even taught himself how to use mechanical computing devices better than
the engineers assigned to operate them, often streamlining the whole
process.
In a particularly telling anecdote, Feynman simplified one group’s
approach to neutron diffusion by realizing they were unnecessarily
solving a full partial differential equation when an approximation and
symmetry argument would give an answer almost instantly. This insight
not only saved time but brought clarity to the underlying physics.
What had started out as complex and overwhelming became manageable—even
elegant—through experience, effort, and creative shortcuts."
In a series of previous posts we were discussing the space R2,2, two dimensional space and two-dimensional time, to study the conformal compactification of R1,1, a toy spacetime with only one space dimension. We played with the Clifford algebra Cl(2,2), and we have a somewhat strange doubling. Matrices representing R22 vectors were block-off diagonal, matrices representing Spin(2,2) were block diagonal. They contained a lot of zeros! Why do we need all these zeros? Can't we get the desired result without all these zeros? The Eureka came onto me only yesterday. I checked if my discovery has no errors, and it seems that all works as desired. At the same time we are getting a new insight into the internal machinery of the whole structure. Which makes me happy. Doing all this I recalled one of the songs that I like. It has these words.
And happiness is close, happiness is far.
It is difficult and easy to find
It sounds much better in the original Russian (Роксана Бабаян):
А счастье близко, счастье далеко.
Его найти трудно и легко.
You can find the song online.
There is a movie "Maestro". We have another annoying doubling there: "American composer Leonard Bernstein (Bradley Cooper) lives a double life." The same with our Cl(2,2). We do need all this suspicious doubling. We do not need all these unnecessary zeros. So let us simplify everything from scratch. What we need is R2,2 and Spin(2,2) isomorphic to SL(2,R) x SL(2,R).
The solution.
R2,2 is already a Clifford algebra! Namely it is the Clifford algebra Cl(2,0) aka Cl(2). Excellent notes "Clifford algebra, geometric algebra, and applications" by Douglas Lundholm and Lars Svensson provide the hint in Exercise 2.5, p. 13:
Exercise 2.5. Find an R-algebra isomorphism
G (R2)) → R2 × 2 = { 2 × 2 matrices with entries in R } .
Hint: Find (preferably very simple) 2 × 2 matrices γ1, γ2 which anti-commute and satisfy γ12 = γ22 = 12 × 2 .
Note. Sec. 2.2 of this paper describes "Combinatorial Clifford algebra" - the concept I was not aware of before.
We will do it in details in the next post.
P.S. 18-07-25 18:19 The next notebook will use the calculation in this Mathematica notebook:
e1 := mat((1, 0), (0, -1));e2 := mat((0, 1), (1, 0));e12 := e1 * e2;omega := e12;id := mat((1,0),(0,1));e3 := id;e4 := e12;invomega := -omega;xmat := x1*e1 + x2*e2 + x3*e3 + x4*e4;ymat := y1*e1 + y2*e2 + y3*e3 + y4*e4;procedure gradeinvolution(z);beginreturn omega*z*invomega;end;procedure reversion(z);beginreturn tp(z);end;procedure cliffconj(z);beginreturn reversion(gradeinvolution(z));end;procedure delta(z);beginzc:= cliffconj(z);return zc * z;end;gradeinvolution(xmat);reversion(xmat);cliffconj(xmat);delta(xmat);end;

Thank you for this post/note, it clarified things extensively which apparently I got very wrong recently, and as the title says: these same things also got simplified in earnest!
ReplyDelete@Saša, couldn't you please say a little more about what this post clarified that you had got wrong before?
DeleteWell, in short, I got many things mixed up, one time and one space dimensions, two plus two dimensions, of positive and negative signatures, not paying attention about differences between vector spaces and algebras, basically not really understanding what compactification means (still kind of don't, but at least realizing that and taking it into account not to jump to conclusions).
DeleteIn principle trying to relate what Ark's been presenting here "immediately" to physics and things observed in Nature, while there could be, and often are, still few steps until reaching that state of "identification". So learning to be a bit more patient and just learn new things on the way, kind of leaving expectations, anticipation and thinking that I got things completely understood on the side/margins, hopefully not being plagued by all that, but just enjoying the process of learning and discovery.
Or at least something like that.
Thank you, now I see that you meant not a specific idea that you have got, but rather a deeper understanding on a worldview level.
DeleteArk, in P.S. 18-07-25 18:19, Mathematica notebook, I cannot find identification of Simplify[...] operation. This is unlikely to be a standard tool, so the intrigue remains until the next post.
ReplyDeleteAnna, are you familiar with any computer algebra software?
DeleteArk, long ago, I coded in Algol, Basic, Pascal, and C. Then I wrote Java scripts for websites, and recently tried Python. That's all. Oh, and sometimes I used Wolfram Mathematica
DeleteIf you have programmed in Algol, you will have no problems with Reduce. You better install it and start playing. I will be using it more and more. In the next post in one of the exercises, tomorrow.
DeleteSo, "Simplify" is a built-in function of Reduce, ok. That was all I asked about, thank you!
DeleteRe today's P.S., e3 in Reduce code differs from e3 in Mathematica, one is Id, the other -Id. FWIW.
ReplyDeleteYes, you are right. I decided today to use Id. Perhaps I will have to pay for it later with time going backwards, but so be it!
DeleteThe reason for original minus will be clear when we will see how our 2x2 matrices relate to 4x4 matrices used in Cl(2,2). This is for later though.
DeleteSo would the 2-volume form symplectic double Minkowski structure mentioned in the previous post's comments have a Sp(8,R) structure group? If so I think I might like that given the Cl(4,4) middle grade's own 1 16 36 16 1 grading of sorts.
ReplyDeleteJohn, you are very ambitious. You ant to do something really serious. Before taking on serious tasks I want first to play with toys, to grow my muscles, and to have lot of fun. It is while freely playing, freely like children do, that we can discover mysteries that adults will never discover! Look around and you see the terrible results of adults' efforts - wars, bombings, lies, everywhere. Nobel Prize totally discredited.
DeletePlay is kind of all I can do and I have two ways of playing. One is related to the SO(8) root lattice being useful for plotting Jungian personality bivectors and the other is due to Cl(8) being useful for the 256 rules of elementary cellular automata. Physics kind of just happened to be the place where SO(8) and Cl(8) get talked about the most so my original interest kind of becomes more the analogy instead of physics being the analogy for my original interest.
DeleteI have exactly two papers on viXra, one for each of my original interests being related to physics but they both have the maximum 5 updates and I will probably update one of them with a new paper on the AI assisted version of viXra. I basically used AI to compare you (EEQT) and Tony's use of CL(8). Tony does very little with the Cl(8) middle grade so I basically have AI discussing the toy version of the middle grade (Lorentz boosts) but I still want to cover the whole middle grade with my best guess and that middle 36 is the part I'm least sure of.
The Reduce download and run worked for me with the in function or just copy and paste of the code but with selecting the file from the file menu it runs but I can't read it because the window closes as soon as it finishes running.
ReplyDeleteIt runs fine for me, so I can't reproduce this bad behavior. Perhaps ask AI for a diagnostic?
DeleteI also noticed after File/Read, it looks automatically for directoris in the Path variable. So, it is good to put the .red file in one of these directories.
DeleteThe closing window phenomenon may be realted to the editor you are using to save the file. Try using simple a simple editor, perhaps Notepad, perhaps even something simple, free, and special for code editing. Do not use Word etc.
I am using emEditor:
Deletehttps://www.emeditor.com/text-editor-features/history/emeditor-free/
I was using notepad and it does still do in the path variable path or with the executable file's directory. ChatGPT said the following (which included using the in command that did work and I'm very OK using anyways):
DeleteThanks! You're on Windows 10, using CSL Reduce, and you're double-clicking .red files. That explains the behavior — here's exactly what's happening and how to fix it:
❗ Why the Reduce Window Closes Immediately
When you double-click a .red file, Windows opens it in the Reduce CSL interpreter, runs the file, and closes the window as soon as it's done, even if there's an error or output — because it's launched in a non-interactive, disposable terminal window.
✅ Best Solutions
🔹 Solution 1: Run Reduce from Command Prompt (Recommended for debugging)
Open Command Prompt (cmd.exe).
Navigate to the folder with your .red file:
c
Copy
Edit
cd path\to\your\file
Run Reduce manually with:
c
Copy
Edit
reduce.exe yourfile.red
This keeps the window open, so you can see output or errors.
🔹 Solution 2: Use a Wrapper Batch File with pause
Create a .bat file (e.g., run_reduce.bat) in the same folder with:
bat
Copy
Edit
@echo off
reduce.exe yourfile.red
pause
Now double-click the .bat file instead of the .red file. It will:
Run your script
Wait for a keypress before closing
🔹 Solution 3: Use Interactive Reduce (recommended for working/testing)
Launch reduce.exe without a script (from desktop or start menu if installed).
Once inside the Reduce prompt (1: ), load your file:
r
Copy
Edit
in "yourfile.red";
It will run and keep the session open for further interaction or review.
🛠 Bonus Tip: Associate .red Files with a Persistent Editor
Instead of double-clicking .red files to run them, you might want to:
Open them in an editor like Notepad++, VS Code, or Emacs.
Then run them in Reduce manually.
This avoids accidental "run-and-close" behavior and gives you control over the process.
All complicated. I was alway running .red files typing "in ..." in the window. If there is an error, file will not run. If you change something in the file and save it, press "arrow up" on your keyboard. Reduce remembers the last successful command, even from another session, and will type the "in..." line for you.
Delete