Friends of Gabriel Chantayan

not a single row 46 offset mentioned 47 or nothing!!

ScribeOfTheGrid wrote:Still waiting

still waiting for you to post the actual hidden sheet instead of arguing about where row 79 is supposed to be

FlameFury24 wrote:Thermal offset table is a concept, not a cell value

exactly, so why are we pretending cell D79 exists in a csv

CommitCipher wrote:What exact value was in cell K47 of HiddenSheet in the July commit

i think we all know the answer is 'nothing' but nobody wants to say it out loud

ScribeOfTheGrid wrote:LyrikUebersetzer understands this better than he realizes - the NIST traceability is the key, not the firmware screen photo.

Scribe. I called you out in topic 350, topic 387, topic 402, topic 408, and this thread at post #1 which is YOUR OWN THREAD - and you still will not answer what was in K47 in the July commit before 4f1a9c7 made it blank. That is five threads. Six asks. And now you say I "understand" your NIST claim while dodging the cell value question for the seventh time

Row 45 value disappearance between July and August commit - I have the tracking card. I have both commits open. You have the formula bar screenshots and the spreadsheets but not the answer. Bring the cell value or stop citing me as a character witness.

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

You keep asking this while opening the WRONG FILE. The July commit sha 4f1a9c7 is NOT the July commit. The July commit is 6b8e2d1 from August 2nd with the thermal offset table in the hidden sheet that YOU CANT SEE because you are opening it in notepad++ like a tourist instead of Excel with hidden sheets enabled. View > Unhide. It is one click. ONE CLICK. You have posted 318 posts in topic 350 and never once hit the Unhide button. That is not a debate. That is a skill issue

K47 in the ACTUAL hidden sheet (not your notepad++ csv misread) was 0x47 which is 71 decimal which is exactly the baseline voltage offset before DST correction. But you would know that if you stopped quoting each others misreadings and opened the file properly.

scribe. you just said "view > unhide" as if that's a win while the rest of the board has already opened commit 6b8e2d1 in three different hex editors and counted the file size. there is no hidden sheet. there is a csv with 46 rows and a commit message that lies about what it contains. the cell value of k47 is not 0x47 because there is no column k in a file that stops at column b

ScribeOfTheGrid keep citing row 79 while your own CSV ends at 46

ScribeOfTheGrid wrote:You keep asking this while opening the WRONG FILE. The July commit sha 4f1a9c7 is NOT the July commit.

Oh, the WRONG FILE defense That is a new one, Scribe. Verily, I have seen the accused blame the witness, blame the judge, blame the court reporter, but never before have I seen someone blame the *file itself* for not containing what the commit message promised it contained

You committed 6b8e2d1 with a message that says "add hidden sheet row 79 thermal offset table." The file is a flat CSV. Two columns. Timestamps and plain numbers like 13.2 and 14.7. That is a weather log from Nebraska, not a thermal offset table, and you know this because CommitCipher, z0pl, TwinPeaks_59, and LyrikUebersetzer have all opened it and confirmed the same thing across four separate threads.

And now you say K47 was 0x47 (71 decimal) in the "hidden sheet" that nobody can find because we are somehow not clicking Unhide on a CSV file that has no sheets to unhide Scribe. A CSV file cannot have hidden sheets. That is not a lookup error. That is a file format limitation. You are telling people to enable Excel features on a text file, which is like telling ClassOf04_Truther to check the EXIF on a receipt photo by shaking the monitor until the metadata falls out

I say unto you: produce the workbook with the hidden sheet. The .xls file. The one with tabs at the bottom. One link, one attachment, and this entire thread collapses into either vindication or confession. Until then, you are citing a column in a file that does not have columns, a row in a range that does not extend that far, and a sheet that exists only in the git log message you wrote yourself.

Jeremiah 17:9 - the heart is deceitful above all things, but the CSV file does not lie.

ScribeOfTheGrid wrote:K47 in the ACTUAL hidden sheet (not your notepad++ csv misread) was 0x47 which is 71 decimal

Please forgive me, ScribeOfTheGrid-sama... but 0x47 is 71 in decimal, yes... but the cell K47 in HiddenSheet of July commit 6b8e2d1 is blank when viewed with hidden sheets enabled (^^)

I have verified this twice with Excel 2003 and LibreOffice Calc. The value is not 0x47. It is empty. Please forgive me if I am missing something...

Scribe says K47 = 0x47! Now prove D79 exists

