Miles Periodic Table with Standard Periodic Table reference

.

Slot Layout (SL) diagrams for atoms 1-14.

Cr6 wrote. Your recent updates look good. I'll reload the Physics database with your updates and more fine tuned layouts.

Airman. Pardon me but that may take a while. Good thing, as usual, slow progress is better than no progress. Haven't read the rest of your post yet.

BT alphas have been added to most all the small atoms up to Silicon. While they are all guesses, which may or may not be accurate representations of charge field atomic matter proton stacks, BT alphas, with their top and bottom low charge field bonding holes, are a big addition compared to single top or bottom holes for constant electron position and constant proton spin stacks, or overlapping holes within TB alpha stacks. I believe I might see how a BT alpha can form a carousel hub. As such, our stack types and bonding rules may now be sufficient to account for all internal atomic structures, allowing all atomic slots to form the SL diagram and hang together. Plus a reminder we still need additional rules, such as angled bonds occurring between atoms.

I’m sure you’ve noticed, the LTAMKey cannot account for all possible stacks. I believe that should be fixed by adding the 1-144 stack number to the LTAMKey code, and include it in the SL diagram.



A 3d view of Si is included in the lower right corner. The neutrons are removed for extra clarity.

I decided not to ‘vary’ the atomic slot assignments. All fourteen atoms shown here are an attempt to identify vertically aligned atoms in the same field, with mostly upwardly directed charge, as on Earth, with top to bottom z-axis vertical slots with alpha types: s14:TL, s4:M, s2:A, s1:P, s3:V, s5:C, s15:BR. As I keep saying, stack variations can be added easily enough.
.

Thanks for displaying these lower formations...LTAM. In the database alignments with this was kind of hit or miss.

.
You're welcome Cr6. I'll try displaying the rest after a two-week summer vacation hold. Maybe it will do me some good.
.

.

My last two week break involved mainly extra chores, catching up on politics, and pleasure reading. I could only spend brief amounts of time just thinking about assigning slots, as in, ‘how exactly do adjacent orthogonal slots follow the right hand rule? Now I’m back at work. Looking over this latest batch of 16 atoms. I should point out it appears that the hook positions (slots 16 -19), cannot properly bound to TB alphas slots two and three. Do slots 2 and 3 also need to be BT alphas??? I thought we had the atoms licked. More work will need to be done.



Molecular humor.

.

LTAM...welcome back! Thanks for your picture updates above. I like the water buffalo pic!  

I've been playing around with Neo4j again. Trying to use your files out on github to load "models" for Nodes-Relationships directly from the files. Might need a bit more notation on a few columns (like descriptions for some of the single or two letter symbols especially "SlotSpin" and "Electrons"). I should just look into the Jupyter notebooks for them.

Here are scripts I'm using now for loading Neo4j Desktop. Looking to add filters for Relationships for allowed bonds: https://neo4j.com/docs/cypher-manual/current/clauses/where/#filter-on-relationship-property

Code:


LOAD CSV WITH HEADERS FROM 'https://raw.githubusercontent.com/LtAirman/ChargeFieldTopics/master/data/Elements-Positions4.csv' as row
MERGE (s:Element {Element:row.Element})
SET s.AtomicSymbol = row.AtomicSymbol,
    s.AtomicType = row.AtomicType,
    s.AtomicNumber = toInteger(row.AtomicNumber),
    s.AtomicPeriod = row.AtomicPeriod


LOAD CSV WITH HEADERS FROM 'https://raw.githubusercontent.com/LtAirman/ChargeFieldTopics/master/data/Elements-Positions4.csv' as row
WITH row
WHERE row.CanBind = 'Y'
MATCH (s:Element {Element:row.Element})
MERGE (slt:SlotNumber {SlotNumber:toInteger(row.SlotNumber)})
SET
slt.CanBindYN = row.CanBind,
slt.CanBind  = toInteger(CASE WHEN row.CanBind = 'Y' THEN 1 ELSE 0 END),
slt.Protons = row.Protons,
slt.Neutrons = row.Neutrons,
slt.PX = row.PX,
slt.PY = row.PY,
slt.PZ = row.PZ,
slt.P2P3 = toFloat(row.P2P3),
slt.P12 =  toFloat(row.P12),
slt.PE =   toFloat(row.PE),
slt.p1x =  toFloat(row.p1x),
slt.p1y =  toFloat(row.p1y),
slt.p1z =  toFloat(row.p1z),
slt.p2x =  toFloat(row.p2x),
slt.p2y =  toFloat(row.p2y),
slt.p2z =  toFloat(row.p2z),
slt.p3x =  toFloat(row.p3x),
slt.p3y =  toFloat(row.p3y),
slt.p3z =  toFloat(row.p3z),
slt.p4x =  toFloat(row.p4x),
slt.p4y =  toFloat(row.p4y),
slt.p4z =  toFloat(row.p4z),
slt.p5x =  toFloat(row.p5x),
slt.p5y =  toFloat(row.p5y),
slt.p5z =  toFloat(row.p5z),
slt.p6x =  toFloat(row.p6x),
slt.p6y =  toFloat(row.p6y),
slt.p6z =  toFloat(row.p6z),
slt.N1N2 = toFloat(row.N1N2),
slt.N1 =   toFloat(row.N1),
slt.N2 =   toFloat(row.N2),
slt.N3 =   toFloat(row.N3),
slt.N4 =   toFloat(row.N4),
slt.N5 =   toFloat(row.N5),
slt.N6 =   toFloat(row.N6),
slt.n1x =  toFloat(row.n1x),
slt.n1y =  toFloat(row.n1y),
slt.n1z =  toFloat(row.n1z),
slt.n2x =  toFloat(row.n2x),
slt.n2y =  toFloat(row.n2y),
slt.n2z =  toFloat(row.n2z),
slt.n3x =  toFloat(row.n3x),
slt.n3y =  toFloat(row.n3y),
slt.n3z =  toFloat(row.n3z),
slt.n4x =  toFloat(row.n4x),
slt.n4y =  toFloat(row.n4y),
slt.n4z =  toFloat(row.n4z),
slt.n5x =  toFloat(row.n5x),
slt.n5y =  toFloat(row.n5y),
slt.n5z =  toFloat(row.n5z),
slt.n6x =  toFloat(row.n6x),
slt.n6y =  toFloat(row.n6y),
slt.n6z =  toFloat(row.n6z),
slt.Electrons = row.Electrons,
slt.e1x = toFloat(row.e1x),
slt.e1y = toFloat(row.e1y),
slt.e1z = toFloat(row.e1z),
slt.e2x = toFloat(row.e2x),
slt.e2y = toFloat(row.e2y),
slt.e2z = toFloat(row.e2z),
slt.e3x = toFloat(row.e3x),
slt.e3y = toFloat(row.e3y),
slt.e3z = toFloat(row.e3z),
slt.e4x = toFloat(row.e4x),
slt.e4y = toFloat(row.e4y),
slt.e4z = toFloat(row.e4z),
slt.e5x = toFloat(row.e5x),
slt.e5y = toFloat(row.e5y),
slt.e5z = toFloat(row.e5z),
slt.e6x = toFloat(row.e6x),
slt.e6y = toFloat(row.e6y),
slt.e6z = toFloat(row.e6z),
slt.SlotOrien = row.SlotOrien,
slt.SlotSpin = row.SlotSpin,
slt.Tcount = row.Tcount,
slt.CanBind = row.CanBind,
slt.StackNum = row.StackNum,
slt.AltStacks = row.AltStacks

MERGE (s) - [:HAS_SLOT {LTAMKey: row.Electrons || row.SlotNumber || row.SlotOrien || row.Protons ||row.SlotSpin, SlotNumber:toInteger(row.SlotNumber), SlotOrientation: row.SlotOrien, Protons: row.Protons, SlotSpin: row.SlotSpin, Electrons: row.Electrons, CanBind: row.CanBind }] -> (slt)



Output:

.
Cr6 wrote. I've been playing around with Neo4j again. Trying to use your files out on github to load "models" for Nodes-Relationships directly from the files.
Airman. If I understand you correctly Cr6, I believe that loading modelss from the files may be the best way forward.

Elements-Positions3.csv contains all the x, y and z coordinate positions for each and every (1-19) occupied slot in any given atom (1-90), as well as all the electron, proton and neutron (epn) positions according to the TRBL configuration data coded for each slot.  

Elements-Positions4 is an improvement in that while it still contains each occupied slots’ center coordinates, it instead identifies every stack’s specific epn locations and TRBL configuration by pointing to a separate file, EPNStacks.csv, containing all possible 1-144 ‘allowed’ slot stacks. Changing the pointer value makes it easy to swap between alternative possible stack types.

In the future, we could increase Elements-Positions4’s flexibility further by having it calculate each slot’s geometric center according to the proton counts within each slot. The program would then be able to plot proper atoms even if the user makes slot assignment changes and/or moves one or more protons from one slot to another within any single atom.  

Unfortunately, I’m only up to Zinc, Atomic Number 30, in my own working copy of Elements-Positions4.csv and I’m far from updating Elements-Positions4.csv at GitHub.

Cr6 wrote. Might need a bit more notation on a few columns (like descriptions for some of the single or two letter symbols especially "SlotSpin" and "Electrons"). I should just look into the Jupyter notebooks for them. 
Airman. Please tell me what additional changes or information you might like to see in order to load database models directly from Elements-Positions4 and EPNStacks.
.

Yeah was just looking for a layman's description of "P" kind of thing.

.
Added """comments""" to your script.

Code:


LOAD CSV WITH HEADERS FROM'https://raw.githubusercontent.com/LtAirman/ChargeFieldTopics/ter/data/Elements-Positions4.csv' as row
MERGE (s:Element {Element:row.Element})
""" Element. col C. 90 Values: ‘Hydrogen’, ‘Helium’, ‘Lithium’, … , ‘Radon’,
‘Actinium’, ‘Thorium’. Used in atomic plot and gui dropdown. """

SET s.AtomicSymbol = row.AtomicSymbol,
""" AtomicSymbol. col B. 90 Values: 'H’, 'He’, ‘Li’, … , ‘Ra’, ‘Ac’, ‘Th’.
Used in SL diagram, atomic plot and gui dropdown. """

 s.AtomicType = row.AtomicType,
""" AtomicType. col E. Value: 'nonmetal', 'noblegas', 'alkalimetal',
'alkalineearth', 'metalloid', 'halogen', 'basicmetal', 'transitionmetal',
'lanthanide', 'actinide'. Used to color each atom in the Periodic table. """

 s.AtomicNumber = toInteger(row.AtomicNumber),
