[mxplxxx (OP)]

Here is the skeleton Visual Basic code for a 3dSystem. This allows you to create open-ended systems that are infinite in scope.

Code: [Select]

Namespace Library

    <Serializable()>
    Public MustInherit Class _3dSystem

        ' a 3dSystem is the base building block of the Universe. It consists of an outer Shell containing a Star (central/inner) System and Shells radiating out from the Star.

        Public Property Parent As _3dSystem
        Public Overridable Property DataStore As DataStore.System               ' persistence
        Public Overridable Property Star As _3dStar                            ' central/inner system containing state data (e.g. sun in solar system)
        Public Overridable Property Shells As sortedlist(Of String, _3dShell)  ' shells in order possibly containing (sub) _3dSystems

        ' create a new base system object

        Public Sub New(Parent As _3dSystem, Star As _3dStar, Optional Shells As sortedlist(Of String, _3dShell) = Nothing, Optional DataStore As DataStore.System = Nothing)

            Me.Parent = Parent

            Me.Star = _Star

            Me.Shells = If(Shells Is Nothing, New SortedList(Of String, Shell), Shells)

            If DataStore Is Nothing Then
                Me.DataStore = If(My.App Is Nothing, Nothing, My.App.DataStore)
            Else
                Me.DataStore = DataStore
            End If

        End Sub

    End Class

    Public MustInherit Class _3dShell

        Public Overridable Property Systems As sortedlist(Of String, _3dSystem)

        ' get a group of systems having the same parent

        Public ReadOnly Property Group(Parent As _3dSystem) As List(Of _3dSystem)
            Get
                Dim group_ As New List(Of _3dSystem)

                For Each system_ As _3dSystem In Systems.Values

                    If system_.Parent Is Parent Then
                        group_.Add(system_)
                    End If
                Next

                Return group_
            End Get
        End Property

    End Class

    Public MustInherit Class _3dStar
        Inherits _3dSystem

        Public Overridable Property Version As Integer
        Public Property LastUpdated As DateTime

    End Class

End Namespace


[Bored chemist]

You have explained how you imagine that the world is so composed.
That's no reason to believe that it actually is.

[ron123456]

Dismissing quantum jump, just think of the electron spiralling down to the next lower energy level by spiralling down around the nucleus. This would produce a diminishing wavetrain from high energy level to low (a photon). For Hydrogen, this could easily be calculated from the Bohr model.

[alancalverd]

Problem is that the Bohr model is so obviously incorrect that any calculation based on it is invalid.

[ron123456]

Really?....just extrapolate mathematically to 3D for Hydrogen and only Hydrogen for the wave train…...simply can be explained with antenna theory and eliminate the quantum jump!

[mxplxxx (OP)]

3dAbstractions is a computer system. You can do whatever you like, including moving an electron between shells/levels on either the receipt of an event (a boson) or the expiry of a timer within a 3dSystem - providing the action obeys any constraints associated with the event (or natural laws in the case of Reality).

Events will be generated at a 3dSystem boundary via receptors (as you would expect in a neural network). I am currently working on this. There is nothing random about events in a 3dSystem. Everything has a purpose (even random events!). Ditto for Reality. Everything is based on things that worked for a System in the past, and random events are probably generated based on the possibility of them creating beneficial mutations.

e.g. in visual basic:

Code: [Select]

   ' Raising system (Photon as Photon.System in this case, Event Happened(Frequency as Double).

   Raisevent Happened(Frequency:=Frequency)

   ' Receiving System (sender = Photon, e = Frequency))

   Private Sub QuantumLeap(sender As Object, e As EventArgs) Handles Photon.Happened

        ' move an electron from one shell to another (just an example - operation would be generalized based on frequency of photon in Real deal

        me.Shells(0).Electrons(1).Move(MoveTo:=me.Shells(0).Electrons(0))


[mxplxxx (OP)]

Events in computer science record the change of state of an object at a point in time. This is also the case for 3dAbstractions. 3dEvents are processed by 3dSystems in an identical manner from system to system. That is they are scaled up and down along with the systems themselves. The processing of events in the 3dUniverse system occurs in an identical manner to the processing of events in a 3DAtom system. The recursive nature of this means that events can be designed and programmed (relatively) independently of other systems, with a minimum of effort and executed flawlessly in most cases. It also means that processing of events in a 3dSystem naturally occurs in an abstraction hierarchy without any effort from a developer..

The following is a narrative that explains how events work in a 3dSystem:

1. Events only occur in a 3dStar (e.g. sun system in a solar system) type of system (because a 3dStar system contains the state of the main 3dSystem (i.e. solar system in our example))

