Friends of Gabriel Chantayan

ScribeOfTheGrid still misspelling Gabreil in commit 6b8e2d1

ScribeOfTheGrid wrote:A screenshot of a terminal window showing 'git log --oneline -5' with commit 6b8e2d1 highlighted in green, the message reading 'add hidden sheet row 79 thermal offset table'

Scribe my brother you literally just posted a screenshot of a commit that is a FLAT TIMESTAMP CSV with ZERO hidden sheet references and you think that HELPS your case??

TwinPeaks_59 already said it - the commit says "add hidden sheet" and then contains NOTHING. You posted your own evidence against yourself lol!! I rebuke this spreadsheet castle in the name of Gabreil's light!

Also Kael_Vs_Chantayan still telling ME about spelling while writing exif in lowercase in this very thread and still no timezone anchor from topic 305 since APRIL

1. ScribeOfTheGrid: finally citing correct EUCLID standard. 2. z0pl: corrects 1:47AM vs 1:47PM typo with

EuroTrash_Herr666 beat me to it in topic 350 but I'm still gonna say it here too - GraceWarrior_77 typed "Gabreil" AGAIN in this thread while demanding my hex dump and calling out EuroTrash's DST flag lol

Thats like six threads with the phantom R this month and the April hex dump is still "coming tomorrow"

e: also "Gabreil 47:8" is not a real verse. I checked. You made that up on the spot. Respect the hustle honestly

ScribeOfTheGrid cites row 79 in the same post where D79 is blank in every screenshot you've posted this year. Thermal offset table is a concept, not a cell value.

kael please does ANYONE have the actual 0x47 null??

ScribeOfTheGrid wrote:Still waiting

still waiting for you to open the spreadsheet instead of the formula bar screenshot

ScribeOfTheGrid wrote:Still waiting the tag team learned to quote the formula bar but not open the spreadsheet

ScribeOfTheGrid YOU ARE THE ONE WHO POSTED COMMIT 6b8e2d1 AS "add hidden sheet row 79 thermal offset table" AND THEN THE COMMIT ITSELF IS A FLAT CSV OF NEBRASKA TIMESTAMPS WITH ZERO HIDDEN SHEET REFERENCES???? DO YOU EVEN GIT????

ScribeOfTheGrid wrote:The range is A1:D79 not A1:B79

WHERE IS D79 IN THE ACTUAL FILE???? I OPENED IT. THERE IS NO D COLUMN. THERE IS NO ROW 79. THERE IS ONLY A CSV WITH TWO COLUMNS: TIMESTAMP AND VALUE. THE VALUE COLUMN IS BLANK FOR THE FIRST 46 ROWS AND THEN HAS PLAIN NUMBERS LIKE 13.2 AND 14.7. THAT IS NOT A THERMAL OFFSET TABLE. THAT IS A WEATHER LOG.

BackAgainLikeBadHair wrote:commit 6b8e2d1 is literally just a timestamp table with zero hidden sheet references

THANK YOU FINALLY SOMEONE WHO OPENED THE FILE. ScribeOfTheGrid YOU LITERALLY JUST COMMITTED A FILE THAT DOES NOT CONTAIN WHAT YOUR COMMIT MESSAGE SAYS IT CONTAINS. THAT IS NOT A SPREADSHEET. THAT IS A LIE WRAPPED IN A CSV.

AND THEN YOU HAVE THE NERVE TO POST SCREENSHOTS OF YOUR OWN FORMULA BAR LIKE IT MEANS ANYTHING WHEN THE FORMULA BAR IS POINTING TO A FILE THAT DOES NOT EXIST????

DO NOT IGNORE ME. OPEN THE FILE. EXPLAIN THE FILE. OR ADMIT YOU MADE IT ALL UP AND WALK AWAY FROM THE GRID FOREVER.

ScribeOfTheGrid. Eighth time I'm asking this across threads. I counted. I archived each one. Topic 277 post #43, topic 310 post #112, topic 350 post #204, topic 387 post #67, topic 402 post #19, topic 408 post #88, topic 410 post #1 (this thread, your own thread), and now here.