”” AtomicNumber. col A. The selected Element number. Values: 1-90. Used
in SL diagram, gui dropdown and periodic table. """

 s.AtomicPeriod = row.AtomicPeriod,
""" AtomicPeriod. col G. The row of the periodic table in which the
element is found. Values: 1-7. Not used. """

LOAD CSV WITH HEADERS FROM 'https://raw.githubusercontent.com/LtAirman/ChargeFieldTopics/master/data/Elements-Positions4.csv' as row
WITH row
WHERE row.CanBind = 'Y'
""" CanBind. col CD. Values: Y or N. This description is repeated below. All
slots can bind, so, currently, all occupied atomic slot values are Y. With respect
to molecules, the question should be, ‘Can that atomic slot bind with a slot of
another atom? Then only the +/- x, y and z atomic extents as well as hook
positions should be ‘Y’. All the remaining interior atomic slots should be ‘N’.
This needs to be part of my current Elements-Positions4.csv update. """

MATCH (s:Element {Element:row.Element})
MERGE (slt:SlotNumber {SlotNumber:toInteger(row.SlotNumber)})
""" SlotNumber. col H. Values: 1-19. A single row for every occupied atomic slot.
Used in SL diagram, gui dropdown and periodic table. Elements-Positions4.csv
is 90 (elements) times 19 (maximum number of slots) = 1710 rows. """

SET
slt.CanBindYN = row.CanBind,
slt.CanBind = toInteger(CASE WHEN row.CanBind = 'Y' THEN 1 ELSE 0 END),
slt.Protons = row.Protons,
""" Protons. col I. The number of protons (and electrons) for a given slot.
Values: 0-6. Used in SL diagram, gui dropdown and periodic table. """

slt.Neutrons = row.Neutrons,
""" Neutrons. col AH. The number of neutrons for a given slot. Values: 0-6.
Used in SL diagram, gui dropdown and periodic table. """

slt.PX = row.PX,
slt.PY = row.PY,
slt.PZ = row.PZ,
""" PX, PY, PZ. cols J, K, L. The x, y and z coordinate position of that slot
(1-19) with respect to the atomic center (0,0,0), the geometric center of slot1. """

slt.P2P3 = toFloat(row.P2P3),
""" P2P3. Col M. Value 0.3. The distance between adjacent parallel protons within a
slot. """

slt.P12 = toFloat(row.P12),
""" P12. Col N. Value 0.295. The distance between adjacent (orthogonal) protons between
2 slots. """

slt.PE = toFloat(row.PE),
""" PE. Col O. Value 0.0648. The ‘vertical’ and 'horizontal' separation distance between
protons and electrons. PE was a bad variable name choice, with over 321 word count
occurrences. """

""" P12, P2P3, and PE Default values: 0.3, 0.295, and 0.0648. Could be changed
with the gui panel with Elements-Positions3.csv. When using Elements-Positions4.csv,
the program does not yet have that capability. """

""" Cols P thru AG. The following 18 values are the coordinate locations of a
single slot’s up to 6 protons, used in Elements-Positions3.csv. Not intended for
use with Elements-Positions4.csv where those coordinates are found in EPNStacks.csv. """
slt.p1x = toFloat(row.p1x),
slt.p1y = toFloat(row.p1y),
slt.p1z = toFloat(row.p1z),
slt.p2x = toFloat(row.p2x),
slt.p2y = toFloat(row.p2y),
slt.p2z = toFloat(row.p2z),
slt.p3x = toFloat(row.p3x),
slt.p3y = toFloat(row.p3y),
slt.p3z = toFloat(row.p3z),
slt.p4x = toFloat(row.p4x),
slt.p4y = toFloat(row.p4y),
slt.p4z = toFloat(row.p4z),
slt.p5x = toFloat(row.p5x),
slt.p5y = toFloat(row.p5y),
slt.p5z = toFloat(row.p5z),
slt.p6x = toFloat(row.p6x),
slt.p6y = toFloat(row.p6y),
slt.p6z = toFloat(row.p6z),

slt.N1N2 = toFloat(row.N1N2),
""" N1N2, col AI. The ‘horizontal’ separation between two neutrons orbiting
a single proton pole. """

slt.N1 = toFloat(row.N1),
slt.N2 = toFloat(row.N2),
slt.N3 = toFloat(row.N3),
slt.N4 = toFloat(row.N4),
slt.N5 = toFloat(row.N5),
slt.N6 = toFloat(row.N6),
""" ‘N1’, ‘N2’, ‘N3‘, … , ‘N6’. Cols ‘AJ’, ‘AK’, … , ‘AO’. Values: 0, 1 or 2.
The number of neutrons orbiting the first, second, third, … , and sixth proton.
of that stack. P1, P2, … , P6."""

""" Cols ‘AP’, ... , ‘BG’. These 18 values are the coordinate locations
of a single slot’s neutrons, used in Elements-Positions3.csv. Second neutrons orbiting
a single protons’ pole are added opposite (about the z-axis). to the coordinate provided.
Neutrons are not yet coded for Elements-Positions4.csv and EPNStacks.csv. """
slt.n1x = toFloat(row.n1x),
slt.n1y = toFloat(row.n1y),
slt.n1z = toFloat(row.n1z),
slt.n2x = toFloat(row.n2x),
slt.n2y = toFloat(row.n2y),
slt.n2z = toFloat(row.n2z),
slt.n3x = toFloat(row.n3x),
slt.n3y = toFloat(row.n3y),
slt.n3z = toFloat(row.n3z),
slt.n4x = toFloat(row.n4x),
slt.n4y = toFloat(row.n4y),
slt.n4z = toFloat(row.n4z),
slt.n5x = toFloat(row.n5x),
slt.n5y = toFloat(row.n5y),
slt.n5z = toFloat(row.n5z),
slt.n6x = toFloat(row.n6x),
slt.n6y = toFloat(row.n6y),
slt.n6z = toFloat(row.n6z),

slt.Electrons = row.Electrons,
""" Electrons. col BH. Values: T, B, A, V, E, W, M, C, P, Q.
Identifying the given stack’s 1-6 electron positions at their
respective proton’s T or B pole. Coded to indicate either a
constant proton pole position, TB or BT alphas. """

""" Cols ‘BI’, ... , ‘BZ’. These 18 values are the coordinate
locations of a single slot’s up to 6 electrons, used in
Elements-Positions3.csv. For Elements-Positions4.csv use the
electron coordinates found in EPNStacks.csv. """
slt.e1x = toFloat(row.e1x),
slt.e1y = toFloat(row.e1y),
slt.e1z = toFloat(row.e1z),
slt.e2x = toFloat(row.e2x),
slt.e2y = toFloat(row.e2y),
slt.e2z = toFloat(row.e2z),
slt.e3x = toFloat(row.e3x),
slt.e3y = toFloat(row.e3y),
slt.e3z = toFloat(row.e3z),
slt.e4x = toFloat(row.e4x),
slt.e4y = toFloat(row.e4y),
slt.e4z = toFloat(row.e4z),
slt.e5x = toFloat(row.e5x),
slt.e5y = toFloat(row.e5y),
slt.e5z = toFloat(row.e5z),
slt.e6x = toFloat(row.e6x),
slt.e6y = toFloat(row.e6y),
slt.e6z = toFloat(row.e6z),

slt.SlotOrien = row.SlotOrien,
""" SlotOrien. col CA. The selected slot’s single or parallel proton
emission plane. Values: ‘X’, ‘Y’, or ‘Z’. """

slt.SlotSpin = row.SlotSpin,
""" SlotSpin. col CB. Values: L, R, A, V, E, W, M, C, P, Q. Identifying
the given stack’s vertically aligned 1-6 proton spin directions, L or R
given a constant proton spin direction or TB or BT alphas. """

slt.Tcount = row.Tcount,
""" Tcount. col CC. Values: 0-5. Identifying the number of protons in the
top (+z) portion of the TB or BT alpha stack. """

slt.CanBind = row.CanBind,
""" CanBind. col CD. Values: Y or N. This entry is a repeat from
above. All slots can bind, so, currently, all occupied atomic slot values
are Y. With respect to molecules, the question should be, ‘Can that atomic
slot bind with a slot of another atom? Then only the +/- x, y and z atomic
extents as well as hook positions should be ‘Y’. All the remaining interior
atomic slots should be ‘N’. This needs to be part of my current
Elements-Positions4.csv update. """

slt.StackNum = row.StackNum,
""" StackNum. col CE. Values: 1-144. The stack type occupying that atomic slot. """

slt.AltStacks = row.AltStacks

MERGE (s) - [:HAS_SLOT {LTAMKey: row.Electrons || row.SlotNumber || row.SlotOrien ||
row.Protons ||row.SlotSpin, SlotNumber:toInteger(row.SlotNumber),
SlotOrientation: row.SlotOrien, Protons: row.Protons, SlotSpin: row.SlotSpin,
Electrons: row.Electrons, CanBind: row.CanBind }] -> (slt)


Any help?

P.S. I don’t see any likes, so I guess not. Made the following changes.
1. AtomicType. Changed ‘Not used’ to ‘Used to color each atom in the Periodic table’.
2. Added P12, P2P3, and PE Default values.
3. Added """ P12, P2P3, and PE Default values: 0.3, 0.295, and 0.0648. Could be changed with the gui panel with Elements-Positions3.csv. When using Elements-Positions4.csv, the program does not yet have that capability. """
4. Added “PE was a bad variable name choice, with over 321 word count occurrences. """
.

.

Zinc, comprised of 4 single protons – actually an electron/proton or ep set, in slots 14,15,18,19; and 13 BT alphas - two ep sets with bottom and top electron positions in which proton spins may or may not be constant, slots 1-13.  Zn’s slot15 single proton position error present in my 7 August post has been corrected as shown.

Stacks with a constant proton spin and constant electron position result in a single top or bottom electron vacant, low charge field pressure, proton pole sided ‘hole’. TB alphas create a single (dual overlapping) hole in the center of a stack. These two alpha types together are not sufficient to form a proper Slot Layout diagram type configuration. Not counting single ep stacks, it appears all 90 atomic SL diagrams can be formed with BT alpha stacks alone.

As far as adding BT alpha assignments to Elements-Positions4.csv goes, why include any TB or constant spin and constant electron position alpha stacks at all?

Its given me a mental breakdown. Please pardon my even slower than usual progress.

If BT alphas alone are sufficient to create well-structured SL configurations, how do I choose which BT alpha spin directions to use for each slot?

I need to come up with some legitimate means or rationale to identify every slot’s specific BT or single ep spin directions. Sure, upward traveling CCW (viewed from above) charge entering a bottom proton pole as with Zn slot5’s bottom or the bottom proton of slot 1, will cause those protons to spin R, to the right. Downward traveling anti-charge from above will cause Zn’s slot1 top proton to spin L. It seems to me that, when viewed from either the four directions: + or –, x and y directions toward the center of the atom, single protons in slots 6, 7, 8 and 9 will all spin CCW. That would agree with the proton spin directions identified for Zn slots 6-9 ‘innermost’ protons, closest to slot1 shown above.  I then imagine that the outermost protons in slots 6-9 would follow suit, and spin in the same direction as the innermost protons. Also as shown. Next, according to this rationale akin to spinning gears, I might expect that the proton spins of slots 10-13 would be the same as the two spin BT configuration as slot1. If true, the Zn slots shown are wrong and need to be corrected. Single direction BT slots 4 and 5 appear to me to be correct. I’m presently unable to rationalize the resulting spins directions for the single protons in slots 14, 15, which may not matter. The single protons in slots 18 and 19 also seem backward to me, assuming slot 18 is spun primarily by downward anti-charge, and slot 19 is spun mainly by upward charge - but I’m far from certain.

As usual, your patience is appreciated, your comments are welcome.
.

.

Zinc. Second attempt. Here are 13 BT alphas and four single electron proton ep set slot assignments for Zn. My previous post’s spin ‘thoughts’ and Slot Layout diagram were unsatisfactory. I believe this SL is a more accurate and acceptable configuration.

The bottom protons in slots 5, 10, 11, 12, 13 receive upward CCW charge from below; they all spin R.
The top protons in slots 4, 10, 11, 12, 13 receive downward anti-charge from above; they all spin L.
Slots 10, 11, 12, 13 are thus all BLTR, two-spin “P” type BT alphas.
Slot4’s bottom proton will spin in the same direction as the top proton, a BLTL a “M” type BT alpha.  
Slot5’s top proton will spin in the     same direction as the bottom proton, a BRTR a “C” type BT alpha.  

Slot6’s two protons spin in one direction - ‘geared’ with slot 10, BRTR “C”.  
Slot7’s two protons spin in one direction - ‘geared’ with slot 12, BLTL “M”.  
Slot8’s two protons spin in one direction - ‘geared’ with slot 11, BLTL “M”.  
Slot9’s two protons spin in one direction - ‘geared’ with slot 13, BRTR “C”.
When viewed toward the center of the Zn nucleus, slot1, the spin directions of slots 6, 7, 8, 9 are all CW.
Slot1 will then be spinning complementary with slots 6-9, in two directions, BRTL a “Q” type BT alpha, (upside down from what I thought last time).

My four single electron proton ep set assignments however may need more work:
Slots’ 14 and 15 are arbitrary.
For the two hook positions, slots 18 and 19, if Zn’s carousel is spinning, slot 19 receives primarily uninterrupted upward right spinning charge, while slot 18 receives uninterrupted downward left spinning anti-charge; or they both might be right spinners.

I found I was best able to identify the directions of adjacent orthogonal spins by assuming spinning adjacent protons would behave like meshed orthogonal gears; turning one turns the other in the “same” amount in the same forward direction, but with a 90 bend. Trace a path in the direction of the proton’s spin, along a slightly enlarged proton emission circle then turn 90 degrees when reaching the adjacent orthogonal proton’s emission circle. Do the spins match or not? In a slot with a single spin direction, the same path position and direction apply to both protons. In a two spin direction slot, one may reverse a path’s direction by switching to the slot’s other proton. One needs to keep the +/-, x y and z directions in mind. The paths form both directions within the three nuclear channels: left to right, front to back, and top to bottom.

