https://www.wolframphysics.org/questions/quantum-mechanics/how-does-quantum-entanglement-occur-in-your-models/
 :

Q. How does quantum entanglement occur in your models?

A. Two global Wolfram model states are said to be “entangled” if they share 
a common ancestor in the multiway evolution graph. Since spacelike-locality 
is not a necessary condition for branchlike-locality, it is possible for 
these states to be causally connected (i.e. to be connected in the multiway 
causal graph) even if they are not spatially local. This is the essence of 
quantum entanglement as it occurs, for instance, in the context of Bell’s 
theorem.

@philipthrift

On Friday, August 7, 2020 at 6:38:33 AM UTC-5 Lawrence Crowell wrote:

> That might be, but a programming language that has no context with 
> anything is not that valuable. At least it is not that valuable to me. My 
> point is this seems to connect with concepts of spacetime as built up from 
> large N entanglements.
>
> LC
>
> On Thursday, August 6, 2020 at 4:17:44 PM UTC-5 [email protected] wrote:
>
>> Ultimately this is not really about "theory" (in the usual sense) at all, 
>> It is about defining a programming library: So it's really in the end a 
>> programmer's manual.
>>
>> *Wolfram Physics Project Functions*
>> https://www.wolframcloud.com/obj/wolframphysics/Tools/guide-page
>>
>> *Hands-On Introduction to the Wolfram Physics Project*
>>
>> https://www.wolframcloud.com/obj/wolframphysics/Tools/hands-on-introduction-to-the-wolfram-physics-project.nb
>>
>> (an extension of the Wolfram language/ecosystem)
>>
>> All of general relativity, quantum mechanics, and whatever comes next is 
>> to be written as programs in this library/language.
>>
>> @philipthrift
>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Everything List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/everything-list/ccac2e7d-7f04-4eec-81c7-e7b3c3f01b7cn%40googlegroups.com.

Reply via email to