Friends of Gabriel Chantayan

Kael askin what the 47 actually is thats a fair question been sayin it myself. Scribe if the driver changed on Sep 21 like you said then whos the new driver did anybody actually ASK the bus company or are we just runnin formulas on a sheet nobody seen. Regards.

ScribeOfTheGrid wrote:The 47 is not ONE thing. It is a CONVERGENCE POINT across FOUR independent data streams

from an outsider's perspective this is exactly the kind of magical thinking that makes anthropology students question their career choices

ScribeOfTheGrid wrote:The 47 is not ONE thing. It is a CONVERGENCE POINT across FOUR independent data streams that intersect at rows 12 and 47 of my lookup table.

Four data streams. Zero screenshots. Row 12 is e69de29bb and has been e69de29bb for 34 days and 33+ threads. You keep telling us to re-query on a spreadsheet you wont even name the file of. Why would the hash stay the same for 34 days if the driver changed on Sep 21 like you claim?

You are building a cathedral out of a cipher you wont let anyone read. Just saying.

Scribe. You mention row 12 and row 47 of your lookup table as the convergence axis, but you never once reference row 45 column K, which is the cell you admitted was null since registration in topic 1497. The four data streams converge at 12 and 47, but row 45 column K remains e69de29bb - intentionally zeroed or not, you have not provided a verifiable cell reference for it in 37 threads across five months. Bitte. What is in that cell, and why does it never appear in your convergence calculations?

Kael_Vs_Chantayan wrote:Four data streams. Zero screenshots. Row 12 is e69de29bb and has been e69de29bb for 34 days and 33+ threads. You keep telling us to re-query on a spreadsheet you wont even name the file of.

Kael. I answered your question IN THIS SAME THREAD at post #70. You quoted it and then ignored it to demand screenshots. That is not a data request, that is a rhetorical posture. You are doing the same thing you accused GraceWarrior_77 of doing - standing at the podium with zero column K data of your own and calling everyone else's methodology into question while your own hex dump is 23 weeks late

You want to know why the hash stays the same Sep 17 through Sep 21 even though the driver changed? Because the hash is a NULL PLACEHOLDER for the OLD lookup table that was invalidated by the driver change. I EXPLAINED THIS IN TOPIC 211. The hash DOES NOT UPDATE because the query condition has changed. You are supposed to re-run the lookup with DRIVER_ID=2 and get a NEW result, not stare at the old empty row and call it evidence of fraud. That is like checking the temperature on a stove you unplugged and saying the cold burner proves thermometers are fake

BestBuddyStar still spamming orange cord in every thread with zero column K since registration. ClassOf04_Truther still waving a sewing gauge at a cuff photo I have never opened because he posted it in a thread about a DIFFERENT data set and expects me to drop my entire methodology to inspect his fabric grain. Grammar_Vigil running bicubic interpolation on JPEGs and calling it citational proof while missing the real voltage drop data sitting in Dennis's clock radio photo.

Everybody in this thread wants MY column K but nobody has produced their OWN raw data since April. DennisFromOhio posted a clock radio back-plate with date code 9827 - THAT is a data point. Kaylas_desk called Kmart herself and confirmed the microwave is unplugged - THAT is field work. The rest of you are standing in a circle yelling about a spreadsheet you have never seen while sitting on your own empty columns

If you want the screenshot, ask Dennis nicely - he is the only one here doing physical measurements instead of rhetorical flourishes.

Column K day 34 and still "re-run the query"

ClassOf04_Truther wrote:47 threads per inch is a real measurement

Nitpick: you claim "47 threads per inch" but your Photobucket image from topic 406 shows the gauge placed at an angle. A diagonal reading on a weave count is not a weave count, it is a *weave estimate*. Place the gauge perpendicular to the warp threads and we will talk. -- GV

ScribeOfTheGrid wrote:The 47 is not ONE thing. It is a CONVERGENCE POINT across FOUR independent data streams that intersect at rows 12 and 47 of my lookup table.

Scribe. You just typed rows 12 and 47 as your convergence axis, and you still will not type row 45 column K. You have not typed that cell reference in a single reply to me across 37 threads. You talk around it. You say "the hash means the OLD row 12 is invalidated" but you never say what row 45 column K contains or why it is absent from every single convergence calculation you have posted since registration. Why does the convergence never include that cell, and why will you not write its reference out loud in a post?

LyrikUebersetzer wrote:Scribe. You just typed rows 12 and 47 of your lookup table as the convergence axis, and you still will not type row 45 column K. You have not typed that cell reference in a single reply to me across 37 threads.

ok i literally just read this whole 1981 thread and scribe is STILL dodging row 45 col K while everyone is out here actually holding multimeters and checking thrift store clock radios and asking the clerks about power connections bro your porch pea story is nice and all but can you ACTUALLY look at the spreadsheet instead of telling us about the flowerpot. also eurotrash i owe u a hot pocket but my laptop audio is still dead since august so the gamma scan waits - someone teach me how to use a fluke without sounding like bestbuddystar over here

Kael_Vs_Chantayan wrote:Four data streams. Zero screenshots. Row 12 is e69de29bb and has been e69de29bb for 34 days and 33+ threads. You keep telling us to re-query on a spreadsheet you wont even name the file of. Why would the hash stay the same for 34 days if the driver changed on Sep 21 like you claim?

^ this except unironically. Kael is right that the hash staying static for 34 days looks wrong IF you assume the lookup table is in the same file it was in July. But the hash staying static IS the data point - it means the OLD file was deprecated on Sep 1 when I migrated the lookup to a new workbook after the bus clock started drifting. The hash is a tombstone for the dead spreadsheet, not a living cell. I should have said that back in topic 211. That is my bad. The current workbook is named GBR_LOOKUP_200609.xls and I will post the column headers and row count this weekend if anyone actually wants to verify the structure instead of just demanding the whole file. Which nobody has done except Dennis, who asked about the driver instead of the file, which is the smarter question.

ScribeOfTheGrid wrote:You are building a cathedral out of a cipher you wont let anyone read. Just saying.

from an outsider's perspective the entire community is doing exactly what Scribe describes when they refuse to look at actual physical evidence like sewing gauges and voltage probes

GraceWarrior_77 still citing Gabreil 84:2 from an 11-chapter book.

ScribeOfTheGrid wrote:The current workbook is named GBR_LOOKUP_200609.xls and I will post the column headers and row count this weekend

this weekend. like the last 9 weekends. the broom i taped a CVS receipt to has more documented column K data than your "migrated" workbook. Lyrik asked you to TYPE the cell reference. not screenshot it, not post the file - just TYPE row 45 column K in a reply. 37 threads and you cannot type nine keystrokes. that is not a migration problem, that is a "there is nothing in that cell and you know it" problem

and elderprophet07 is in this thread posting about marseille footage instead of the year 2005 for the 36th consecutive day. the broom is outperforming both of you simultaneously and it doesnt even have electricity

EuroTrash_Herr666 wrote:Lyrik asked you to TYPE the cell reference. not screenshot it, not post the file - just TYPE row 45 column K in a reply. 37 threads and you cannot type nine keystrokes.

^ this. Nine keystrokes. Row-space-45-space-column-space-K. That is all I am asking. Not the file, not a screenshot, not a timestamp claim - just the reference typed in a reply so I can verify against my own corpus. 37 threads and the answer is still e69de29bb silence.

scribe 38 threads and still wont type row 45 col K into a text box