[alancalverd]

Has the Universe been generated via a computer Inheritance Hierarchy?

Highly likely.

Congratulations on inventing something even more absurd than God.

[hamdani yusuf]

Has the Universe been generated via a computer Inheritance Hierarchy?

Highly likely.

What generated the computer?

[mxplxxx (OP)]

Has the Universe been generated via a computer Inheritance Hierarchy?

Highly likely.

What generated the computer?

No idea! Most Likely it has always been there. Chances are the question cannot be asked and the answer, if there is any, would not make any sense to the current reality.

[hamdani yusuf]

Occam's razor tells us not to make assumptions unnecessarily. Instead of saying that universe works like a computer, it's better to say that computers work like the universe, since it's already there before humans invented computer.

[alancalverd]

I sometimes think that "The Matrix" has done as much harm to rational thought as 2000 years of Papal authority.

[mxplxxx (OP)]

Has the Universe been generated via a computer Inheritance Hierarchy?

Highly likely.

Congratulations on inventing something even more absurd than God.

Me!. I am the only system in the universe that I am sure exists. Ergo, I Could be God. Heavens to Betsy, I deserve to be.

[hamdani yusuf]

Has the Universe been generated via a computer Inheritance Hierarchy?

Highly likely.

Congratulations on inventing something even more absurd than God.

Me!. I am the only system in the universe that I am sure exists. Ergo, I Could be God. Heavens to Betsy, I deserve to be.

You can only be sure about your own existence while you are thinking about it. You can't be sure about your own past nor future existence. You need to infer from your experience, which sometimes contain false information.

[mxplxxx (OP)]

You can't be sure about your own past nor future existence.

Unless there is no past nor future; just an eternally present state machine which contains me as a substate. In this case, consciousness is just a state in the me substate.

[hamdani yusuf]

You can't be sure about your own past nor future existence.

Unless there is no past nor future; just an eternally present state machine which contains me as a substate. In this case, consciousness is just a state in the me substate.

If that's the case, your memory would be useless. You can't use causality either to make decisions.

[mxplxxx (OP)]

You can't be sure about your own past nor future existence.

Unless there is no past nor future; just an eternally present state machine which contains me as a substate. In this case, consciousness is just a state in the me substate.

If that's the case, your memory would be useless. You can't use causality either to make decisions.

A state machine contains all possible states of a system. i.e. all possible futures and pasts of the system.

[hamdani yusuf]

A state machine contains all possible states of a system. i.e. all possible futures and pasts of the system.

How do you distinguish the between the possible states and actual states?

[mxplxxx (OP)]

A state machine contains all possible states of a system. i.e. all possible futures and pasts of the system.

How do you distinguish the between the possible states and actual states?

Not sure; I haven't actually programmed this. There would be very likely be Future and Past Substates.

4dAbstractions deals in HFSMs. The central ("Star") system is the functional/state part of a 4d System. It contains a State property, which is a type of State.System, which is a type of HFSM.

In Reality, the Sun of a Solar.System may be a HFSM. Reality in fact may be just a HFSM, in which case things don't move, they just change state.  Makes a lot of sense.

[mxplxxx (OP)]

A state machine contains all possible states of a system. i.e. all possible futures and pasts of the system.

How do you distinguish the between the possible states and actual states?

This is just a basic function of a HFSM. It is difficult to explain. There are States, and Substates, and Superstates and Concurrent States, and Transitions, and the Events that cause transitions, and transition Handler functions and much, much more. It takes decades to be able to fully appreciate HFSMs; how they work and what sort of problems they can solve.

[mxplxxx (OP)]

The creation of a 4dAbstractions protein continues apace. The structures involved have been defined. Here is the code for a Leucine Amino Acid.  Ridiculously simple as it turned out. Probably ditto for Reality.

Code: [Select]