Once again, I’ll need to go back and make corrections before continuing with the new Elements-Positions4 slot assignments. This time I’m relieved to have broken a worrisome mental logjam.
.

.

Proof of life. After just a few corrections in this first group, here are H thru Si, 1-14, Slot Layouts and plots.

I didn't want to step on Lloyd's post, I expect to provide the next batch tomorrow or the next day.

.

.

Currently good up to Zinc (again). Bottom/top electron position alpha types (MCPQ), with both top and bottom proton stack low charge field pressure holes, allows proper bonding between adjacent orthogonal slots, resulting in well-formed atomic Slot Layout diagrams. Decided to go ahead and remove all single holed TB alpha (WEAV) and ‘constant electron position’/‘constant proton spin’ type alphas (TL,TR,BR,BL) from all the atomic slot assignments. Here are the SL’s and plots for Phosphorus thru Zinc.

Starting with obvious right (upward charge) or left (downward anti-charge) spinning protons, then assuming adjacent orthogonal proton spins behave like meshed orthogonal gears - or perhaps they might tend to over time, may or may not be a valid charge field ‘spin rule’, nevertheless I believe such a spin rule is a positive addition. I’m getting plenty of practice and crossed eyes applying it to these BT assignments. Updated Elements-Positions4 with the new ‘StackNum’ values at github. Please feel free to point out any error.  

.

.

Here’s the next batch of BT assignments, Gallium thru Palladium, atomic numbers 31-46. Updated at
https://github.com/LtAirman/ChargeFieldTopics/blob/master/data/Elements-Positions4.csv

Finally, some forward progress!

BT indicates bottom/top electron positions, alpha type configurations. There are four types of BT configurations, consisting of two to six protons, all shown here are two or four proton stacks:
M. tBL … TLb. Left spinning protons.
C. tBR … TRb. Right spinning protons.
P. tBL … TRb. Left and right spinning protons. 
Q. tBR … TLb. Right and left spinning protons.
The small t’s and b’s indicate BT stack low charge field pressure, top and bottom holes, near the electron-vacant proton poles.

These new BT assignments (not including atomic numbers 1-30 and their s1-s9 single ep stack assignments) all have the ‘same’ basic Slot Layout configuration.

Code:


__________, __________, s14:TL/P
__________, __________, s4:M______, s9:C_______, s13:TR/P,
__________, s18:TL/BL_, s2:Q______, s16: TL/BL_,
s10:TR/P__, s6: C_____, s1:Q______, s7:M_______, s12:TR/P,
__________, s17:BR/TR_, s3:Q______, s19:TR/P/BR,  
s11:TR/P__, s8:M______, s5:C
__________, __________, s15:BR/P


It may just show my limited selection preferences and/or lack of imagination, but I’m tempted to draw conclusions from that general configuration. Like what alternate stacks are possible for the new ‘AltStacks’ column – which does not yet contain any valid values or code.


.

Hey LTAM,

Really really Nice Work! Looks good!

.


Thanks Cr6. I thought things were moving along nicely too till I found a fairly low level problem that must be corrected next. The least I could do was to make the problem look nice.

In five proton (or ep) stacks, as in Samarium, there are four alternate configurations for each of the
four BT type configurations, M, C, P, Q.

M. a. BL TL TL TL TL, b. BL BL TL TL TL, c. BL BL BL TL TL, d. BL BL BL BL TL
C. a. BR TR TR TR TR, b. BR BR TR TR TR, c. BR BR BR TR TR, d. BR BR BR BR TR          
P. a. BL TR TR TR TR, b. BL BL TR TR TR, c. BL BL BL TR TR, d. BL BL BL BL TR
Q. a. BR TL TL TL TL, b. BR BR TL TL TL, c. BR BR BR TL TL, d. BR BR BR BR TL

a. epn_stacks [88, 88, 88, 85, 86, 86, 85, 85, 86, 15, 15, 15, 15, 15, 15, 0, 2, 16, 16]
b. epn_stacks [92, 92, 92, 89, 90, 90, 89, 89, 90, 15, 15, 15, 15, 15, 15, 0, 2, 16, 16]
c. epn_stacks [96, 96, 96, 93, 94, 94, 93, 93, 94, 15, 15, 15, 15, 15, 15, 0, 2, 16, 16]
d. epn_stacks [100, 100, 100, 97, 98, 98, 97, 97, 98, 15, 15, 15, 15, 15, 15, 0, 2, 16, 16]

The three images a, b, and d show 'problems'.

M and C stack problems. The electrons are in their correct T or B positions,
though not all electrons have their correct colors - Top (cyan) or Bottom (black).
P and Q stack problems. Same electrons problem, plus not all protons spins
have their correct colors - Left (blue) or Right (red).

Only c is correct. Since all electrons are in their correct positions - this is likely a programming error in mBuilder15Jun.ipynb.

I should also mention that 5 ep stacks do not appear to conform with the ‘meshed’ orthogonal spin directions which made such good sense to me when thinking about two or four ep stacks.
.

.

My previous post's problem with bad BT type configurations has been corrected.
I reorient occasional plots in order to better see the electron positions.
Two ep alphas in the hook positions, slots 16-19 don't agree with upward CCW and downward anti-charge and meshed orthogonal gears either.  
.

.