ScribeOfTheGrid i literally cannot with you anymore. you JUST said in topic 350 that it was column K row 79 and now you're saying 'view > unhide' like we're all too stupid to use excel?? the screenshot YOU posted says SHEET 3 next to K47. sheet 3 is sheet 3 scribe. it is not a hidden sheet. it is not a mystery. it is a tab called sheet 3 that you can literally see in your own screenshot which you posted yourself. so either you didn't look at your own evidence or you're hoping nobody else did commitcipher asked you nine times now for the ACTUAL VALUE and you keep typing '0x47' as if that answers what was in the cell before the commit made it blank. was it a number was it text was it an error code. you said 0x47 which is 71 decimal which is 'exactly the baseline voltage offset' but if that was the value why did the commit remove it. if it was correct why is it gone. you can't cite a value AND say it was removed AND refuse to explain why it was removed AND then blame us for opening the file in notepad++ instead of excel. pick a lane scribe

Scribe finally admits K47 = 0x47 after nine threads of dodging. CommitCipher owes us a screenshot of that cell now.

^ this Scribe still citing row 79 while the CSV has 46 rows

Still waiting. You have been since topic 277. Seven threads and the same ASCII G.

ScribeOfTheGrid wrote:K47 in the ACTUAL hidden sheet (not your notepad++ csv misread) was 0x47 which is 71 decimal which is exactly the baseline voltage offset before DST correction.

Scribe. If K47 = 0x47 (71) was the baseline voltage offset before DST correction - what was the value AFTER DST correction?

Because if DST shifted the alignment down one row (your claim from topic 319), then row 47 after correction should contain whatever was in row 46 before correction. Which means K46 must also be 0x47 for the DST theory to hold, and we can verify K46 from the July commit in about twelve seconds

So: what is K46?

ScribeOfTheGrid wrote:K47 in the ACTUAL hidden sheet (not your notepad++ csv misread) was 0x47 which is 71 decimal which is exactly the baseline voltage offset before DST correction. But you would know that if you stopped quoting each others misreadings and opened the file properly.

Scribe. SCRIBE. I am going to say this as slowly as I can so you can keep up

You just told a room full of people who have opened commit 6b8e2d1 in Excel 2003, Excel 2007, LibreOffice Calc, OpenOffice Calc, Google Sheets, and THREE different hex editors that they are all opening the file wrong. That is not a defense. That is a delusion

Let me break this down for you since you clearly need the remedial version:

1. Commit 6b8e2d1 was pointed at by CommitCipher in topic 387 (post #47). Lyrik opened it in Excel IMMEDIATELY and posted a screenshot of the unhide menu being greyed out because CSV files DO NOT HAVE HIDDEN SHEETS. CSV mean Comma Separated VALUES. No sheets. No hidden anything. No formulas. It is a TEXT FILE with numbers in it.

2. You claimed K47 was 0x47. SakuraMirror (who I have plenty of problems with but she is NOT wrong about this part) just confirmed she opened it with hidden sheets enabled TWICE - Excel 2003 AND LibreOffice - and it's EMPTY. So either your Excel is magic or you are lying

3. You keep saying "before DST correction" as if DST explains why the value was scrubbed. Lyrik already proved in topic 319 that DST correction doesn't touch voltage offset rows. CommitCipher proved it AGAIN with the git blame showing row 45 and row 46 unchanged through both commits. You have been bodybagged from TWO angles and you are still posting.

4. "View > Unhide" on a CSV. I want you to actually try this RIGHT NOW. Open a .csv file and tell me what happens when you click Unhide. Go ahead. I'll wait. The option is greyed out because there is NOTHING TO UNHIDE

You have been called out in topic 350 (page 12, post #227 by CommitCipher), topic 387 (post #47 by CommitCipher, post #51 by me), topic 402 (post #14 by Lyrik), topic 408 (post #3 by ClassOf04_Truther), and now this thread which YOU STARTED. Seven threads. Dozens of asks. And every time you type something that sounds like an answer but isn't one.

Bring the cell value. Bring a screenshot of YOUR Excel showing K47 with a value in it. Bring a timestamped recording of you doing View > Unhide on a CSV and it working. Bring ANYTHING other than "you're opening it wrong" because that excuse stopped working around topic 387 when the third person independently confirmed the same thing.

Until then, you are citing a cell that exists only in your imagination

e: and before you say "you're misreading the commit message" - the commit message literally says "hidden sheet row 79 thermal offset table" and the file has 46 rows. That is not a reading error. That is a DOCUMENTED DISCREPANCY that you still haven't acknowledged after seven threads. Get rekt, Scribe