2. An event raised in the 3dStar System is handled by an Event Handler (a standard Visual Basic function) method in the Parent 3dSystem (the solar system in our example)

3. This method will typically:

   a. raise the event further, thus making it available in the parent system of the outer/main system (a galaxy system in the case of the a solar system), and/or
   b. do some other processing with the main system (solar system) or in another referenced system.

Case 3a is the means by which a subsystem (or referenced system e.g. the earth system in the case of the solar system) communicates with its parent system. In this case, the parent (the solar system in our example) will typically change the state of the 3dStar system (the sun in our example) based on the nature of the event from the subsystem. The same may be true of reality. There is a lot of evidence that a photon does not contain energy (e.g. it is not affected by gravity). Changing the state of a system does not not necessarily involve energy. A system can change state based on the frequency of a photon only. 

Events in 3dSystems are types of 3dSystems but with no capabilities to change state. They correspond to bosons in Reality. A boson is basically the amount a system has changed state by at some time in the past. Photons in a 3dSystem will be raised from system to system until one system accepts and processes the photon. Other bosons will be reabsorbed by the emitting 3dStar object (I am guessing). I.e bosons/events can only travel upwards in an abstraction hierarchy (travelling down is done via method calls and I am not sure how Reality achieves this).

Code for these actions was supplied in my previous post.

 

[Bored chemist]

IMHO I think ...

What does the H stand for?

Are you going to answer this?

[mxplxxx (OP)]

Here is the latest on a photon from a 3dAbstractions perspective

3dPhotons provide information to 3dSystems about the energy involved in collisions.

3dPhoton System
   
    3dPhoton Ion (a _3dStar/central System)
   

Code: [Select]

        WhenHappened as DateTime
WhereHappened as Double
Spin as integer
        Frequency as Double ' frequency of photon's Spin

    Subsystems

        E Gymbal
        M Gymbal
   
    Gymbals provide stability to the photon as per a gyroscope.

For example, two fermion systems A and B of energy EA and EB respectively collide. The resulting two systems A and B have energy EX and EY respectively where EX + EY = EA + EB. Two 3dPhoton systems, PA and PB, will result from this collision. PA will have (from E = hf) frequency (EX - EA)/h. Neither 3dPhoton system contains any energy. A system that processes photon PA will recognize (via E = hf) that system A has lost/gained EX - EA amount of energy in the collision.

That is, a 3dPhoton contains information about the result of a collision, but no energy from the collision (thus answering the question posed by the topic). As per the conservation of energy, all of the energy involved in the collision stays with the two fermion systems involved. Energy and Time are closely related. No Time: No Energy. Because it travels at SOL, a photon does not experience time. It exists in an eternal present (ditto for all bosons). It is likely a Photon is a boson that is adapted for long distance travel with maximum stability (although as "shifts" (i.e. changes in frequency) show,  perfect stability/integrity of information is not attainable). The universe loses information (a boson function ) over time but not energy (a fermion function).

Energy changes momentum, Frequency changes State. Energy is not required to change State. Frequency is an attribute of Spin, an entity in Physics that appears to be conceptual (versus "real") in nature only.     

[Bored chemist]

That is, a 3dPhoton contains information about the result of a collision, but no energy from the collision.

A thing with no energy is not a photon.

[mxplxxx (OP)]

State in the central (_3dStar) system of a computer App is mostly implemented by straight-forward computer programming constructs; properties, method (function) calls and event declarations/handlers. For example, in the case of a Door object, a Closed Boolean plus an Open event. In more complex cases, Hierarchical Finite State Machines (HFSM) are used. The EFTPOS pinpad superstate diagram with this post is an example of a HFSM.

The _3dState system is a type of _3dSystem that is a means of implementing a HFSM. It is basically a _3dSystem with SubStates substituted for SubSystems. SubStates are concurrent states. Below is the basics the pinpad HFSM.

Code: [Select]

Pinpad.System
    inherits _3dSystem

    PinPad.Star
        inherits _3dStar

        Pinpad.HFSM
            Inherits _3dState
 
            Property PinpadState as string (e.g. "Existing")

            Property PinpadSubStates as sortedlist(of string, string) (e.g. Test/Production, Active/Inactive)
A pinpad actually does not have a central system. This is similar to reality where the centre of a system is a black hole. I am assuming the overall state of a system with  a black hole resides in the black hole itself.

A state in a computer system is actually a Name ; i.e. a string; i.e. a series of elementary 0/1's (digits). The same seems true in Reality where a state is likely to be a series of elementary fermions (.e.g. quarks). So, events (bosons) interact with state (fermions) to give new states.