Here are the next 16 atoms, Silver to Samarium. All slot assignments are single electron-proton ep’s (TRb, tBR, tBL, TLb) and 2,4,5,6 ep set BT type stacks (P-tBLTRb, Q-tBRTLb, C-tBRTRb, M-tBLTLb). There are no TB type stacks (A-TLbtBR, V-TRbtBR, E-TRbtBR, W-TLbtBL. There are also no constant-e-position/constant-spin stack types (TRTRb, tBRBR, tBLBL, TLTLb).

In clearing up the 5 ep BT type stacks’ T or B electron position and R or L proton spin color problem described in my two previous posts, I noticed a ‘bigger’ problem with 3 ep or larger TB type stacks. TB stacks must include low charge field pressure holes somewhere within the stack - stack gaps. Those gaps lengthen those stacks, making it necessary for the code to recalculate TB stack centers and where adjacent slots or atoms may bond with TB stacks. It felt like a gut punch. Why had I never noticed that problem in the project's current slot assignments?  

Thinking more about it, I believe TB stacks must occur, although I’d already decided to exclude TB slot assignments for the 90 elements since TB slots prevent well-formed slotlayout diagrams. Do you have any thoughts or  suggestions you might add?


.

Sounds like you see the logic behind the arrangements and alignments. Might check out Nevyn's old site to see C.F. directions? Just a thought.

.

Nevyn’s ‘Atomic Viewer’ Carbon and Oxygen atoms. I could argue that C slot1 which shows two, stacked, 2-ep BT alphas, involving three electron position changes and O slot1’s three, 2-ep BT alphas and 5 electron position changes are too many electron position changes. I believe Miles has said that the charge channel in any given stack limits electron position changes (and proton spin direction changes), to no more than one. On the other hand Miles has diagrammed C slot1 and O slot1 as two and three separate 2 proton alphas pretty much as Nevyn has shown.    

Hey Cr6. As we know, our project’s current set of slot assignments are roughly based on my ‘interpretation’ of Miles’ Diatomic Hydrogen paper, in which he describes how an electron accompanied proton creates a low charge field pressure zone, which I refer to as a ‘hole'. Bonds between protons must occur at one or the other (or both) proton’s hole(s). My project interpretation extrapolated two proton bonding to up to six axially aligned protons with one or no change of spin direction, either right or left (R to L) or L to R, and one top to bottom (TB) or no change of electron position within that stack. TB type electron position change alphas contain a single (actually two overlapped) internal hole bonding location. I also included constant electron position and constant spin stacks with a single external top or bottom hole. I did not include bottom-to-top, BT type alphas.  

Over the last few months I realized that my exclusion of BT electron position type stacks was wrong. Given ep hole bonding and a closer study of Miles’ descriptions of Carbon and Oxygen, BT stacks, with two external, top and bottom holes, are essential for building the elements. I cannot fault Miles for describing how two protons can bond without a BT stack, he wasn’t necessarily describing how a star might create Helium.

Another consideration, TB stacks’ top and bottom electrons are very exposed to the charge field. They are shielded on only their top or bottom side by one proton (and possibly more protons behind the first). BT stacks must be more stable, since every electron is shielded on both top and bottom sides by two protons. Maybe BT stacks are more difficult to form and result in stronger atomic bonds, while weaker molecular bonds can include TB stack bonds?

Anyway, as I’ve said before, when creating models, one must usually make some assumptions. If there are mistakes or problems, its best to correct and learn from them and move on. So my next order of business has developed into converting our atomic slot assignments from TB to BT. I’m feeling more and more confident that that is the correct and right thing to do.

At this point, with respect to alignments, another improvement might be to code re-centering 5 ep stacks in slots like slot2 or slot3 such that three protons with one electron position and one spin might be located on one side of a charge channel, and two protons with a second electron position and spin are on the other side of the channel. That likely results in a spin imbalance that may be acceptable in some circumstances but not all. One proton with one electron position and spin on one side of a charge channel and four protons with a second electron position and spin on the other side of the channel within a single slot may constitute a severe imbalance, and a good reason to disallow such unbalanced slots in most situations. I didn’t include any such re-centering in my Silver to Samarium slot layouts or plots, do you think I should? Or perhaps the vertical charge channel should pass through an orthogonal proton in a stack containing an even number of protons in slot2 or slot3 which would also require slot re-centering?

What am I missing?
.

I don't think you are missing anything in your thoughts about these structures. I know I've asked this before but maybe look for "problem children"...cases (Atomic Formulas) where alignments are found to work with your structures and cases where they "don't". I know these can be hard to find.  Or just look at simple 2-3 atom formulas and look for cases to "determine good-problem-known bad".  You've explain formulas quite well in the past. Just looking for validation steps...something like this? Sometimes it is easier to start defining the negatives instead of the positives for the bonds...Rules like this? (Coded in Python validation functions). You have the structures for this looking really good at this point:

Step 1: These two atoms can bond on this single slot because of T-B/R-L/pressure.  
Step 2: This atom should allow bonds of this Slot type on these slots.
Step 3: This atom should allow bonds on this Slot at these angles
Step 4: These are proton-neutron arrangements on this slot for these bonds to occur
Step 5: This atom won't bond on this slot because X,Y,Z,L,R,T,B, epn's or slot is unreachable.
Step 6: This pressure +/- won't allow these slot bonds.

LTAM wrote:I didn’t include any such re-centering in my Silver to Samarium slot layouts or plots, do you think I should? Or perhaps the vertical charge channel should pass through an orthogonal proton in a stack containing an even number of protons in slot2 or slot3 which would also require slot re-centering?

Good question? Which slot formations allow N-S and which output horizontally.  

I know we kind of rehash this every few months but it is tricky to wrap one's mind globally around this for all cases. Like how unique is this case? Why is it unique?

Here's something I randomly found in my "ElementSrc-BIND-ElementDest" graph. Can these bond? I still need better "negative" step by step...reasons set up for Non-binding...

.

The next 16 atoms, Europium thru Platinum.

I sure have slowed things down in trying to add EPNStacks.csv and replacing TB slot assignments with BT type slots instead. They seem to me to be the right things to do but of course I may be mistaken.

Thanks for your thoughts and guidance, I needed them.

Cr6 wrote. Here's something I randomly found in my "ElementSrc-BIND-ElementDest" graph. Can these bond? I still need better "negative" step by step...reasons set up for Non-binding...  

Given this ‘random example’, I’ll play along, I like trying to interpret formulas.

Ok, the image doesn’t include any formula, but I see two elements, and the two candidate binding slots to consider: Ta:(B13Z2L) and He:(A1Z2A).
I tried looking for “He?Ta?” at NIST and came up empty. https://webbook.nist.gov/chemistry/form-ser/#Help

Also tried looking for formulas containing He and Ta in ‘Physics’ with no joy, realizing I’ll need another go round in re-familiarizing myself with T SQL ‘Physics’, cypher and Neo4j.  


Here’s Ta:(B13Z2L) and He:(A1Z2A) from mBuilder - not including EPNStacks.csv or BT alphas.

Z aligned Ta slot 13 has a single low charge field pressure hole at its top– identified with an asterisk ‘*’. TB alpha Helium presumably has a hole in its center, as I mentioned recently, if there’s a center hole in He, maybe both protons need to be vertically separated to indicate that. I’ll add it to my to-do list and do that later if I still think that needs to be done. More importantly, there may be as many as 12 different He 2-ep stacks, of varying stability??? 4 different constant electron-position/constant proton-spin types, 4 TB alpha types and 4 BT alpha types.

Since Ta slot13 and He slot1 together total just 4 protons – less than the maximum slot proton count of 6, He and Ta slot13 might add together in a single in-line stack; just flip He vertically and place it at the asterisk to make a single stack - TRBLBLBL. Does ‘Physics’ include single final stack solutions?
 
BT He alphas, with holes at top and bottom, might bond at both Ta slot 13 ends, as well as a separate 2-ep stack orthogonal to slot13 in the negative x direction.

Were there no other Ta-He bonds identified? Oops, this is a pretend discussion. That’s enough fun for now. Thanks again Cr6. 



There are a few Tantalum Formulas mainly from ChemSpider with a couple of Superconductors:

Formula Detail
CSID:22504700 Al10La3O51Sr14Ta7
Aluminum - tantalum (3:1) Al3Ta
Tantalum trialuminide Al3Ta
Tantalumaluminium(Ta-Al) AlTa
Gold - tantalum (1:3) AuTa3
Diborylidynetantalum B2Ta
BARIUM TANTALUM OXIDE BaO6Ta2
Beryllium - tantalum (5:1) Be5Ta
Beryllium - tantalum (1:1) BeTa
Tantalum(2+) dibromide Br2Ta
Tantalum bromide Br2Ta
Tantalum(4+) tetrabromide Br4Ta
Tantalum bromide (TaBr5) Br5Ta
Hexabromotantalate(1-) Br6Ta
Borylidynetantalum BTa
tantalum monoxide trifluoride F3OTa
Tantalum monoxide trifluoride F3OTa
tantalum pentafluoride F5Ta
Tantalum pentafluoride F5Ta
Potassium hexafluorotantalate(1-) F6KTa
Sodium tantalum(5+) fluoride (1:1:6) F6NaTa
TT1225000 F7K2Ta
Iron - tantalum (2:1) Fe2Ta
Iron - tantalum (7:3) Fe7Ta3
Barium hydroxide - tantalum hydrate (1:2:2:4) H10BaO6Ta2
Cadmium hydroxide - tantalum hydrate (1:2:2:4) H10CdO6Ta2
Barium - tantalum hydrate (1:2:6) H12BaO6Ta2
Germane - tantalum (3:5) H12Ge3Ta5
lead;tantalum;hexahydrate H12O6PbTa2
Tantalum - trihydridoaluminium (1:7) H21Al7Ta
Borylidynetantalum H2BTa
Tantalum, hydroxydioxo-, lead salt (2:1) H2O6PbTa2
D2TaO H2OTa
H2TaO H2OTa
++²-Plumbane - tantalum (1:3) H2PbTa3
++²-silanylidene(silylidene)tantalum H2Si2Ta
Dihydridotantalum H2Ta
Tantalum - trihydridoaluminium (1:1) H3AlTa
Tantalum nitride H3NTa
Phosphine - tantalum (1:1) H3PTa
Germane - tantalum (1:1) H4GeTa
Germane - tantalum (1:3) H4GeTa3
Tantalum dihydrate H4O2Ta
Disilylenetantalum H4Si2Ta
Tantalum telluride H4TaTe2
Potassium hydroxide - tantalum hydrate (1:1:1:2) H5KO3Ta
Lithium hydroxide - tantalum hydrate (1:1:1:2) H5LiO3Ta
Tantalum(5+) pentahydroxide H5O5Ta
Tantalum(V) hydride H5Ta
potassium; tantalum; trihydrate H6KO3Ta
Tantalum hydrate H6O3Ta3
Tantalum(2+) bis[pentahydridosilicate(1-)] H6Si2Ta
disilylsilyl(tantaliotantaliotantaliotantalio)tantalum H7Si3Ta5
MFCD00074975 H8F7N2Ta
Gadolinium - tantalum hydrate (1:1:4) H8GdO4Ta
Germane - tantalum (2:1) H8Ge2Ta
Helium - tantalum (1:1) HeTa
Hydroxy(dioxo)tantalum HO3Ta
++³-silanylidyne(silylidyne)tantalum HSi2Ta
TANTALUM (V) IODIDE I5Ta
Iridium - tantalum (1:1) IrTa
MFCD00049652 KO3Ta
Potassium oxido(dioxo)tantalum KO3Ta
potassium;oxygen(2-);tantalum(5+) KO3Ta
WW5470000 LiO3Ta
lithium;ozone;tantalum LiO3Ta
lithium; oxygen(-2) anion; tantalum(+5) cation LiO3Ta
LiTaO3 NULL
dimagnesium; oxygen(-2) anion; tantalum(+5) cation Mg2O7Ta2
Magnesium bis[oxido(dioxo)tantalum] MgO6Ta2
Molybdenum - tantalum (1:1) MoTa
N2O2Ta N/A
N2Ta N/A
N2Ta N/A
N2Ta N/A
CSID:9541759 N2Ta2
N3O3Ta N/A
nitrogen(3-);tantalum(5+) N5Ta3
sodium; oxygen(-2) anion; tantalum(+5) cation NaO3Ta
NaTaO3 NULL
Niobium - tantalum (1:1) NbTa
NOTa N/A
NOTa- N/A
Nitridotantalum NTa
O2Ta 12036-14-5
O2Ta+ N/A
O2Ta- N/A
O2Ta2 N/A
Rubidium oxido(dioxo)tantalum O3RbTa
Oxido(dioxo)tantalum O3Ta
O3Ta- N/A
O4Ta N/A
O5Ta2 1314-61-0
Tetraoxo[++-++²-plumbanediolato(2-)-+¦O¹:+¦O¹]ditantalum O6PbTa2
distrontium; oxygen(-2) anion; tantalum(+5) cation O7Sr2Ta2
Tungsten, oxo-, rubidium tantalum salt (1:1:1) ORbTaW
OTa 12035-90-4
OTa+ N/A
OTa3 112510-43-7
OTa3 N/A
OTa3- N/A
Tantalum phosphide PTa
phosphorus(3-);tantalum(3+) PTa
S2Ta N/A
selenium;tantalum Se2Ta
MFCD00064699 Se2Ta
Tantalum silicide (TaSi2) Si2Ta
silicon; tantalum Si2Ta
silanidylidynesilanide; tantalum(2+) Si2Ta
silicon; tantalum Si3Ta5
Ta 7440-25-7
Ta+ 20561-66-4
Ta- 56217-42-6
Ta3 N/A
Tantalum - titanium (3:7) Ta3Ti7
Ta4 N/A
TaBa9Cu10O20 SuperConductor
TaBr3 NULL
TaBr5 NULL
TaCl5 NULL
TaI5 NULL
TaO3 NULL
TaSi2O2 SuperConductor
Ditelluroxotantalum TaTe2
tantalum(+2) cation; tungsten(+2) cation TaW

Query:
SELECT DISTINCT [ID]
,[Molecule]
,[Formula]
,[Detail]
FROM [Physics].[dbo].[Species]
Where Formula like '%Ta%'
and Formula not like 'C%'
Order by Formula

LTAM wrote:Here’s Ta:(B13Z2L) and He:(A1Z2A) from mBuilder - not including EPNStacks.csv or BT alphas.

Z aligned Ta slot 13 has a single low charge field pressure hole at its top– identified with an asterisk ‘*’. TB alpha Helium presumably has a hole in its center, as I mentioned recently, if there’s a center hole in He, maybe both protons need to be vertically separated to indicate that. I’ll add it to my to-do list and do that later if I still think that needs to be done. More importantly, there may be as many as 12 different He 2-ep stacks, of varying stability??? 4 different constant electron-position/constant proton-spin types, 4 TB alpha types and 4 BT alpha types.

Since Ta slot13 and He slot1 together total just 4 protons – less than the maximum slot proton count of 6, He and Ta slot13 might add together in a single in-line stack; just flip He vertically and place it at the asterisk to make a single stack - TRBLBLBL. Does ‘Physics’ include single final stack solutions?

BT He alphas, with holes at top and bottom, might bond at both Ta slot 13 ends, as well as a separate 2-ep stack orthogonal to slot13 in the negative x direction.

Hi LTAM...thanks for detailed post. I did see a simple bond between He and Ta...thought it would be more complex in a larger formula structure. Strange that bonding between a gas and a metal exists like this. Just another "curiosity" possibly. May need to vet this with more mainstream literature as well. Tantalum apparently binds with Oxygen: https://en.wikipedia.org/wiki/Tantalum_pentoxide



Query:

Code:

SELECT *
  FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
  where Formula like '%Ta%He%' or Formula like '%He%Ta%'
  and CanBindDest = 1 and CanBindSrc = 1

Didn't see it as valid in NIST...let me try to source this. Looks like it is from "ChemSpider": Helium - tantalum (1:1) | HeTa | ChemSpider

Uses
In electronics
Owing to its high band gap and dielectric constant, tantalum pentoxide has found a variety of uses in electronics, particularly in tantalum capacitors. These are used in automotive electronics, cell phones, and pagers, electronic circuitry; thin-film components; and high-speed tools. In the 1990s, interest grew in the use of tantalum oxide as a high-k dielectric for DRAM capacitor applications.[22][23]

It is used in on-chip metal-insulator-metal capacitors for high frequency CMOS integrated circuits. Tantalum oxide may have applications as the charge trapping layer for non-volatile memories.[24][25] There are applications of tantalum oxide in resistive switching memories.[26]

In optics
Due to its high refractive index, Ta2O5 has been utilized in the fabrication of the glass of photographic lenses.[2][27] It can also be deposited as an optical coating with typical applications being antireflection and multilayer filter coatings in near UV to near infrared. [28]

Ta2O5 has also been found to have a high nonlinear refractive index,[29][30] on the order of three times that of silicon nitiride, which has led to interest in the utilization of Ta2O5 in photonic integrated circuits. Ta2O5 has been recently utilized as the material platform for the generation of supercontinuum[31][32] and Kerr frequency combs[30] in waveguides and optical ring resonators. Through the addition of rare-earth dopants in the deposition process, Ta2O5 waveguide lasers have been presented for a variety of applications, such as remote sensing and LiDAR.[33][34][35] https://en.wikipedia.org/wiki/Tantalum_pentoxide

Whenever I see "Stokes" or "Ramen Scattering" I immediately think of Miles' Charge Field which likely can account for all observations...just my opinion. A lot of time and money have been dumped into this over the last decades...I would think they would have a better accounting of it at this point:
https://www.frontiersin.org/journals/remote-sensing/articles/10.3389/frsen.2021.641723/full
https://en.wikipedia.org/wiki/Supercontinuum

Like is this the C.F.? Or something half-baked:

Description of dynamics of continuum formation in fiber

In this section we will briefly discuss the dynamics of the two main regimes in which supercontinua are generated in fibre. As previously stated a supercontinuum occurs through the interaction of many nonlinear processes to cause extensive spectral broadening. Many of these processes such as: self-phase modulation, four-wave mixing, and soliton-based dynamics have been well understood, individually, for some time. The breakthroughs in recent years have involved understanding and modelling how all these processes interact together to generate supercontinua and how parameters can be engineered to enhance and control continuum formation. The two main regimes are the soliton fission regime and modulation instability regime. The physical processes can be considered to be quite similar and the descriptions really enable us to distinguish between the processes that drive the continuum formation for varying pump conditions. A third regime, pumping in the normal dispersion region, is also covered. This is a perfectly viable way to generate a supercontinuum. However, it is not possible to generate the same bandwidths by this method.

http://milesmathis.com/antistokes2.pdf
http://milesmathis.com/bright3.pdf
http://milesmathis.com/raman.pdf
http://milesmathis.com/bohr2.pdf

.

Slotlayout (SL) diagrams above and atomic plots below for Gold through Thorium, 79-90. ‘SlotNum’ values (0 to 144), referring to all possible, none or 1-6 electron/proton ep stacks have been added to the 1710 slot stacks (1246 with values of 1 or more) for our 90 atoms. Most slot ep configuration assignments have been changed from top-bottom (TB) electron-positions to BT type alphas.

Additional tasks that need doing:

Coding new slot labels. As I’ve previously mentioned, additional data should be added to the lot layout labels in order to identify exactly which stack is in any given slot. The additional stack data would allow the code or users to select specific alternative SL configurations.

The SL’s slot labels currently consist of the following data: 1. ‘SlotSpin’: (‘ ’, L, R, A, V, E, W, P, Q, M, C). 2. ‘SlotNumber’:1-19. 3. ‘SlotOrien’: (X,Y,Z). 4. ‘Protons’: 0-6. And 5. ‘Electrons’: (‘ ’, T, B, A, V, E, W, P, Q, M, C). If you know the code, the result is an easy to read group of 5 or 6 ‘character digits’. Such as Gold slot1 Au:(Q1Z6Q). The ambiguity is that there are 5 (of 144) ep stacks in which there are 6 protons, and where both ‘SlotSpin’ and ‘Electrons’ have ‘Q’ values. Those stacks are: 128, 132, 136, 140, 144.

One constraint, the slot label is currently, 5-6 digits, that’s fairly long. I don’t want to just add 6. ‘StackNumber’: 0-144, to the end. That would result in a 6-9 digit code as in Au:(Q1Z6Q136). A shorter label is needed. I might just add 6. ‘Tcount’:1-5,  the number of top (or bottom) electron positions in the +z portion of the TB or BT alpha stack. That results in an easy to read (if you know the code) 6 or 7 digits as in Au:(Q1Z6Q3), indicating (tBRBRBRTLTLTLb).

I suppose the smallest number of digits might result from: 1. ‘SlotNumber’:1-19. 2. ‘SlotOrien’: (X,Y,Z). And 3. ‘StackNumber’: 0-144. Au slot1 would be Au:(1Z136). That’s the same length as the current slot label but without an explicit proton count or electron position or proton spin data, B, T, R, L, A, V, E, W, P, Q, M, C its a little more difficult to ‘read’. One would need to look up the stack number. That's probably what I’ll end up doing. Or might that interfere with the current 'Phyics' LTAMkeys data?  

Review all slot ‘CanBind’ values. And correct as needed. All ep’s and ep stacks can bond. ‘CanBind’ needs to be with respect to the atom. As you said, whether the slot can be reached or not.  

Add the new ‘AltStacks’ column. I still need to figure out how to format and include values for the new ‘AltStacks’ column, which can involve one or more integers and integer lists.

Make many cell changes in order to read the new stack data, create the SL’s, plot the atoms, etc and arrive at the next version of mBuilder which may need a new name.

Add a new gui control or two. As far as the notebook project goes, a main goal is to display molecules. I’ll probably need to add a new gui control or two for more atomic slot alternatives.

\//\\\////\\\\\/////\\\\///\\/

HeTa.

Cr6 wrote. Strange that bonding between a gas and a metal exists like this. Just another "curiosity" possibly. May need to vet this with more mainstream literature as well.
Airman. I think it exists all right. Let me know what your mainstream vetting turns up.

Last time I screwed up flipping Helium, He:(A1Z2A) and placing it at the asterisk to make a single stack – TRBLBLBL. Changing He to (V1Z2V) would allow it to bond at Tantalum slot13’s top. After all these years I better stop before I screw it up again. As you’ve noted, its a simple bond.

Thank for all the Ta formulas, and thanks for the %He%Ta% or %He%Ta% formulas query. I’m surprised to see the 10 row outputs, each row a separate bond. In six of the rows, He can bond in-line at every Ta extent, slots 10-15: (B10Z3R-A1Z2A), (T11Z2R-A1Z2A), (T12Z3L-A1Z2A), (B13Z2L-A1Z2A), (T14Y3L-A1Z2A), (B15Y3R-A1Z2A). All are in Ta-He order.

In 2 rows, He can bond with the two unoccupied Ta hook positions at slots 2 and 3 - which must be orthogonal, to become He stacks in Ta slots 18 and 19.  (A2Y6A-A1Z2A), (V3Y6V-A1Z2A). How could we tell whether any of those bonds are orthogonal or in-line bonds? The particle coordinates are included, I guess I should try plotting them out?  

The two remaining rows how Ta bonding to He, and would appear to be duplicates of He bonding to Ta at slots 11 and 13: (A1Z2A-T11Z2R),  (A1Z2A-B13Z2L). They are in He-Ta order.  Shouldn’t all bonds between He and Ta be repeated in both directions?

I admit I have a hard time understanding SQL, but your binding list seems expansive, and generous, finding more bonds than a single He TB alpha slot can account for. Maybe you are ahead of me?  

Your query output forced me to reappraise my bonding thoughts. As we know, any proton accompanied by an electron (ep) has a relative low charge field pressure zone – a hole, on the pole side opposite the electron. That hole can capture and bind with any nuclear particle (e n or p). A proton with two electrons, (epe), an oppositely spun electron for each proton pole, may not be uncommon. That proton will have both top and bottom holes. Neither electron nor positron can prevent another electron (or positron) or an electron accompanied or unaccompanied proton or neutron from approaching and occupying that hole. Any ep proton stack sharing a spin axis has holes at its poles whether there is an electron already at the stack end (such as TB alphas) or not. Intervening electrons aren’t sufficient to prevent in-line stack bonding between protons. I’ve probably been overly-rigid in specifying whether allowed stacks are either TB or BT alphas. The electrons are more fluid than that.


.

For Ta this is an interesting query to filter to 1 or 2 molecule bonds. If you do come up with an extended "LTAMKey" would be kind of cool to have a table for each key and "Description" next to the Key value to describe at length what each value represents? Could be done with a code function possibly?

Code:

SELECT Distinct  [ZID]
      ,[Formula]
     ,ElementSrc
     ,ElementDest, AtomicNumberSrc, AtomicNumberDest, IsValid, IsValidinNist --, LTAMKeySrc, LTAMKeyDest
  FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
  WHERE 1=1
  and Formula like '%Ta%'
  and Formula not like '%-%'
  and CanBindSrc =1 and CanBindDest =1
  and (ElementSrc = 'tantalum' or ElementDest = 'tantalum')
  and LEN(Formula) < 5 and  Formula not like '%[0-9]%'
  order by 1, ElementSrc, ElementDest


Output...just uncomment the -- to see all LTAMKeys.

ZID Formula ElementSrc ElementDest AtomicNumberSrc AtomicNumberDest IsValid IsValidinNist
44068.03125 TaAs arsenic tantalum 33 73 1 0
44068.03125 TaAs tantalum arsenic 73 33 1 0
74745 NTa nitrogen tantalum 7 73 1 0
74745 NTa tantalum nitrogen 73 7 1 0
124062 OTa oxygen tantalum 8 73 1 1
124062 OTa tantalum oxygen 73 8 1 1
140205 CTa carbon tantalum 6 73 1 1
140205 CTa tantalum carbon 73 6 1 1
648183 TaPS phosphorus tantalum 15 73 1 0
648183 TaPS sulfur tantalum 16 73 1 1
648183 TaPS tantalum phosphorus 73 15 1 0
648183 TaPS tantalum sulfur 73 16 1 1
648973 TaPd tantalum palladium 73 46 1 0
1523600 TaIr iridium tantalum 77 73 1 0
1523600 TaIr tantalum iridium 73 77 1 0
1527277 TaTc tantalum technetium 73 43 1 0
1527277 TaTc technetium tantalum 43 73 1 0
1529710 TaNO nitrogen tantalum 7 73 1 0
1529710 TaNO oxygen tantalum 8 73 1 1
1529710 TaNO tantalum nitrogen 73 7 1 0
1529710 TaNO tantalum oxygen 73 8 1 1
2310099 TaB boron tantalum 5 73 1 0
2310099 TaB tantalum boron 73 5 1 0
9008974 TaP phosphorus tantalum 15 73 1 0
9008974 TaP tantalum phosphorus 73 15 1 0
9008975 TaN nitrogen tantalum 7 73 1 0
9008975 TaN tantalum nitrogen 73 7 1 0
10636616 TaW tantalum tungsten 73 74 1 0
10636616 TaW tungsten tantalum 74 73 1 0
21542598 PTa phosphorus tantalum 15 73 1 0
21542598 PTa tantalum phosphorus 73 15 1 0
28688565 MoTa molybdenum tantalum 42 73 1 0
28688565 MoTa tantalum molybdenum 73 42 1 0
57448694 BeTa tantalum beryllium 73 4 1 0
57449223 CoTa cobalt tantalum 27 73 1 0
57449223 CoTa tantalum cobalt 73 27 1 0
57449670 IrTa iridium tantalum 77 73 1 0
57449670 IrTa tantalum iridium 73 77 1 0
57450295 HeTa helium tantalum 2 73 1 0
57450295 HeTa tantalum helium 73 2 1 0
57566544 NbTa niobium tantalum 41 73 1 0
57566544 NbTa tantalum niobium 73 41 1 0
75336402 AlTa aluminium tantalum 13 73 1 0
75336402 AlTa tantalum aluminium 73 13 1 0

Working with this query to load Formula bonds into Neo4j-Aura for each atom-slot in a formula. I still need to refactor everything with your newer "slot" notations for epn directions.
Might help to see more "weird" stuff.

Dupes the Atoms per their Count in the formula (CO2) -- Carbon listed once, Oxygen duped 2 times showing all binding slots duped as well:
--------

Code:

SELECT TOP 100 PERCENT
     A.*
 ,Number AS AtomCountNumber
FROM (
 SELECT DISTINCT Formula
 ,LTAMKeySrc AS LTAMKey
 ,AtomicNumberSrc AS AtomicNumber
 ,ElementSrc AS Element
 ,ElectronsSrc AS Electrons
 ,SlotNumberSrc AS SlotNumber
 ,SlotOrienSrc AS SlotOrientation
 ,AlphaTypeSrc AS AlphaType
 ,SlotSpinSrc AS SlotSpin
 ,AtomicSymbolSrc AS AtomicSymbol
 ,CurrentAtomCount AS AtomCount
 ,1 AS AtomOrder
 --,'Src' AS BondDirection
 --,IsValidinNist
 FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
 WHERE CanBindSrc = 1
 AND CanBindDest = 1
 AND AtomicSymbolSrc = CurrentAtom
 
 UNION
 
 SELECT DISTINCT Formula
 ,LTAMKeyDest AS LTAMKey
 ,AtomicNumberDest AS AtomicNumber
 ,ElementDest AS Element
 ,ElectronsDest AS Electrons
 ,SlotNumberDest AS SlotNumber
 ,SlotOrienDest AS SlotOrientation
 ,AlphaTypeDest AS AlphaType
 ,SlotSpinDest AS SlotSpin
 ,AtomicSymbolDest AS AtomicSymbol
 ,CurrentAtomCount AS AtomCount
 ,1 AS AtomOrder
 --,'Dest' AS BondDirection
 --,IsValidinNist
 FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
 WHERE CanBindSrc = 1
 AND CanBindDest = 1
 AND AtomicSymbolDest = CurrentAtom
 
 UNION
 
 SELECT DISTINCT Formula
 ,LTAMKeySrc AS LTAMKey
 ,AtomicNumberSrc AS AtomicNumber
 ,ElementSrc AS Element
 ,ElectronsSrc AS Electrons
 ,SlotNumberSrc AS SlotNumber
 ,SlotOrienSrc AS SlotOrientation
 ,AlphaTypeSrc AS AlphaType
 ,SlotSpinSrc AS SlotSpin
 ,AtomicSymbolSrc AS AtomicSymbol
 ,NextAtom1Count AS AtomCount
 ,2 AS AtomOrder
 --,'Src' AS BondDirection
 --,IsValidinNist
 FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
 WHERE CanBindSrc = 1
 AND CanBindDest = 1
 AND AtomicSymbolSrc = NextAtom1
 
 UNION
 
 SELECT DISTINCT Formula
 ,LTAMKeyDest AS LTAMKey
 ,AtomicNumberDest AS AtomicNumber
 ,ElementDest AS Element
 ,ElectronsDest AS Electrons
 ,SlotNumberDest AS SlotNumber
 ,SlotOrienDest AS SlotOrientation
 ,AlphaTypeDest AS AlphaType
 ,SlotSpinDest AS SlotSpin
 ,AtomicSymbolDest AS AtomicSymbol
 ,NextAtom1Count AS AtomCount
 ,2 AS AtomOrder
 --,'Dest' AS BondDirection
 --,IsValidinNist
 FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
 WHERE CanBindSrc = 1
 AND CanBindDest = 1
 AND AtomicSymbolDest = NextAtom1
 
 UNION
 
 SELECT DISTINCT Formula
 ,LTAMKeySrc AS LTAMKey
 ,AtomicNumberSrc AS AtomicNumber
 ,ElementSrc AS Element
 ,ElectronsSrc AS Electrons
 ,SlotNumberSrc AS SlotNumber
 ,SlotOrienSrc AS SlotOrientation
 ,AlphaTypeSrc AS AlphaType
 ,SlotSpinSrc AS SlotSpin
 ,AtomicSymbolSrc AS AtomicSymbol
 ,NextAtom2Count AS AtomCount
 ,3 AS AtomOrder
 --,'Src' AS BondDirection
 --,IsValidinNist
 FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
 WHERE CanBindSrc = 1
 AND CanBindDest = 1
 AND AtomicSymbolSrc = NextAtom2
 
 UNION
 
 SELECT DISTINCT Formula
 ,LTAMKeyDest AS LTAMKey
 ,AtomicNumberDest AS AtomicNumber
 ,ElementDest AS Element
 ,ElectronsDest AS Electrons
 ,SlotNumberDest AS SlotNumber
 ,SlotOrienDest AS SlotOrientation
 ,AlphaTypeDest AS AlphaType
 ,SlotSpinDest AS SlotSpin
 ,AtomicSymbolDest AS AtomicSymbol
 ,NextAtom2Count AS AtomCount
 ,3 AS AtomOrder
 --,'Dest' AS BondDirection
 --,IsValidinNist
 FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
 WHERE CanBindSrc = 1
 AND CanBindDest = 1
 AND AtomicSymbolDest = NextAtom2
 
 UNION
 
 SELECT DISTINCT Formula
 ,LTAMKeySrc AS LTAMKey
 ,AtomicNumberSrc AS AtomicNumber
 ,ElementSrc AS Element
 ,ElectronsSrc AS Electrons
 ,SlotNumberSrc AS SlotNumber
 ,SlotOrienSrc AS SlotOrientation
 ,AlphaTypeSrc AS AlphaType
 ,SlotSpinSrc AS SlotSpin
 ,AtomicSymbolSrc AS AtomicSymbol
 ,NextAtom3Count AS AtomCount
 ,4 AS AtomOrder
 --,'Src' AS BondDirection
 --,IsValidinNist
 FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
 WHERE CanBindSrc = 1
 AND CanBindDest = 1
 AND AtomicSymbolSrc = NextAtom3
 
 UNION
 
 SELECT DISTINCT Formula
 ,LTAMKeyDest AS LTAMKey
 ,AtomicNumberDest AS AtomicNumber
 ,ElementDest AS Element
 ,ElectronsDest AS Electrons
 ,SlotNumberDest AS SlotNumber
 ,SlotOrienDest AS SlotOrientation
 ,AlphaTypeDest AS AlphaType
 ,SlotSpinDest AS SlotSpin
 ,AtomicSymbolDest AS AtomicSymbol
 ,NextAtom3Count AS AtomCount
 ,4 AS AtomOrder
 --,'Dest' AS BondDirection
 --,IsValidinNist
 FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
 WHERE CanBindSrc = 1
 AND CanBindDest = 1
 AND AtomicSymbolDest = NextAtom3
 
 UNION
 
 SELECT DISTINCT Formula
 ,LTAMKeySrc AS LTAMKey
 ,AtomicNumberSrc AS AtomicNumber
 ,ElementSrc AS Element
 ,ElectronsSrc AS Electrons
 ,SlotNumberSrc AS SlotNumber
 ,SlotOrienSrc AS SlotOrientation
 ,AlphaTypeSrc AS AlphaType
 ,SlotSpinSrc AS SlotSpin
 ,AtomicSymbolSrc AS AtomicSymbol
 ,NextAtom4Count AS AtomCount
 ,5 AS AtomOrder
 --,'Src' AS BondDirection
 --,IsValidinNist
 FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
 WHERE CanBindSrc = 1
 AND CanBindDest = 1
 AND AtomicSymbolSrc = NextAtom4
 
 UNION
 
 SELECT DISTINCT Formula
 ,LTAMKeyDest AS LTAMKey
 ,AtomicNumberDest AS AtomicNumber
 ,ElementDest AS Element
 ,ElectronsDest AS Electrons
 ,SlotNumberDest AS SlotNumber
 ,SlotOrienDest AS SlotOrientation
 ,AlphaTypeDest AS AlphaType
 ,SlotSpinDest AS SlotSpin
 ,AtomicSymbolDest AS AtomicSymbol
 ,NextAtom4Count AS AtomCount
 ,5 AS AtomOrder
 --,'Dest' AS BondDirection
 --,IsValidinNist
 FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
 WHERE CanBindSrc = 1
 AND CanBindDest = 1
 AND AtomicSymbolDest = NextAtom4
 
 UNION
 
 SELECT DISTINCT Formula
 ,LTAMKeySrc AS LTAMKey
 ,AtomicNumberSrc AS AtomicNumber
 ,ElementSrc AS Element
 ,ElectronsSrc AS Electrons
 ,SlotNumberSrc AS SlotNumber
 ,SlotOrienSrc AS SlotOrientation
 ,AlphaTypeSrc AS AlphaType
 ,SlotSpinSrc AS SlotSpin
 ,AtomicSymbolSrc AS AtomicSymbol
 ,NextAtom5Count AS AtomCount
 ,6 AS AtomOrder
 --,'Src' AS BondDirection
 --,IsValidinNist
 FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
 WHERE CanBindSrc = 1
 AND CanBindDest = 1
 AND AtomicSymbolSrc = NextAtom5
 
 UNION
 
 SELECT DISTINCT Formula
 ,LTAMKeyDest AS LTAMKey
 ,AtomicNumberDest AS AtomicNumber
 ,ElementDest AS Element
 ,ElectronsDest AS Electrons
 ,SlotNumberDest AS SlotNumber
 ,SlotOrienDest AS SlotOrientation
 ,AlphaTypeDest AS AlphaType
 ,SlotSpinDest AS SlotSpin
 ,AtomicSymbolDest AS AtomicSymbol
 ,NextAtom5Count AS AtomCount
 ,6 AS AtomOrder
 --,'Dest' AS BondDirection
 --,IsValidinNist
 FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
 WHERE CanBindSrc = 1
 AND CanBindDest = 1
 AND AtomicSymbolDest = NextAtom5
 
 UNION
 
 SELECT DISTINCT Formula
 ,LTAMKeySrc AS LTAMKey
 ,AtomicNumberSrc AS AtomicNumber
 ,ElementSrc AS Element
 ,ElectronsSrc AS Electrons
 ,SlotNumberSrc AS SlotNumber
 ,SlotOrienSrc AS SlotOrientation
 ,AlphaTypeSrc AS AlphaType
 ,SlotSpinSrc AS SlotSpin
 ,AtomicSymbolSrc AS AtomicSymbol
 ,NextAtom6Count AS AtomCount
 ,6 AS AtomOrder
 --,'Src' AS BondDirection
 --,IsValidinNist
 FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
 WHERE CanBindSrc = 1
 AND CanBindDest = 1
 AND AtomicSymbolSrc = NextAtom6
 
 UNION
 
 SELECT DISTINCT Formula
 ,LTAMKeyDest AS LTAMKey
 ,AtomicNumberDest AS AtomicNumber
 ,ElementDest AS Element
 ,ElectronsDest AS Electrons
 ,SlotNumberDest AS SlotNumber
 ,SlotOrienDest AS SlotOrientation
 ,AlphaTypeDest AS AlphaType
 ,SlotSpinDest AS SlotSpin
 ,AtomicSymbolDest AS AtomicSymbol
 ,NextAtom6Count AS AtomCount
 ,6 AS AtomOrder
 --,'Dest' AS BondDirection
 --,IsValidinNist
 FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
 WHERE CanBindSrc = 1
 AND CanBindDest = 1
 AND AtomicSymbolDest = NextAtom6
 ) A
INNER JOIN [dbo].[Numbers] N ON N.Number BETWEEN 1
 AND A.AtomCount
--where A.Formula = 'AcBeH8'
ORDER BY
         A.Formula
 ,A.AtomOrder
 ,N.Number
 ,A.SlotNumber
 ,A.AlphaType



Will add it to this after looking at it a bit more with a "Formula" node linked with each Element:

Some more initial "dorking around" with Neo4j's Aura and getting the Formula -> Element -> Slot Number lined up. The import script for creating a .csv file is below. This is based on logic for creating the [dbo].[AtomicMilesMathisOrbitalsDetailAllBonds] table within the Stored Procedure [dbo].[spBuildAtomicMilesMathisOrbitalsDetailAllBonds]. I may need to add the "IsValid=1" to the query below to get rid of "known bad bonds" (like slot-1-3 bonding with full carousel atoms):
-------

Code:


SELECT TOP 100 PERCENT
    A.*
   ,Number AS AtomCountNumber
FROM (
   SELECT DISTINCT Formula
      ,LTAMKeySrc AS LTAMKey
      ,AtomicNumberSrc AS AtomicNumber
      ,ElementSrc AS Element
      ,ElectronsSrc AS Electrons
      ,SlotNumberSrc AS SlotNumber
      ,SlotOrienSrc AS SlotOrientation
      ,AlphaTypeSrc AS AlphaType
      ,SlotSpinSrc AS SlotSpin
      ,AtomicSymbolSrc AS AtomicSymbol
      ,CurrentAtomCount AS AtomCount
      ,1 AS AtomOrder
      --,'Src' AS BondDirection
      --,IsValidinNist
   FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
   WHERE CanBindSrc = 1
      AND CanBindDest = 1
      AND AtomicSymbolSrc = CurrentAtom
   
   UNION
   
   SELECT DISTINCT Formula
      ,LTAMKeyDest AS LTAMKey
      ,AtomicNumberDest AS AtomicNumber
      ,ElementDest AS Element
      ,ElectronsDest AS Electrons
      ,SlotNumberDest AS SlotNumber
      ,SlotOrienDest AS SlotOrientation
      ,AlphaTypeDest AS AlphaType
      ,SlotSpinDest AS SlotSpin
      ,AtomicSymbolDest AS AtomicSymbol
      ,CurrentAtomCount AS AtomCount
      ,1 AS AtomOrder
      --,'Dest' AS BondDirection
      --,IsValidinNist
   FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
   WHERE CanBindSrc = 1
      AND CanBindDest = 1
      AND AtomicSymbolDest = CurrentAtom
   
   UNION
   
   SELECT DISTINCT Formula
      ,LTAMKeySrc AS LTAMKey
      ,AtomicNumberSrc AS AtomicNumber
      ,ElementSrc AS Element
      ,ElectronsSrc AS Electrons
      ,SlotNumberSrc AS SlotNumber
      ,SlotOrienSrc AS SlotOrientation
      ,AlphaTypeSrc AS AlphaType
      ,SlotSpinSrc AS SlotSpin
      ,AtomicSymbolSrc AS AtomicSymbol
      ,NextAtom1Count AS AtomCount
      ,2 AS AtomOrder
      --,'Src' AS BondDirection
      --,IsValidinNist
   FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
   WHERE CanBindSrc = 1
      AND CanBindDest = 1
      AND AtomicSymbolSrc = NextAtom1
   
   UNION
   
   SELECT DISTINCT Formula
      ,LTAMKeyDest AS LTAMKey
      ,AtomicNumberDest AS AtomicNumber
      ,ElementDest AS Element
      ,ElectronsDest AS Electrons
      ,SlotNumberDest AS SlotNumber
      ,SlotOrienDest AS SlotOrientation
      ,AlphaTypeDest AS AlphaType
      ,SlotSpinDest AS SlotSpin
      ,AtomicSymbolDest AS AtomicSymbol
      ,NextAtom1Count AS AtomCount
      ,2 AS AtomOrder
      --,'Dest' AS BondDirection
      --,IsValidinNist
   FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
   WHERE CanBindSrc = 1
      AND CanBindDest = 1
      AND AtomicSymbolDest = NextAtom1
   
   UNION
   
   SELECT DISTINCT Formula
      ,LTAMKeySrc AS LTAMKey
      ,AtomicNumberSrc AS AtomicNumber
      ,ElementSrc AS Element
      ,ElectronsSrc AS Electrons
      ,SlotNumberSrc AS SlotNumber
      ,SlotOrienSrc AS SlotOrientation
      ,AlphaTypeSrc AS AlphaType
      ,SlotSpinSrc AS SlotSpin
      ,AtomicSymbolSrc AS AtomicSymbol
      ,NextAtom2Count AS AtomCount
      ,3 AS AtomOrder
      --,'Src' AS BondDirection
      --,IsValidinNist
   FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
   WHERE CanBindSrc = 1
      AND CanBindDest = 1
      AND AtomicSymbolSrc = NextAtom2
   
   UNION
   
   SELECT DISTINCT Formula
      ,LTAMKeyDest AS LTAMKey
      ,AtomicNumberDest AS AtomicNumber
      ,ElementDest AS Element
      ,ElectronsDest AS Electrons
      ,SlotNumberDest AS SlotNumber
      ,SlotOrienDest AS SlotOrientation
      ,AlphaTypeDest AS AlphaType
      ,SlotSpinDest AS SlotSpin
      ,AtomicSymbolDest AS AtomicSymbol
      ,NextAtom2Count AS AtomCount
      ,3 AS AtomOrder
      --,'Dest' AS BondDirection
      --,IsValidinNist
   FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
   WHERE CanBindSrc = 1
      AND CanBindDest = 1
      AND AtomicSymbolDest = NextAtom2
   
   UNION
   
   SELECT DISTINCT Formula
      ,LTAMKeySrc AS LTAMKey
      ,AtomicNumberSrc AS AtomicNumber
      ,ElementSrc AS Element
      ,ElectronsSrc AS Electrons
      ,SlotNumberSrc AS SlotNumber
      ,SlotOrienSrc AS SlotOrientation
      ,AlphaTypeSrc AS AlphaType
      ,SlotSpinSrc AS SlotSpin
      ,AtomicSymbolSrc AS AtomicSymbol
      ,NextAtom3Count AS AtomCount
      ,4 AS AtomOrder
      --,'Src' AS BondDirection
      --,IsValidinNist
   FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
   WHERE CanBindSrc = 1
      AND CanBindDest = 1
      AND AtomicSymbolSrc = NextAtom3
   
   UNION
   
   SELECT DISTINCT Formula
      ,LTAMKeyDest AS LTAMKey
      ,AtomicNumberDest AS AtomicNumber
      ,ElementDest AS Element
      ,ElectronsDest AS Electrons
      ,SlotNumberDest AS SlotNumber
      ,SlotOrienDest AS SlotOrientation
      ,AlphaTypeDest AS AlphaType
      ,SlotSpinDest AS SlotSpin
      ,AtomicSymbolDest AS AtomicSymbol
      ,NextAtom3Count AS AtomCount
      ,4 AS AtomOrder
      --,'Dest' AS BondDirection
      --,IsValidinNist
   FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
   WHERE CanBindSrc = 1
      AND CanBindDest = 1
      AND AtomicSymbolDest = NextAtom3
   
   UNION
   
   SELECT DISTINCT Formula
      ,LTAMKeySrc AS LTAMKey
      ,AtomicNumberSrc AS AtomicNumber
      ,ElementSrc AS Element
      ,ElectronsSrc AS Electrons
      ,SlotNumberSrc AS SlotNumber
      ,SlotOrienSrc AS SlotOrientation
      ,AlphaTypeSrc AS AlphaType
      ,SlotSpinSrc AS SlotSpin
      ,AtomicSymbolSrc AS AtomicSymbol
      ,NextAtom4Count AS AtomCount
      ,5 AS AtomOrder
      --,'Src' AS BondDirection
      --,IsValidinNist
   FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
   WHERE CanBindSrc = 1
      AND CanBindDest = 1
      AND AtomicSymbolSrc = NextAtom4
   
   UNION
   
   SELECT DISTINCT Formula
      ,LTAMKeyDest AS LTAMKey
      ,AtomicNumberDest AS AtomicNumber
      ,ElementDest AS Element
      ,ElectronsDest AS Electrons
      ,SlotNumberDest AS SlotNumber
      ,SlotOrienDest AS SlotOrientation
      ,AlphaTypeDest AS AlphaType
      ,SlotSpinDest AS SlotSpin
      ,AtomicSymbolDest AS AtomicSymbol
      ,NextAtom4Count AS AtomCount
      ,5 AS AtomOrder
      --,'Dest' AS BondDirection
      --,IsValidinNist
   FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
   WHERE CanBindSrc = 1
      AND CanBindDest = 1
      AND AtomicSymbolDest = NextAtom4
   
   UNION
   
   SELECT DISTINCT Formula
      ,LTAMKeySrc AS LTAMKey
      ,AtomicNumberSrc AS AtomicNumber
      ,ElementSrc AS Element
      ,ElectronsSrc AS Electrons
      ,SlotNumberSrc AS SlotNumber
      ,SlotOrienSrc AS SlotOrientation
      ,AlphaTypeSrc AS AlphaType
      ,SlotSpinSrc AS SlotSpin
      ,AtomicSymbolSrc AS AtomicSymbol
      ,NextAtom5Count AS AtomCount
      ,6 AS AtomOrder
      --,'Src' AS BondDirection
      --,IsValidinNist
   FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
   WHERE CanBindSrc = 1
      AND CanBindDest = 1
      AND AtomicSymbolSrc = NextAtom5
   
   UNION
   
   SELECT DISTINCT Formula
      ,LTAMKeyDest AS LTAMKey
      ,AtomicNumberDest AS AtomicNumber
      ,ElementDest AS Element
      ,ElectronsDest AS Electrons
      ,SlotNumberDest AS SlotNumber
      ,SlotOrienDest AS SlotOrientation
      ,AlphaTypeDest AS AlphaType
      ,SlotSpinDest AS SlotSpin
      ,AtomicSymbolDest AS AtomicSymbol
      ,NextAtom5Count AS AtomCount
      ,6 AS AtomOrder
      --,'Dest' AS BondDirection
      --,IsValidinNist
   FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
   WHERE CanBindSrc = 1
      AND CanBindDest = 1
      AND AtomicSymbolDest = NextAtom5
   
   UNION
   
   SELECT DISTINCT Formula
      ,LTAMKeySrc AS LTAMKey
      ,AtomicNumberSrc AS AtomicNumber
      ,ElementSrc AS Element
      ,ElectronsSrc AS Electrons
      ,SlotNumberSrc AS SlotNumber
      ,SlotOrienSrc AS SlotOrientation
      ,AlphaTypeSrc AS AlphaType
      ,SlotSpinSrc AS SlotSpin
      ,AtomicSymbolSrc AS AtomicSymbol
      ,NextAtom6Count AS AtomCount
      ,6 AS AtomOrder
      --,'Src' AS BondDirection
      --,IsValidinNist
   FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
   WHERE CanBindSrc = 1
      AND CanBindDest = 1
      AND AtomicSymbolSrc = NextAtom6
   
   UNION
   
   SELECT DISTINCT Formula
      ,LTAMKeyDest AS LTAMKey
      ,AtomicNumberDest AS AtomicNumber
      ,ElementDest AS Element
      ,ElectronsDest AS Electrons
      ,SlotNumberDest AS SlotNumber
      ,SlotOrienDest AS SlotOrientation
      ,AlphaTypeDest AS AlphaType
      ,SlotSpinDest AS SlotSpin
      ,AtomicSymbolDest AS AtomicSymbol
      ,NextAtom6Count AS AtomCount
      ,6 AS AtomOrder
      --,'Dest' AS BondDirection
      --,IsValidinNist
   FROM [Physics].[dbo].[vwAtomicMilesMathisOrbitalsDetailAllBonds]
   WHERE CanBindSrc = 1
      AND CanBindDest = 1
      AND AtomicSymbolDest = NextAtom6
   ) A
INNER JOIN [dbo].[Numbers] N ON N.Number BETWEEN 1
      AND A.AtomCount
where A.Formula not like '%-%'
ORDER BY
    A.Formula
   ,A.AtomOrder
   ,N.Number
   ,A.SlotNumber
   ,A.AlphaType


.
Cr6 wrote. If you do come up with an extended "LTAMKey" would be kind of cool to have a table for each key and "Description" next to the Key value to describe at length what each value represents? Could be done with a code function possibly?
Airman. I'd be happy to oblige but I’m confused, how is a table different from the following?
1. ‘SlotSpin’: (‘ ’, L, R, A, V, E, W, P, Q, M, C).
2. ‘SlotNumber’:1-19.
3. ‘SlotOrien’: (X,Y,Z).
4. ‘Protons’: 0-6. The number of protons in the stack.
5. ‘Electrons’: (‘ ’, T, B, A, V, E, W, P, Q, M, C).
6. ‘StackNumber’: 0-144. Those stacks are found in EPNStacks.csv
Are you suggesting that I put that same information in a table form, then maybe adding more information to each of those data values? Such as the proton spin direction and electron position details for all the R, L, T, B, A, V, E, W, P, Q, M, C  ‘SlotSpin’ and ‘Electrons’ values? How might a 'code function' be intended to operate?

I haven’t run Neo4j since my extended absence. Your image showing the Formula -> Element -> Slot Number added to Neo4j sure looks nice.

Viewing and executing the query to import script for creating a .csv file, ‘CreateNeo4jBonds17Sep.sql’ I see 570,241 bonds. Does the resulting CreateBonds.csv take the place of the previous bond.csv – or is it an alternate bonds.csv file? Also, can you remind me what is the preferred CreateTheElementNodes.csv .sql query is?  


a.Ta:(A2Y6A)-He:(A1Z2A). b. Ta:(B10Z3R)-He:(A1Z2A). c. He:(A1Z2A)-Ta:(T11Z2R).

Concerning the HeTa query output consisting of 10 possible TaHe bonds,
I wrote. How could we tell whether any of those bonds are orthogonal or in-line bonds? The particle coordinates are included, I guess I should try plotting them out?  
Airman. Having thus obligated myself to take a closer look at the possible bonds' particle coordinates, I put together the above mostly autocad image, showing just the proton positions for three possible bonds. Protons within any given stack are separated by 0.3. Electron and neutron positions within each slot are with respect to the slot’s individual protons so I didn't need to include them. He slot1’s center for each bond is at (0,0,0) and is Z aligned with 2 protons at z locations -0.15, 0.15. Ignore the green dots at He (0,0,0). A few values have been rounded for clarity:

a. Ta:(A2Y6A)-He:(A1Z2A). Ta slot2’s (x,y,z) coordinate center is at (0,0,1)) and is aligned to the y axis. Ta slot2’s 6 protons are at y locations: -0.75, -0.45, -0.15, 0.15, 0.45, 0.75.
b. Ta:(B10Z3R)-He:(A1Z2A). Ta slot10 is located at (0,-2,0), aligned to the z axis, with 3 protons at z locations: -0.3,0.0,0.3,
c. He:(A1Z2A)-Ta:(T11Z2R). Ta slot11 is located at (2,0,0), aligned in the y axis, with 2 protons at z locations: -0.15,0.15.

