[Bored chemist]

And again.

And again.

And again...

Once again...

The fact that you can't measure a Photon directly seems to be a good indicator that there is something to my theory.

What can you measure "directly"?
For example, how do I measure an electric current "directly"?

Are you unable to tell us what you think you are talking about?

[alancalverd]

From Copilot AI; "Yes, ?alancalverd? and ?Bored chemist? are the same person on the Naked Science Forum."

Hilarious. Or are we somehow entangled?

Try asking your copilot whether we are the same person as Hamdani Yusef. If the answer is yes, then you have demonstrated entanglement  not just across 100 miles but over several time zones!

And would you fly with such a copilot?

[Bored chemist]

I couldn't resist it...

Hamdani Yusef and Alan Calverd are not the same person. Let me provide some context:

Yusuf Hamadani (Abū Yaʿqūb Yūsuf al-Hamadānī) was a Persian Sufi who lived during the Middle Ages. He is known for his spiritual teachings and as the first teacher of the Khwajagan in the Naqshbandi order.
Alan Calverd, on the other hand, is a British physicist and science writer. He has written extensively on topics related to physics, mathematics, and science communication.

[Bored chemist]

Incidentally, this isn't me.
https://www.youtube.com/@theboredchemist3655

[mxplxxx (OP)]

Hilarious. Or are we somehow entangled?

Maybe. You both whinge frequently and similarly. And your initials are AC and BC. And there is also the "Good Cop" "Bad Cop" technique which is evident in your posts.

AC, BC, CC (KK) and PC; all Bored Chemist? HHU.

[alancalverd]

Yusuf Hamadani (Abū Yaʿqūb Yūsuf al-Hamadānī) was a Persian Sufi who lived during the Middle Ages.

Entanglement across many, many time zones.

Oddly, there is another Alan Calverd who works in a related field but is much younger and not a blood relative.

The real test of Copilot is how many John Smiths it can get into one pair of trousers.

[alancalverd]

And your initials are AC and BC.

I rather think that BC is a pseudonym. My name was a typing error by the War Ministry.   

[Bored chemist]

You both whinge frequently and similarly

Yes; but I'm the one who is right.

[alancalverd]

And I don't whinge.

[mxplxxx (OP)]

The Sun is the most abstract part of a Solar System. It contains its own Abstraction Hierarchy with a Star at its centre that is a molten (VERY abstract!) core. In 4dAbstractions, a Star is the central subsystem of a 4d System. A 4d Star contains a Star and that Star contain a Star etc. etc. to infinity.  As these scientists are finding out. https://1drv.ms/b/s!AkkAzGDByUeBqJ5uFUJta6yLaxl_wQ?e=4hDZYa

The doughnut mentioned in the article is a core that sits at a particular level of abstraction in the abstraction hierarchy internal to the sun.

[mxplxxx (OP)]

The Periodic Table is an Inherits hierarchy in disguise. Lithium inherits Helium inherits Hydrogen etc. etc... Backs up my theory that everything in reality is a type of Hydrogen atom.

Also corresponds to the binary nature of the universe, where each element is related to a single base element.

IF electron shells were abstraction hierarchies, shells would go 1, 2 ,4 ,8, 16, 32 etc. etc... electrons and in this configuration, carbon would have 3 full shells of electrons. making it very stable and useful for organic molecules.

In 4dabstractons shell 1 would hold a different type of electron which would contain the state of the electron abstraction hierarchy., leaving carbon with a full shell 3 and the ability to form 4 covalent bonds with e.g. amino acid groups. Electrons 1 and 2 would be more abstract than electrons 3,4,5,6. and processes electron events.

It is interesting in 4dProtein, the top electron is actually a 4dStar (central System) that contains the Carbon Ion and therefore protons, which are squashed up and slow compared to the Carbon electrons which whirl around quickly, far apart near the edge of the carbon atom/system and thus electrons could be energetic protons with opposite charges.

There are also properties according to related elements and Periods and Groups that will come into it. I am learning how these poperies relate to particular elements according to their atomic number.

The Og element is going to inherit possibly thousands of properties from all the elements in the periodic table. No wonder it is "Heavy"!

No wonder also that the heavier elements  are so unstable!

The massive number of properties and events happening in Og due to inheritance would make it a difficult element to program and control!

Difficult but maybe not so hard to program given Og interacts only with Ts and the interaction possibly automatically traverses the whole periodic table one element at a time.

An abstraction hierarchy derived from the Periodic Table will be so revelatory, I am sure.

[paul cotter]

What a load of irrelevant rubbish, completely devoid of any coherent meaning. Where do we get them from?

[alancalverd]