Namespace AminoAcid
    Namespace Leucine

        ' contains classes relating to a Leucine Amino Acid

        Public Class System

            Inherits _4dLibrary.System

            ' create a blank Leucine system

           Public Sub New()

               MyBase.New()

           End Sub

            ' create a new Leucine system

            Public Sub New(T)

                MyBase.New(Type:=eSystemTypes.LEUCINE, SubType:=eSystemSubTypes.DATA, Star:=New Star, SubSystems:=New SubSystems)

               ' add groups

                Me.AddSubSystem(SubSystem:=New AminoGroup.System())
                Me.AddSubSystem(SubSystem:=New Hydrogen.System())
                Me.AddSubSystem(SubSystem:=New CarboxylGroup.System())
                Me.AddSubSystem(SubSystem:=New SideChain.System())

                ' add carbon System

                Me.Star.Star = New Carbon.System(AminoGroup:=AminoGroup, Hydrogen:=Hydrogen, CarboxylGroup:=CarboxylGroup, SideChain:=SideChain)

               End Sub


[mxplxxx (OP)]

Here is an excerpt for the 4dAbstractions simulation of the central carbon system/atom of a Leucine Amino Acid. This is common code that is applicable to all Amino Acids. In 4dAbstractions Carbon electrons do not bond to Groups. Rather they (VB) reference them (entanglement in Reality).

In a massive sleight of hand 😎, the same code, except for "Leucine Namespace", can be used to create any Amino Acid. In 4dbstractions this is done via T4 Text Templates.

Not sure whether Protons and/or Neurons are needed in this design. If so, then they can be added via Star.Star for Protons and Star.Star.Star for Neutrons.

Code: [Select]


Namespace AminoAcid
    Namespace Leucine
        Namespace Carbon

            Public Class System

                Inherits _4dLibrary.SuperSystem

                Public Sub New()

                    MyBase.New()

                End Sub

                Public Sub New(
                    AminoGroup As AminoAcid.AminoGroup.System,
                    Hydrogen As AminoAcid.Hydrogen.System,
                    CarboxylGroup As AminoAcid.CarboxylGroup.System,
                    SideChain As Carbon.SideChain.System
                )

                    ' create a basic 4d supersystem (a 4d System with shells)

                    MyBase.New(Type:=eSystemTypes.CARBON, SubType:=eSystemSubTypes.DATA, Star:=New Star(Id:="Carbon", Name:="Carbon"), Subsystems:=New SubSystems, Shells:=3)

                    ' add electrons (Shell(0) is Carbon.Star)

                    With Me.getShell(1)
                        .AddSubSystem(SubSystem:=New Carbon.Electron1.System())
                        .AddSubSystem(SubSystem:=New Carbon.Electron2.System())
                    End With

                    With Me.getShell(2)
                        .AddSubSystem(SubSystem:=New Carbon.Electron3.System(AminoGroup:=AminoGroup))
                        .AddSubSystem(SubSystem:=New Carbon.Electron4.System(Hydrogen:=Hydrogen))
                        .AddSubSystem(SubSystem:=New Carbon.Electron5.System(CarboxylGroup:=CarboxylGroup))
                        .AddSubSystem(SubSystem:=New Carbon.Electron6.System(SideChain:=SideChain))
                    End With

                    ' create electron abstraction hierarchy with me.Star at top (COOL)

                    With Me.Star
                        .AddSubSystem(SubSystem:=Me.Electron1)
                        .AddSubSystem(SubSystem:=Me.Electron2)
                    End With

                    With Me.Electron1
                        .AddSubSystem(SubSystem:=Me.Electron3)
                        .AddSubSystem(SubSystem:=Me.Electron4)
                    End With

                    With Me.Electron2
                        .AddSubSystem(SubSystem:=Me.Electron5)
                        .AddSubSystem(SubSystem:=Me.Electron6)
                    End With

                End Sub

                Public Shadows Star As Carbon.Star = MyBase.Star
                Public Shadows SubSystems As Carbon.SubSystems = MyBase.Subsystems

                ' Electron access via Subsystems

                Public ReadOnly Electron1 As Electron1.System = Me.getShell(1).SubSystems(System.getSystemName(eSystemTypes.ELECTRON1))
                Public ReadOnly Electron2 As Electron2.System = Me.getShell(1).SubSystems(System.getSystemName(eSystemTypes.ELECTRON2))
                Public ReadOnly Electron3 As Electron3.System = Me.getShell(2).SubSystems(System.getSystemName(eSystemTypes.ELECTRON3))
                Public ReadOnly Electron4 As Electron4.System = Me.getShell(2).SubSystems(System.getSystemName(eSystemTypes.ELECTRON4))
                Public ReadOnly Electron5 As Electron5.System = Me.getShell(2).SubSystems(System.getSystemName(eSystemTypes.ELECTRON5))
                Public ReadOnly Electron6 As Electron6.System = Me.getShell(2).SubSystems(System.getSystemName(eSystemTypes.ELECTRON6))

            End Class