State is a necessary part of Reality which is infinite in nature (think Zeno's paradox). Systems in Reality are timestamped with the time of the next state change which is an infinite number. In this way, State changes  proceed infinitely quickly (SOL is a limitation of Reality), a state change at a time and state changes are timeless i.e. occur immediately. A digital computer works similarly. State turns an infinite number of points into something "real" (and manageable). In fact, a major part of computer software design is managing possibilities via assigning groups of them to a state.

Of course, State and Time are intimately related. It is impossible to perceive time as passing unless state changes are taking place. A _3dState System can progress a State through Time starting at the top superstate level. More on this later; it is intimately related to how Realty works.

PS. State is really, really hard to get clued up on. It took me many years in computer science to gain clarity around it.   

[mxplxxx (OP)]

A _3dSystem implements what is called in computer science a Model View Controller Persistence (MVCP) pattern. A pattern is a way of computing that is best practice.

In a _3dSystem, a MVCP is implemented as follows:

1. Model

   This is the database that a system implements. It consists of the a _3dStar (Central/Inner system) and Subsystems.

2. View.

   This is the visible part of the system. It consists of a a partial Class that inherits a UserControl. A UserControl is a canvas on which other controls (such as a Button) can be displayed.

3. Controller.

    This is the part of a system that controls the flow of Data between the Model, View and Persistence parts. In a _3dSystem it is the the system itself that is the Controller.

4. Persistence

    This is the part of a system that records the past history of the system (i.e. its memory). A special system, _3dDataStore, handles this aspect of the system. 

In a _3dApp, top level systems Display, Data and Datastore are specialist View, Model and Persistence _3dSystems. The Display system is the top level for screen output. The Data system is the top level for the App's in-memory Database. The Datastore system is the top level for the App's permanent memory. 

Does Reality implement the MVCP pattern? Possibly. It would seem that bosons interacting with a system provide a means to make the past "visible", thus implementing a View. The Model is the hierarchy of systems and central systems that make up the universe. The controller is the outer level of these systems (e.g. a solar system). What we don't know is how/where persistence happens. It may be that the mysterious dark matter is where persistence happens or it may be that persistence happens only in very intelligent systems, like our brain.

Missing from this picture is the future. Maybe we could add a Possibilities part to the MVCP pattern for Quantum Computing?  Hierarchical Finite State Machines (HFSMs) contain all possible states of a System. The Substates in a  _3dState HFSM are a mix of possible and real (concurrent) states with the 3dState system programmed to choose between them when an appropriate event is received/occurs. This is the way 3d Abstractions implements Quantum Probabilities. The vast amount of possibilities present in a system are handled/reduced in computer programs by the judicious choice of abstractions when designing the program. Note that this use of abstractions will introduce a degree of UNCERTAINTY into the computation. Something that would have made Heisenberg smile, I am sure

In fact, the only way to live in a universe of a near-infinite number of points is via abstraction and living with the uncertainty thus caused. We, humans, live at a certain level of abstraction in Reality and thus have to deal with a fair amount of uncertainty. Our cells are programmed to do so but mistakes happen and eventually an accumulation of mistakes likely causes our death. 

[mxplxxx (OP)]

It would seem that bosons interacting with a system provide a means to make the past "visible"

According to current physics theory, a photon travels at a constant speed of SOL. It may be more logical to think of a photon as stationary (its gyroscopic nature will keep it that way) and the 3dSystem that the photon is part of as travelling at SOL relative to it (this is the rate at which the present passes). A stationary photon is timeless. A 3dSystem ages. A stationary photon's location also identifies where the event happened that caused the photon's current state.

A stationary photon can enable multiple viewers to "see" an event. This is in contrast to the current theory that has the photon destroyed by the viewing process. This aligns more closely with computer science where a single event can have multiple viewers ("handlers").

It is more than possible that the universe is a "sea" of photons that give a picture of how the energy distribution of the universe has changed over time. This way, photons do not need to be created (much like the digits in a digital computer). In fact, because bosons can coexist (as per Pauli Exclusion principle), it may be possible, that photons can be stacked, one on top of the other. This fascinating possibility may allow the past to be recreated. 3d Abstractions software minimizes dependencies amongst 3dSystems by creating data from the past states of the systems as necessary, rather than maintaining the new state of a system into the future. Could Reality be operating this way? Very likely in my opinion, maybe even from the start of time given Reality never appears to "crash". If so, it is very likely that fermions are conceptual only in nature and created temporarily as necessary - from "nothing".

This mechanism is consistent with my postulate that bosons are about State and fermions are about Motion/Time.

If a 3dSystem moves at SOL relative to a photon, then it will possibly do so in "leaps" that are SOL/t in length where t is time as per E=h/t and E is the energy of the system. Relativity may come into this picture but I am not too sure how at present. See also Zeno's paradox that makes continuous motion unlikely.

[mxplxxx (OP)]

It is possible a photon is a "shadow" of the 3dSystem it represents. That  makes a photon generated by a 3dSystem the same size as the system which means it can easily interact with the 3dSystem's parent and siblings. It is consistent with my theory that 3dSystems are scaled-down versions of their parents. 

Actually, a "shadow" system would be a 3dSystem in its own right but contain a 3dCentralSystem that is the "shadow" of a real 3dSystem. e.g. a Photon.System would be a normal 3dSystem with 3dGymbal subsystems as previously discussed but would contain a "shadow" 3dStar system that represents the system that created the photon.

e.g a photon created by the sun would have the following structure:

3dShadow
    inherits 3dStar

Photon
    System
        inherits 3dSystem
       
       property Star as Star (created via Sun.Star)

       property Subsystems as sorted list of 3dSystem
            E_Gymbal
            M_Gymbal

    Star
         inherits 3dShadow
               
A photon going from one 3dSystem to another would have to be scaled-up/down is some way, probably at the system boundary. Actually, the 3dSystem goes (moves) rather than the photon and chances are the photon will be too small or too large to be even noticed by the 3dSystem, or the photon will not be a type that the 3dSystem is interested in.

This also gives rise to an interesting possible that a fermion is just a "real" photon.

w and z bosons will also have "shadows" . Note that a Higgs boson fits neatly into this scheme and will occupy the same space as its parent system.

If, as suggested in a previous post (https://www.thenakedscientists.com/forum/index.php?topic=75960.msg601611#msg601611) photons are absolute/stationary and can be stacked one on top of the other, the "shadow" aspect of a photon can allow space/time to exist and even allow time travel if photons can exist as possibilities.

[Bobolink]

I was wondering how in the world is this thread still active?  Now I see it is that it is just mxplxxx talking to himself.  Mystery solved.

[mxplxxx (OP)]

As discussed recently, Photons and other bosons "live" in the present. Photons contain information about the past, but live in the present. What else "lives" in the present? Nothing I suspect except space itself (which is timeless). Fermions "travel" at a constant SOL meaning they are never stationary - a precursor for being present it would seem. A fermion encountering a photon that will cause it to change state will do so instantaneously - this feature of state in reality.

So, it would seem, all things being equal, we never really "exist". An interesting thought! Maybe quantum possibilities are necessary for Reality to come into existence.           

[Bobolink]

As discussed recently, Photons and other bosons "live" in the present. Photons contain information about the past, but live in the present. What else "lives" in the present? Nothing I suspect except space itself (which is timeless). Fermions "travel" at a constant SOL meaning they are never stationary - a precursor for being present it would seem. A fermion encountering a photon that will cause it to change state will do so instantaneously - this feature of state in reality.

So, it would seem we never really "exist". An interesting thought! 

Have you been eating wild mushrooms?  I think you might have accidentally gotten a hold of psilocybin.
I live in the present, heck I even have information from the past.

[mxplxxx (OP)]

I live in the present

Yet everything you experience is a past event. If you do live in the present, what and how long is the present?  We don't have an answer to that, so how can you be so sure you live in the present? Chances are you experiencing something initially in your short-term memory, in which case you are experiencing the past. Maybe your awareness is in the present but, given we don't know what awareness is, this statement is pretty meaningless anyway.

[Bobolink]

I live in the present

Yet everything you experience is a past event. If you do live in the present, what and how long is the present?  We don't have an answer to that, so how can you be so sure you live in the present? Chances are you experiencing something initially in your short-term memory, in which case you are experiencing the past. Maybe your awareness is in the present but, given we don't know what awareness is, this statement is pretty meaningless anyway.

So in other words quantum fluctuations harmonizing in resonance with Hilbert space result in a Alexander Hamiltonian.  Hey, I can write gibberish like you!
Bye-bye...

[mxplxxx (OP)]

quantum fluctuations harmonizing in resonance with Hilbert space

Rigged Hilbert Space Resonances and Time Asymmetric Quantum Mechanics https://arxiv.org/abs/quant-ph/9909081
If you don't have the domain knowledge, you will likely regard discussions about the domain as gibberish. Or, as Crocodile Dundee would say, jibber-jabber.