theory that everything in reality is a type of Hydrogen atom.

I just came across this nugget of drivel.

Oddly, it  occurred to me a few hours earlier (whilst driving to work this morning) that it is not possible for heavy elements to be analogues of hydrogen!

Funny how once can accept a fact for about 70 years without wondering why it is true, and the moment you look at it, the answer is obvious.

[mxplxxx (OP)]

Lithium inherits Helium inherits Hydrogen etc. etc...

Taking this further, Og inherits Ts inherits Lv .... inherits Lithium inherits Helium inherits Hydrogen. ie. Og is a type of Hydrogen atom.

In computer science, if Class A inherits Class B, then I can reference Class A without any knowledge of Class B yet still interact with Property X of Class B. So, in Class Og I can reference the Inherited Hydrogen atom (at the base of a 118-occurrence inheritance chain) as Proton (0).

[Bored chemist]

Lithium inherits Helium inherits Hydrogen etc. etc...

Taking this further, Og inherits Ts inherits Lv .... inherits Lithium inherits Helium inherits Hydrogen. ie. Og is a type of Hydrogen atom.

In computer science, if Class A inherits Class B, then I can reference Class A without any knowledge of Class B yet still interact with Property X of Class B. So, in Class Og I can reference the Inherited Hydrogen atom (at the base of a 118-occurrence inheritance chain) as Proton (0).

At best this is counting the angels on the head of a pin.

[alancalverd]

I can reference the Inherited Hydrogen atom (at the base of a 118-occurrence inheritance chain) as Proton (0).

...and you will get a wrong answer because you have ignored some very basic (primary school) physics.

[mxplxxx (OP)]

 A Proton in VB.NET. Reality sure as hell makes it easy to simulate itself!!!

Code: [Select]

Module Module1

    Sub Main()

        ' Example of creating a new Proton
        Dim proton As New Proton()

        ' Checking the properties of the proton
        Console.WriteLine($"Proton Charge: {proton.Charge}")
        Console.WriteLine($"Proton Spin: {proton.Spin}")
        Console.WriteLine($"Proton Mass: {proton.Mass}")

    End Sub

End Module


' Define the Particle class
Public Class Particle
    Public Property IsHadron As Boolean
    Public Property Charge As Double
    Public Property Spin As Double
    Public Property Mass As Double

    Public Sub New(Optional isHadron As Boolean = False, Optional charge As Double = 0.0, Optional spin As Double = 0.0, Optional mass As Double = 0.0)
        Me.IsHadron = isHadron
        Me.Charge = charge
        Me.Spin = spin
        Me.Mass = mass
    End Sub
End Class

' Define the Quark class that inherits from Particle
Public Class Quark
    Inherits Particle
    Public Property Type As String

    Public Sub New(type As String, charge As Double, mass As Double)
        MyBase.New(False, charge, 1 / 2, mass)  ' Example spin value for a quark
        Me.Type = type
    End Sub
End Class

' Define specific quark types
Public Class UpQuark
    Inherits Quark

    Public Sub New()
        MyBase.New("Up", 2 / 3, 0.0022)  ' Example mass in GeV/c^2
    End Sub
End Class

Public Class DownQuark
    Inherits Quark

    Public Sub New()
        MyBase.New("Down", -1 / 3, 0.0047)  ' Example mass in GeV/c^2
    End Sub
End Class

' Define the Fermion class
Public Class Fermion
    Inherits Particle

    Public Sub New(Optional isHadron As Boolean = False, Optional charge As Double = 0.0, Optional spin As Double = 0.0, Optional mass As Double = 0.0)
        MyBase.New(isHadron, charge, spin, mass)
    End Sub
End Class

' Define the Baryon class that inherits from Fermion
Public Class Baryon
    Inherits Fermion
    Public Property Quarks As List(Of Quark)

    Public Sub New()
        MyBase.New(True)
        Quarks = New List(Of Quark)()  ' Initialize empty list of quarks
    End Sub
End Class

' Define the Proton class that inherits from Baryon
Public Class Proton
    Inherits Baryon

    Public Sub New()
        MyBase.New()
        Quarks.Add(New UpQuark())
        Quarks.Add(New UpQuark())
        Quarks.Add(New DownQuark())

        ' Calculate total charge, spin, and mass
        Me.Charge = Quarks.Sum(Function(q) q.Charge)
        Me.Spin = 1 / 2  ' Example spin for proton
        Me.Mass = Quarks.Sum(Function(q) q.Mass)  ' Simplified calculation; real mass is complex due to binding energy, etc.
    End Sub
End Class


In this structure:

Particle includes the properties Charge, Spin, Mass, and IsHadron.

Quark inherits from Particle, and specific quark types (UpQuark and DownQuark) inherit from Quark.

Fermion inherits from Particle.

Baryon inherits from Fermion and contains a list of quarks.

Proton inherits from Baryon, populates its list of quarks, and calculates its charge, spin, and mass.

This setup keeps everything organized within the Particle class while allowing SubAtomic to remain as a namespace.

[mxplxxx (OP)]

Electrons are all about energy/movement (hence they are pure abstractions)  They only exist in conjunction with something "real". Protons are all about state/function.

Electrons form an abstraction hierarchy in conjunction with "real" things. Protons form an HFSM (Hierarchical Finite State Machine) which is basically a type of abstraction hierarchy of State objects. The states involved are that of the System the protons belong to.

So Electrons con be considered to be "Pure" energy and Protons can be considered to be "Pure" State.

So, we have an atom that contains an abstraction hierarchy of Electrons, and at its centre is the nucleus. The nucleus contains an abstraction hierarchy of Protons. So, the two abstraction hierarchies of Energy and State interact to define the behaviour of the atom. The top of the latter abstraction hierarchy is a Neutron which is what remains when the two abstraction hierarchies combine.

[mxplxxx (OP)]

A Proton in VB.NET. Reality sure as hell makes it easy to simulate itself!!!

Code: [Select]

Module Module1

    Sub Main()

        ' Example of creating a new Proton
        Dim proton As New Proton()

        ' Checking the properties of the proton
        Console.WriteLine($"Proton Charge: {proton.Charge}")
        Console.WriteLine($"Proton Spin: {proton.Spin}")
        Console.WriteLine($"Proton Mass: {proton.Mass}")

    End Sub

End Module


' Define the Particle class
Public Class Particle
    Public Property IsHadron As Boolean
    Public Property Charge As Double
    Public Property Spin As Double
    Public Property Mass As Double

    Public Sub New(Optional isHadron As Boolean = False, Optional charge As Double = 0.0, Optional spin As Double = 0.0, Optional mass As Double = 0.0)
        Me.IsHadron = isHadron
        Me.Charge = charge
        Me.Spin = spin
        Me.Mass = mass
    End Sub
End Class

' Define the Quark class that inherits from Particle
Public Class Quark
    Inherits Particle
    Public Property Type As String

    Public Sub New(type As String, charge As Double, mass As Double)
        MyBase.New(False, charge, 1 / 2, mass)  ' Example spin value for a quark
        Me.Type = type
    End Sub
End Class

' Define specific quark types
Public Class UpQuark
    Inherits Quark

    Public Sub New()
        MyBase.New("Up", 2 / 3, 0.0022)  ' Example mass in GeV/c^2
    End Sub
End Class

Public Class DownQuark
    Inherits Quark

    Public Sub New()
        MyBase.New("Down", -1 / 3, 0.0047)  ' Example mass in GeV/c^2
    End Sub
End Class

' Define the Fermion class
Public Class Fermion
    Inherits Particle

    Public Sub New(Optional isHadron As Boolean = False, Optional charge As Double = 0.0, Optional spin As Double = 0.0, Optional mass As Double = 0.0)
        MyBase.New(isHadron, charge, spin, mass)
    End Sub
End Class

' Define the Baryon class that inherits from Fermion
Public Class Baryon
    Inherits Fermion
    Public Property Quarks As List(Of Quark)

    Public Sub New()
        MyBase.New(True)
        Quarks = New List(Of Quark)()  ' Initialize empty list of quarks
    End Sub
End Class

' Define the Proton class that inherits from Baryon
Public Class Proton
    Inherits Baryon

    Public Sub New()
        MyBase.New()
        Quarks.Add(New UpQuark())
        Quarks.Add(New UpQuark())
        Quarks.Add(New DownQuark())

        ' Calculate total charge, spin, and mass
        Me.Charge = Quarks.Sum(Function(q) q.Charge)
        Me.Spin = 1 / 2  ' Example spin for proton
        Me.Mass = Quarks.Sum(Function(q) q.Mass)  ' Simplified calculation; real mass is complex due to binding energy, etc.
    End Sub
End Class


In this structure:

Particle includes the properties Charge, Spin, Mass, and IsHadron.

Quark inherits from Particle, and specific quark types (UpQuark and DownQuark) inherit from Quark.

Fermion inherits from Particle.

Baryon inherits from Fermion and contains a list of quarks.

Proton inherits from Baryon, populates its list of quarks, and calculates its charge, spin, and mass.

This setup keeps everything organized within the Particle class while allowing SubAtomic to remain as a namespace.

