Second question first
skippy1729 said:
...Second question: There are three or so research centers where CDT is studied. All of their "experiments" are based on numerical simulations. Is any of the simulation source code "open source" or is it all proprietary.
...
My understanding is that the Utrecht code, by Loll's group, is freely available. I spoke with Steve Carlip (UC Davis) about their CDT project and what he implied was they COULD HAVE used the already existing Utrecht code but they
chose to write their own. Somehow it is more like "repeating the experiment" in the tradition of empirical science, if you write your own code. Then if it happened that the Utrecht group had made a programming error and their beautiful results were all the result of a mistake (! unlikely but conceivable) then hopefully you would not make the mistake and you would get different results. Experiments should be repeated from scratch. And these are in a certain way "numerical" experiments.
So Carlip's UC Davis grad student had to write the whole CDT monte carlo code. And he did. And it runs. I saw some graphic presentation of output.
I haven't personally verified that anybody can get Loll's code. She says it can run on a a work station. I believe however that it is open source and available without charge. If you were to email her she might want to know if you are connected with an institution, using it for research, for a PhD thesis, or whatever.
I don't know if there are any requirements or restrictions. You'd have to write Loll email and say "what requirements? what restrictions? if any." and she would probably answer a simple question like that. Why not?
Carlip said that Joe Henson is running the Utrecht CDT code at Perimeter in Canada. At least I think this is what he said. My understanding is Henson did not write his own, like Carlip's grad student did.
Jerzy Jurkiewicz in Warsaw is another member of Loll's group. He and his PhD students probably run Utrecht code, because Jurkiewicz helped develop it. There must be more than 3 places now if you include Warsaw.
Joe Henson would be another person you could write to. He is postdoc at Perimeter.
Used to be postdoc at Utrecht. Maybe he is less busy than Loll and would respond quicker.
==============
The 4D triangulations are made up of a sequence of 3D triangulations or slices which are "glued" together with {4,1}, {1,4}, {3,2} and {2,3} 4-simplices. The {A,B} notation denotes A vertices on the time=t slice and B vertices on the time=t+1 slice. The 3D triangulations are constrained to have the same topology (usually S3) and are made up of equilateral spatial tetrahedrons. So a tetrahedron at time=t forms the base of a {4,1} simplex with one point at time=t+1 and likewise a tetrahedron at time=t+1 forms the base of a {1,4} simplex with one point at time=t. The "gaps" are filled with the {3,2} and {2,3} simplices.
You have it exactly right. I remember learning this from a 2001 paper that has a lot of diagrams and works up from the 2 and 3D case.
My first question is: Intuitively or algorithmically, how are these "gaps" filled with the {3,2} and {2,3} simplices? I would be happy with an explanation or a reference where it is clearly explained. My 4D geometric intuition is severely challenged.
As I recall the way you gradually grow your intuition is you first study the 3D case. Here is the 2001 paper:
http://arxiv.org/abs/hep-th/0105267
For starters forget 4D and forget curved. Focus your mind on 3D and uncurved.
So space is flat 2D. Imagine it paved with equilateral triangles.
Imagine two flat 2D copies of space each paved with equilateral triangles. Now you have to make the tetrahedron sandwich that joins them.
The tets are (3,1) and (1,3) and (2,2) -----when you go up to 4D that (2,2) case will spit into two cases .
Imagine them. (3,1) is like a pyramid point up, sitting on its base. (1,3) is a point down pyramid.
A (2,2) tetrahedron is like resting on a horizontal bottom edge that runs north-south, like the keel of a boat.
And it has a horizontal top edge that runs east-west, like the ridge of a conventional peaked roof of a house.
Say you have two (3,1) tets sitting side by side, their two edges meeting along a N-S line (on the time=t ground)
then that makes a perfect gap or crevice where a 2,2 tet can fit between them.
Its keel runs N-S and its roof ridge runs E-W, joining their two vertices.
Loll allows the tets to not be equilateral. To have their horizontal edges be shorter than their "timelike" rising edges.
When you are learning, FORGET this extra complication. Consider everything simple and flat and equilateral. Make it easy for your mind.
I have even cut equilateral tets out of modeling clay. One time I also cut small tets out of carrot or potato in the kitchen.
Just to fit together and play with. Why not? You can eat the carrot later and it is very healthy.
Then when you are very comfortable with the flat 3D case, it is time to advance to curved 3D, and then to 4D. You can ask again later if you find it helpful to discuss this kind of thing. the main thing is to be patient and gradual with your grey matter and its intuition. Then the whole business actually can proceed quickly, paradoxically because you are not rushing.