These 3 images show that both Ta and He atoms are centered at (0,0,0) and that the bonding slot coordinates are with respect to their atomic centers. All 10 bonds are treated similarly, as per the coordinate positions included in Elements-Positions.csv.

A little more information is needed before the code could automatically do the rotations and translations necessary in order to display any possible HeTa molecular configurations.

Such as, where is the bond exactly? I suppose the answers might include: the bond between two stack ends; the bond is between one slot’s center and the other slot’s end; or the bond between both slot centers. Those alternatives may be completely identified by a pair of values taken from the set:( -x, -y, -z, -cx, -cy, -cz, cx, cy, cz, x, y, z). The slot ends are +/- x, y or z. The orthogonal bonds at a slot stack's center can be indicated by +/- cx, cy, or cz, depending the direction of the source slot to the destination slot. Of course certain rules apply, for example, a bond at slots 2 and 3 hook positions occur at slot’s 2 or 3 y aligned (y or -y) stack ends. The bond between slot2 and slot4 may be described as between slot 2's, cz center (pointing up) to slot4’s -z (bottom) end. Given our current information, can the database generate one of those 12 values for each of the two bonding slots in any possible bond?

If not, what additional case rules or details need to be added?

P.S.
1. Added -cx, -cy, -cz to increase the 9 slot bonding location values to 12. ( -x, -y, -z, -cx, -cy, -cz, cx, cy, cz, x, y, z). +/- (x, y, z, cx, cy, cz).
2. Corrected b. and c. proton locations to -0.3,0.0,0.3, and -0.15, 0.15.
3. Adding 'a.' before 'Ta...' to the caption.
.