Along the same lines here is the VB.NET code for creating a Proton HFSM using only a State class!.

Code: [Select]

Module Module1
    Sub Main()
        ' Create the root state for the proton
        Dim protonState As State = CreateStateHierarchy("Proton", New List(Of String) From {
            "Ground State", "Excited States", "Spin States", "Color States", "Virtual States", "Rescattering States", "Baryon Resonances"
        })

        ' Add substates for Excited States
        Dim excitedStates As State = protonState.GetSubstate("Excited States")
        If excitedStates IsNot Nothing Then
            excitedStates.AddSubstates(New List(Of String) From {"1st Excited State", "2nd Excited State"})
        End If

        ' Add substates for Spin States
        Dim spinStates As State = protonState.GetSubstate("Spin States")
        If spinStates IsNot Nothing Then
            spinStates.AddSubstates(New List(Of String) From {"Spin-Up", "Spin-Down"})
        End If

        ' Add substates for Color States
        Dim colorStates As State = protonState.GetSubstate("Color States")
        If colorStates IsNot Nothing Then
            colorStates.AddSubstates(New List(Of String) From {"Red", "Green", "Blue"})
        End If

        ' Print the state hierarchy
        protonState.PrintStateHierarchy()
    End Sub

    ' Recursive function to create state hierarchy
    Function CreateStateHierarchy(stateName As String, substateNames As List(Of String)) As State
        Dim state As New State(stateName)
        For Each name As String In substateNames
            Dim substate As State = CreateStateHierarchy(name, New List(Of String)())
            state.AddSubstate(substate)
        Next
        Return state
    End Function
End Module

Public Class State
    Private ReadOnly stateName As String
    Private Substates As List(Of State)
    Private CurrentSubstate As State

    Public Sub New(name As String)
        Me.stateName = name
        Me.Substates = New List(Of State)()
    End Sub

    Public Sub AddSubstate(substate As State)
        Me.Substates.Add(substate)
    End Sub

    Public Sub AddSubstates(substateNames As List(Of String))
        For Each name As String In substateNames
            Dim substate As New State(name)
            Me.AddSubstate(substate)
        Next
    End Sub

    Public Function GetSubstate(stateName As String) As State
        Return Me.Substates.Find(Function(s) s.stateName = stateName)
    End Function

    Public Sub SetInitialState(stateName As String)
        Me.CurrentSubstate = Me.GetSubstate(stateName)
        If Me.CurrentSubstate IsNot Nothing Then
            Me.CurrentSubstate.OnEnter()
        End If
    End Sub

    Public Sub TransitionTo(stateName As String)
        If Me.CurrentSubstate IsNot Nothing Then
            Me.CurrentSubstate.OnExit()
        End If

        Me.CurrentSubstate = Me.GetSubstate(stateName)
        If Me.CurrentSubstate IsNot Nothing Then
            Me.CurrentSubstate.OnEnter()
        End If
    End Sub

    Public Sub OnEnter()
        Console.WriteLine($"Entering state: {Me.stateName}")
    End Sub

    Public Sub OnExit()
        Console.WriteLine($"Exiting state: {Me.stateName}")
    End Sub

    Public Sub PrintStateHierarchy(Optional indent As String = "")
        Console.WriteLine($"{indent}{Me.stateName}")
        For Each substate As State In Me.Substates
            substate.PrintStateHierarchy(indent & "  ")
        Next
    End Sub
End Class


[mxplxxx (OP)]

Has the Universe been generated via a computer Inheritance Hierarchy?

Highly likely.

An Inheritance Hierarchy (e.g. Mustang, Ford, Car) starts at the bottom the hierarchy and works its way up, one class at a time. So, the Universe could have started at the bottom of the Universal Inheritance hierarchy as a singularity and expanded, one level (i.e. Shell) at a time, resulting in the current Universe, which is still expanding.

So, the closer we get to the centre of the Universe, the more abstract it becomes and the closer we get to the edge of the Universe, the more concrete it becomes.

So, the universe encloses an Abstraction Hierarchy, and we will exist at a certain level of abstraction because of this. A runtime system is needed to create (instantiate) the abstraction hierarchy from the inheritance hierarchy. So, somewhere there is a computer that is creating/expanding the Universe via an Inheritance Hierarchy.

In 4dProtein, the Leucine Class inherits AminoAcid. Theis enables the derived Class, Leucine, being able to access the Base class, AminoAcid, for common code purposes and the Base class AminoAcid being able to access the Derived Class Leucine for the purpose forming an abstraction hierarchy. The two-class nature of this scheme, if applied to Reality, will give us a binary-structured universe.