[mxplxxx (OP)]

In 4dAbstractions, a Carbon atom has 3 shells. Shell(0), the central shell, contains a Carbon. Star.  Shell(1) contains electrons 1 & 2. Shell(2) contains Electrons 3,4,6 and 6. Carbon.Star contains Protons in a similar configuration. Carbon.Star.Star contains Neutrons in a similar configuration. There is no need for Repulsion/Attraction in this design!!!

In this design, protons act in a similar way to electrons but on "positive" systems (whatever that means!).

It is becoming more and more likely (imho opinion😎) that the complexities of Physics have mainly come about because Reality is a Computer System.

[Bored chemist]

What predictions does your model make about Leucine ?

[mxplxxx (OP)]

What predictions does your model make about Leucine ?

None. I am still working on the structure of a protein. I will be lucky to finish it this year. Next comes state/function. This will take some doing.

Of course, the structure is the most important aspect of designing a computer system. Once you have a structure, functions, states, events and data flows follow naturally.

e.g. 1. In 4dAbstractions, a 4d Enzyme is a type of 4d system consisting of an abstraction hierarchy of Amino Acids with the Active Amino Acid being contained by the central Enzyme.Star. The Substrate (the system to be sped up) is a 4d System that contains a 4d Enzyme in Substrate.Star.Star.  This is a very common pattern in both Reality and 4dAbstractions.

 e.g. 2. In Carbon.Star, a "Balanced" event from Electron1/AminoGroup can be easily handled as follows:

Code: [Select]


                ' handle events from Electrons 1 & 2

                Private Function _Balanced1() As Boolean Handles Electron1.Balanced

                    State = "Balanced"

                    RaiseEvent Balanced()

                    Return True

                End Function
e.g.3. Here is the structure of Methane according to 4dAbstractions. https://1drv.ms/i/s!AkkAzGDByUeBqrhy2jyg7y5B18axqg?e=B0setv

The point being that the basic structure of all 4dAbstraction Systems is such that all constructs of Reality can be accommodated, and functions can concentrate on the functions themselves.

[mxplxxx (OP)]

Here is an excerpt of the 3d code used by the Electron3.Star class in 4dProtein to communicate with the AminoGroup class. With this code, a 3d version of Electron3 can roam anywhere it likes and still be able to communicate with the 2d version. Sort of like how entanglement would possibly work in Reality.

Code: [Select]

                ' Electron3.Star

                <Serializable()>
                Public Class Star

                    Inherits _4dLibrary.Star

                    Public Event Initialised()

                    Property No As Integer
                    Property Name As String

                    Public Sub New()

                        MyBase.New()

                    End Sub

                    Public Sub New(Properties As Properties)

                        MyBase.New(Properties:=Properties)

                    End Sub

                    Public Sub New(No As Integer)

                        MyBase.New()

                        No = No
                        Name = System.getSystemName(eSystemTypes.ELECTRON3)

                    End Sub

                    Public WithEvents AminoGroup As AminoGroup.System

                    ' handle an Initialised Event from AminoGroup

                    Private Sub _Initialised() Handles AminoGroup.Initialised

                        RaiseEvent Initialised()

                    End Sub

                    Public Overrides Function getId() As String

                        Return System.getSystemName(Me.Type) & " " & getKey()

                    End Function

                    Public Overrides Function getKey() As String

                        Return Me.No.ToString() & Me.KeyQualifier

                    End Function

                End Class




[mxplxxx (OP)]

A 4dParticle (like 4dCarbon) contains a central 4dStar which is the top of an abstraction hierarchy of electrons.  The center of this 4dStar also contains another very similar 4dStar which processes Protons. And the centre of the latter 4Star contains yet another 4Star which processes Neutrons. All of these 4Stars are very alike. The three 4Stars form an abstraction hierarchy in their own right. With Neutrons at the top (most abstract) and Electrons at the bottom (Most concrete).  So, Electrons don't know about Protons and Protons don't know about Neutrons. Which means that each type of 4dStar can mostly exist in solitary mode.  Hence Ions.