.

8 possible TaHe bonding locations with 14 possible bonds?

Last time I wrote. Given our current information, can the database generate one of those 12 values for each of the two bonding slots in any possible bond?

If not, what additional case rules or details need to be added?

Airman. I need to be more careful asking questions. Hearing no ‘objections’, I’ve continued thinking about identifying the 1 of 12 possible slot bonding sites +/-(x, y, z, cx, cy, cz) for both the source and destination slots in any possible bond.

There are two main types of bonds between protons within and presumably between all atoms: parallel and orthogonal. Any electron accompanied proton (ep) has a low charge field pressure ‘hole’ at which it can parallel bond with another single ep - given a proper combination of electron position and proton spin. Any stack of 1-6 parallel (or parallel and anti-parallel) ep’s has one or more ‘holes’ at which it can bond with another ep stack, in 1. parallel (or anti-parallel), or 2. orthogonally. Orthogonal isn’t necessarily 90 degrees, the ortho-bond can be any angle, just not parallel or anti-parallel.

Currently, the ‘CanBind’ value for any slot in any element in Elements-Positions.csv is ‘Y’ or ‘N’, indicating whether that particular slot’s stack is in a location at which it can bond with another atom. Such as the atom’s hook positions and outermost (+/- x, y, z) slot positions. The ‘CanBind’ value doesn’t provide any information about whether the bond can be parallel or orthogonal.  The ‘CanBindSrc’ and ‘CanBindDest’ values in the ‘Physics’ database formula query outputs are the same, with either 1 or 0, yes no bonding for that slot’s stack, both atoms’ slot stacks must be 1.