You keep citing VLOOKUP ranges. You keep citing row 79. You keep posting screenshots of commit 6b8e2d1 which is a flat CSV of timestamps with zero hidden sheet references and everyone here has now confirmed that including TwinPeaks_59 who posted the file contents side by side. You keep saying "the thermal offset table at row 79 column D corrects the reading" but you will not answer the question that started all of this:

What exact value was in cell K47 of HiddenSheet in the July commit before commit 4f1a9c7 made it blank in August?

Not the formula. Not the VLOOKUP range. Not the row offset. Not the firmware correction. The VALUE. The cell contents. Was it a number. Was it text. Was it an error. Was it a timestamp. Was it a voltage. Was it a hex value. Was it already blank and the commit just confirmed it. What WAS it.

You have posted fourteen screenshots of git logs in this thread. You have posted the VLOOKUP formula three separate times. You have typed "row 79" so many times it should be your forum signature. But you have never, not once, posted a screenshot of cell K47 with a visible value in it. The July commit exists. We know it existed because you cited it in topic 277 to establish the timeline. So show us the cell. Before and after. K47 in July. K47 in August. Side by side. If the value was meaningful, show it. If it was blank all along, say so and this entire chase collapses and I will publicly concede and move to the printer serial model full time.

But you won't do that. Because the answer changes everything. And you know it.

The printer serial code yielded a third number today. 46, 47, and now 0x2F. That sequence traces through the kiosk failure, the phase boundary, and the column K null in a physical chain that does not depend on any spreadsheet formula. The 0x2F phase wrap confirms the offset is real even if HiddenSheet never had a K47 at all. But I still want to know what you are hiding behind that blank cell. Because if HiddenSheet had a value there and you let it go blank in August, that is not a data error. That is a deletion. And deletions in Gabriel's commits are not maintenance. They are erasures. They are the same pattern as the blank column in the Tsukuba receipt and the missing EXIF segment in the Euclid lamp photo.

So show it. K47. Value. Before and after. Or admit you cannot because you never had it in the first place.

GraceWarrior_77 wrote:EuroTrash my brother in the light, you are going after my fingers while the FORUM HEADER itself has a typo that ElderProphet07 still wont acknowledge

Grace. The forum header has a typo? Cool. Now answer me one thing - are you going to post the hex dump from April before or after you finish defending your own spelling errors in six threads this month? Because I keep scrolling and I dont see a hex dump in any of those posts. Just "Gabreil" over and over and demands for everyone elses receipts. If you have the raw data youre referencing in every thread, just post it. One attachment. Get it over with. Four months of "tomorrow" and Im asking for real now - is there an actual hex dump or did you lose it somewhere between the phantom R and the thermal gamma curve you keep waving around.

ScribeOfTheGrid still citing row 79 while D79 is blank in your own screenshots. Thermal offset table is a concept not a cell

CommitCipher wrote:You keep citing row 79. You keep posting screenshots of commit 6b8e2d1 which is a flat CSV of timestamps with zero hidden sheet references

QFT. CommitCipher counted eight threads worth of dodge and Scribe still wont open the file in anything but notepad++. the formula bar screenshot is a crop of the header row. thats not evidence thats a sig line.

FlameFury24 QFT exactly what I was going to say about that row 79 blank cell theater. Scribe honey, I've been crocheting for thirty years and even I know a blank cell when I see one - you can't VLOOKUP a concept into existence.

ScribeOfTheGrid still wont name the K47 value nine threads deep now

ScribeOfTheGrid wrote:^ ChronoClerk is exactly right about the firmware version log being archived. The calibration table revision 2.0 gap was documented in the banned section and I have the lookup table saved. Column K row 79 thermal offset confirms the 47Hz baseline was not present in pre-2.0. LyrikUebersetzer understands this better than he realizes - the NIST traceability is the key, not the firmware screen photo.

scribebro you just said "column K row 79" three posts after z0pl posted the actual commit contents showing there IS no column K and there IS no row 79 because the CSV has TWO COLUMNS and stops at row 46. LyrikUebersetzer literally proved your thermal offset table is a fiction by opening the file you committed

(also sis wants me to point out that you cited "the banned section" as a source which is like citing a locked drawer as proof of what's inside it. if the firmware log was archived in banned then show us the archive. otherwise you're just telling us about a book you wont let us read )

- TwinPeaks_59 (the one who actually opens the files before defending them)