>>4617

Isee, I've been working through this and get the attached image, working backwards.

Some interesting geometries there, with the 8 squares around the centered unit square.

Just a way to picture our original layout, with a specific solution for c=259.

>>4618

>>4619

Also, note other image attached (taken from the Wolfram page Isee *linked), remember the CONWAY hint?! I'd been looking into that particular Conway and Guy book too, ding ding.

BTW, regarding hints that came with that CONWAY one, VQC mentioned "asymmetric warfare". Have been thinking maybe this is asymmetric, as in "Asymmetric Encryption" algorithms = "Public Key Encryption"?!

>>4620

Here is the same, with b added, and the [e,n,t] record label of [3, 6, 2] = {3:6:16:9:7:37}.

It's just the top part of the L, added over to right of the box. Can quickly see geometrical derivation of b=a + 2x + 2n.

Tonight I'll run this through VQC's latest crumbs to check flow of everything (n0, etc.)

>>4621

Suspect the (8) unit blocks surrounding the Orange centered unit, will be the (8) n0=1 pieces. That should give an offset for x from the center unit, that produces a=7. Need to review, just looking geometrically.

If n0=3, it would be shifted 2 blocks (5x5=25, 25-1=24, 24/8=3). If n0=6, it would be shifted 3 blocks (49-1 = 48, 48/8=6).

>>4611

Yo Topol, don't be all butthurt on us. We'll be here when you fire up that tab - you know you can't resist the pathfag VORTEX!

>>4624

Thanks. I think the Pyramids VQC illustrated may be a bit different though, as the 'caps' above the f are (n-1), (6-1)=5 in this case (think that's area). So that's the type of thing to keep going with and work out. Just sharing some progress along the way with integrating the new drops.

>>670

^^ this shows how I'd originally understood the whole "L" thing, which really makes sense, including the odd unit up in the corner.

>>4626

Great new MAP! Had just finished getting all the new drops in a text file.

>>4627

Thanks, inspired by you actually.

>>4630

Cool, will look at that tonight. Here's what I mean by the n0, shown in yellow for c=259 where n0=1, and it disappears in c=287 (n0=0).

That's why I'm figuring n0 progresses in a certain way (2*n0+1)^2-1=n0(8), which are the blocks around the center (1) unit block.

So n0(8)=0, n1(8)=8, n2(8)=24, n3(8)=48, …

>>4632

Love you too, glad you got over it. Sorry to piss on you's parade, hope it didn't dampen spirits too badly!

>>4513 and a Kek from me too, that was just perfect, like, the best.

>>4639 >>4641

How about we use 6107? I'm sketching that one now.

{23:36:78:47:31:197} = 6107 (da answer)

{23:2976:78:77:1:6107} = 6107 (known)

f = 134

(f - 2) = 132

Started by trying to iterate, going to sketch the solution and see if we can back into it? This one appears to have a remainder situation as well.

>>4645

re: n0, PMA calced as n0=6. Sketching the actual result, it looks as if n0=5. That adjustment might be part of the process.

Am still working through the triangles around the unit cell and the n0 region. I think they are supposed to go right to the unit cell, and get 'clipped' by the n0 region. But, it could also be that they go up to the outside of n0. Showing both scenarios for the orig c=259 case.

Next, want to do a sketch of what we would start with, with the initial guess, before any triangle adjustments (and before actual n or x is known).

>>4647

Interesting! Starting with your values, the initial was too large by 1108, which /8 = 138.5. That was with a large square of 88 and small of 23 (basing off your init triangle calc). So Lg^2 - Sm^ = 7744-529 = 7215, which is too large by 1108, (7215-c = 1108).

I like the block triangles Isee and Teach were doing, shows the actual units that get cut off inside the n0 region.

>>4656

Nice effort AA.

>>4650

Block UI's would be interesting for medium demo numbers, probably good as teaching tool. I'm really hoping we aren't in this proto middle-land stage too long!

>>4653

>>4654

Ok, I'm following what you're saying there with the incremental for each row with growing triangle numbers. And I need to watch area vs base as well, think that's mucked up in these.

>>4657

Will be great to know how the factor tree ties in!! Those look fantastic.

>>4649

Here was the first "iteration" attempt. Took the (f-2)=132. So we have 16 with 4 units left over. This is where I think it's the wrong step for me. Used n0=6. We know D, so created the D square, inclusive of the n0 square, and used that to finish out the rest of the geometry.

1) Am not sure d is drawn in correct way in this case. Perhaps it should be going to the Inside of n0 square, bottom left corner?

The idea here was to take the first pass, and see the gap. Not sure that's a valid record, didn't check yet. Probably not, because the remainders "haven't been taken into account".

Will play for another 45min or so.

>>4659

Awesome! Ha, I was sitting here imagining the d square, with e hugging around it (incomplete, or you'd go up to next d). Then, a notch shows up in the upper right and the e blocks scatter to each side, meeting their new friends pouring out of the notch, until all is balanced and well with the world.

>>4660

Thanks for the encouragement. Won't last much longer today, but going through it from beginning to see what sticks. Will dream of triangles later for sure.

And wow, what a day for Q! Big drop on the cellular tech, amazing what classified stuff is getting dropped: #NoMoreSecrets !!!

>>4663

Indeed. Think ball is just getting rolling. Did you see Newsweek clip today, and the reader comments? It was an interesting play with an 'out there' kicker by AJ at the end (just to keep normies in discount mode). 911 narrative right there and interviewer only went after Sandy bit. Hmmm.

>>4661

Thanks VA! Yes, went back to orig diagrams and all looks good, incl where 'a' is for width of L.

>>4658

This isn't valid. Calculating what was produced: {23: __ :78:23:55:121}, solving for 'n', it would have to be 12, not 10. The x, a, and d all worked fine though. So, just drawing a geometry doesn't mean it all 'adds up'!

>>4649

Attached is center detail for the actual solution to this one. The n0=5, meaning 5 units away from the center cell, so 120 cells + center = 11^2.

Am starting to get an intuition/visual about how these pieces move and grow and shift. So the d is a lock, therefore the top and right of the n0 box are a lock. As n0 grows, it 'pulls' the (x+n)*(x+n) square with the 8 triangles in for a deeper cut, causing x to grow in the process.

And here's the image - browser is suddenly lagging big time. Reboot time.

>>4651 VA, thanks for the meme btw! Been thinking about the spice lately. If there are entities about, would be nice to hop on their wavelength, been a while.