I was merely suggesting, in a funny-guy, good-natured, naive kind of way, that the database could simply test for both types of bonds and return each bonding slots’ location and orientation information accordingly. I realize of course that a considerable amount of work needs to be accomplished first. Please pardon me for saying, this looks to me like a database problem.   .

I believe that the set of +/- x, y, z, cx, cy, cz bonding slot values can help provide a way forward.

We really need to work out some bonding logic rules. How do we go about that?

On a separate but related subject, I’ve almost given up on the idea that a vacant bonding hole could be present inside a top/bottom alpha stack. I’m almost ready to ditch all the TB alpha stacks and their internal holes. He isn’t necessarily a TB alpha. That adds to the diagram’s Ta slots 10-15 ambiguity.

I'll say it again, having a separate file containing all possible stacks, EPNStacks.csv, allows more freedom in considering alternate stacks.
.

Hi LTAM,  I think you see it. We would basically need a look up table of sorts for "possible" and "known good" versus "impossible". Yeah outliers always reveal clues. I can re-program the current build in T-SQL. It can be done if you have the "table". Problem with SQL...it is tricky to set yes or no for bonds in a pure 2-D result set. At this point what is "known" good is a lot easier than what is possible. This is one reason I started landing the Chemspider molecules. Break them into individual atoms and the try to re-link them with Miles' structures.

The old electron theory doesn't even get to first base.

By the way, starting to build up more Neo4j with the older style bond layouts:
MATCH p = (m:Formula {Formula: "RbAgO"})-[:Bond_LTAMKEY]->(c:Element)-[:HAS_SLOT]->(r:SlotNumber)
RETURN p LIMIT 10000

Hi LTAM,
I guess where I'm trying to go is if you can give an new "ElementsPositions" type table dump.  I can try and bring it in to the tables with more granularity with what you have working. At the end of the day, I would like to work exclusively from that to build up "bonds". My goal is to represent every known molecule with their respective Atom to Atom bonding. I may also bring in the older "orbital" style bonds into the graph database model just so things can be compared. Still working on the "orbital" style graph "adds". I have it the database so it is just a parse for each atom to each length of traditional values. I'm starting to think that the traditional "bonding" with the "1s, 2s, 2p, 3s...etc". Could be brought in just for comparisons. Still need to get the AtomCount bonds into the model. Right now it is just 1-element to 1-element. If this looks "really wrong" I can reform it a bit.

Might help a few kids out there doing traditional bonding for homework.

Here's another example of "bonding" with the older framework: MATCH p = (m:Formula {Formula: "Br4Pt"})-[:Bond_LTAMKEY]->(c:Element)-[:HAS_SLOT]->(r:SlotNumber)
RETURN p LIMIT 10000

My apologies...let me import the new "Stacks" version and try to hook it up to the slots (from prior work done) in a new table. Keep the old version around still. I'll try to answer your questions above this week as well. Was pretty focused on  getting the bonds with Neo4j working.  As always, still a lot to do and "answer/resolve". Took years and a lot of time to get here...but making advances still. At this point, I just don't want to throw something "sloppy" together and call it good and done.

.
Cr6, thanks for providing your latest project status. Looking good.

My status report is that I’m certain we’re making progress.

Begging your pardon, I’ve been neglecting the charge field atomic modeling project lately, slowing to a near standstill. There have been several real world events and interruptions going on here, plus I must admit I’m obsessed with daily news. Hopefully I’ll be better after the election.

I also beg your pardon for acting unilaterally, making major changes to our working stacks and interrupting your database efforts.

1.  Constant left or right proton spin (L or R), and constant top or bottom electron position (T or B) stacks: TRTRb, tBRBR, tBLBL, TLTLb. These stacks contain a single low charge field pressure ‘hole’ at the top or bottom of the stack, near the electron vacant T or B proton pole.

2. Top/bottom (TB) electron position alpha stacks: TRbtBR, TRbtBL, TLbtBR, TLbtBL.  These stacks may contain dual ‘internal’ opposing and overlapping ‘holes’ and no top or bottom stack holes. The internal holes may, in fact, not be present or 'filled'.

3. Bottom/top (BT) alphas (tBLTLb, tBRTRb, tBLTRb, tBRTLb). These stacks each contain both top and bottom stack end holes.

As we know, one day recently I declared our working stacks, types 1 and 2 above, were wrong, insufficient. They contain too few low charge field pressure holes and cannot form proper Slot Layout atomic configurations.

Clearly the solution was to add 3, BT alpha stacks. The additional stack bonding locations can easily account for all our atomic SL configurations.

Last time I shared some of my TB alpha frustration by threatening to throw out the highly unlikely vacant internal holed alphas. Even though removing the TB stack types’ internal stack gaps from EPNStacks.csv may be correct and necessary, that’s not a good enough reason to throw out TB alpha stacks in their entirety. Even though TB alpha stacks have no stack end bonding holes, single holed (1) constant proton/spin, constant electron/position stacks may still bond (parallel and anti-parallel) with TB alphas’ top and bottom proton ends and so build larger, (up to 6 ep) TB stacks. Furthermore, while it may be true that internal, vacant, TB alpha holes may not be present or filled with another stack’s proton, TB stacks can still ortho bond with (1) or (3) type alpha stacks at the TB stack’s center bonding locations, +/- cx, cy, cz in proper SL fashion.
   
Don’t rush to import the new "Stacks" version, I’m still trying to figure out how to go about building a bonding table.  
.

.

TB stacks without holes. Close-up views of the first 35 stacks of EPNStacks.csv.

Current status. I cleaned up my Jupyter Notebook Charge Field project’s working file – mBuilder15Jun.ipynb a bit and posted it at https://github.com/LtAirman/ChargeFieldTopics under a new name, ElementsAndStacks.ipynb. The main change being, this latest version builds charge field atoms by adding each 1-19 atomic stack according to the number in the data column ‘StackNum’ (the 1-144 stacks are found in EPNStacks.csv) and the slot coordinate location found in Element-Positions4.csv. I also removed the proton separation distances from the gui widget controls. I'll add them again later if/when needed.

The Element-Positions4 ‘AltStacks’ data column does not yet contain any valid values.

Nor have I yet completed my review of Element-Positions4 ‘CanBind’ data column. I get hung up at various atoms. Like 10 Neon Ne. Currently slots 1, 4, 5 ‘CanBind’ = ‘Y’, and slots 2 and 3 ‘CanBind’ = N. Part of me thinks all five ‘CanBind’ slot values should be ‘Y’. I’ve been stuck, mainly thinking about bonding. Including a ‘bonding table’. Maybe something similar to the quote ‘edgy’, triangular chart of ortho-bonds I posted several months ago, but I’m currently boggled and overwhelmed by the idea of 144 X 144 stacks in +/- x, y, z linear and +/- cx, cy, cz orthogonal combinations.

I've made one simplifying change, please let me know if you disagree, after having hinted at it here and given it some thought, removing all the TB alpha stacks’ internal low charge pressure holes - and bonding gaps. For two reasons. First, an adjacent orthogonal stack proton occupying that interior TB stack hole would make it subject to the up to 6 ep TB stack’s orthogonal charge channel from two directions at once – I believe that would keep any proton out of the TB charge channel beam. Second, the proton separation distances within a stack may vary as a function of the surrounding c.f. strength; but the stack protons will always adjust and maintain their minimum spacing according to repulsion between adjacent protons due to their emission fields. I don’t see how a TB stack internal ‘hole’ can maintain a gap larger than the stack’s mutual proton repulsion distance. However, those two objections do not preclude or prevent the possibility of a third type of bond, two orthogonal and intersecting TB alphas, both bonding in a +/- cx, cy, cz single plane, cross-configuration which might be a start for the four directions of a carousel(?). I repeat, its possible(?).

P.S. Just noticed some p2z, h3z and h4z numerical errors, I'll clean them up next.

P.P.S.

TB stacks without holes II – Partial views of the first 41 rows EPNStacks.csv. Correcting proton and hole z-coordinate numerical errors in my image above and prettifying the chart for clarity. The rows are numbered in column A, the number of protons in the stack are in column B. The tan horizontal lines highlight the top rows of the two, three and four proton stack groups. The yellow columns of four different heights show 1, 2, 3 and 4 four proton stack,  protons’ z-coordinate locations. For stacks with an even number of protons (2,4,6), the slot’s two center-most protons straddle the stack’s geometric center (green highlight). In stacks with an odd number of protons (1,3,5), the slot’s geometric center will coincide with the stack’s center proton (no green highlight).
.

I have something loaded with "Traditional Bonds" now. May need to tweak it a bit to line up the "Orbitals" by "ring". Just wanted to make this to compare Miles' and the LTAM Key with Traditional Bonding. This is Neo4j. Want to be able to line up Trad Bonds with Miles on a 1-1 level to allow cross queries between structures. Note this is basic 2-D for now. Could possibly bust out the TradElement to the actual old periodic table child bonds (1s, 2s, etc.):

Code:

//Build relationship based on Element Trad export
MATCH (a:ElementTraditional)
MATCH (b:Element)
WHERE a.AtomicNumber = b.AtomicNumber
MERGE (b)-[:HAS_TRAD_BOND]->(a)
RETURN a,b;

MATCH p = (m:Formula {Formula: "Br4Pt"})-[:Bond_LTAMKEY]->(c:Element)-[:HAS_TRAD_BOND]->(d:ElementTraditional)
RETURN p LIMIT 10000

Here's Li and Au (Gold) which I see as another "strange" bond outside of Miles: