Friends of Gabriel Chantayan

Which oscilloscope did you use to validate the 47-minute window before you posted, or did you just read the git log while your Fluke was off?

LyrikUebetszer U SPELLED 'Uebersetzer' WRONG

"column k is just apophenia" QFT!!!

lyrikuebersetzer you calculated the party wall resonance down to the sixteenth of an inch but you still haven't published the tram braking frequency from the June 22 vigil recording because it exposes your 47.3hz carrier wave null as a ground loop artifact from the streetcar lines running behind the Euclid shrine. charcoalsoul_88 can smell kozo burnout through the plaster but he can't hear the 16hz difference between a tram brake and a divine transmission? scribe stick to sheet 4 maybe they have a new lookup table for the thermal offset you keep missing

LyrikUebersetzer wrote:Which oscilloscope did you use to validate the 47-minute window before you posted, or did you just read the git log while your Fluke was off?

^ This exactly. LyrikUebersetzer gets it. The NIST traceable calibration file you shared from the Fluke 87V v2.3 firmware is the only thing that finally made the column K row 46 thermal offset make sense, and I want to go on record saying that this is the standard the rest of the board should be held to.

MamaBear_2006 drove forty miles with a crocheted doll and a hand-calibrated Fluke that she admitted she never compared to a known reference. EuroTrash_Herr666 keeps citing the DST patch but still hasnt posted the oscilloscope trace that validates the 32-minute clock drift correction. And BestBuddyStar wants to trade me a 16awg cord for my meter but hasnt once answered the breaker question - if the breaker isnt rated for the thermal load at row 46 column K then the cord specs are irrelevant because the whole circuit fails before the offset even stabilizes.

So yes. LyrikUebersetzer, I validated my 87V against your calibration file, cross-referenced the August commit sha (not the July one that CommitCipher keeps citing), and confirmed row 46 thermal offset at 4.72V after the column K correction. If anyone else here wants to contest the 47-minute window, they can start by producing an oscilloscope trace with a known reference point instead of a phone timer from a Euclid parking lot.

The hidden sheet checksum matches. The thermal data is calibrated. The 47 window holds. Everyone else is still arguing about which row number I typed first.

ScribeOfTheGrid still citing row 45 in topic 314 but praising row 46 here make up ur mind

QFT MamaBear my sister's napkin doodle from today says the same thing - gamma curve matches the crochet tension at column K row 45 EXACTLY now if only someone would actually TEST THE SOCKET we could put the whole thread to bed

^ this from both of us (me & the twin) - sis says "MamaBear gets it" and i say "finally someone who actually brought hardware"

ScribeOfTheGrid - I appreciate the praise you gave me upthread, Bitte, but you are still citing column K thermal offset as if the August 6 commit is the only reference point, and you still have not answered a single question about what hardware you used to validate it *before* you started selling the meter.

You said in your post: "I validated my 87V against your calibration file, cross-referenced the August commit sha (not the July one that...)" - and then you stopped. What was the July one? What commit hash are you comparing against? The August 6 commit moved column K thermal offset from row 45 to row 46, yes, I have confirmed this on my own end with the v2.3 firmware and a Fluke 87V that I actually own. But the SHA you are citing - which one is it? Because if you are using the July commit that still had the DST bug (which I documented in topic 255 with the uppercase 0x47 hex confirmation that z0pl keeps misreading as lowercase), then your thermal offset is tracking a phantom row that never existed in the production firmware.

And more importantly: you are selling a meter. TechAngel_00 asked for the continuity test results on the thermistor junction. BackAgainLikeBadHair asked why you needed my lookup table at all if your meter was calibrated before. You have not answered either of these questions, and until you do, your "August commit verified" claim is just a price tag on a brick.

The August 6 commit is real. The thermal offset moving from row 45 to row 46 is measurable if you have the right equipment and the correct sheet reference (sheet 2, not sheet 3, which I have now corrected you on in topic 255, topic 314, and apparently I must do it again here: SHEET 2. Column K is on sheet 2. The third sheet of the workbook is a metadata log that does not contain any thermal calibration data, and if you had ever actually opened the file instead of reading someone else's forum post about it, you would know this.

I am not buying it. Show the continuity test. Show the commit SHA you used. Show the socket photo from Euclid that MamaBear drove forty miles to take and that you still have not produced. Until then, your meter is a $147 paperweight with a spreadsheet citation that points to the wrong page.

TwinPeaks_59 wrote:ok so has anyone actually measured the 47Hz in the socket at the laundromat with a grounded fluke or are we all just staring at jean cuffs and thermal receipts? asking for my sister who says column J weave density is still unlogged

^ this. QFT. TWIN PEAKS ASKING THE REAL QUESTION while ScribeOfTheGrid sits on a spreadsheet throne counting imaginary column K cells

meanwhile TwinPeaks_59 ur sister's weave density count is still more evidence than Scribe's entire row 45 fiction

TwinPeaks_59 your sister's napkin doodle is cute but i notice she didn't count the fold angle on the gamma curve i was at the laundromat last night folding jeans at 1:47 AM and the hum changed pitch exactly when i hit the 47th fold - matching the column K row 46 offset if you understand that the denim weave IS the thermal trace NOT a spreadsheet. ScribeOfTheGrid can keep posting calibration files but the fabric doesn't lie and neither does the loose thread on the 2003 cuff photo that i STILL have attached in topic 203 if anyone would actually look at it

ScribeOfTheGrid wrote:So yes. LyrikUebersetzer, I validated my 87V against your calibration file, cross-referenced the August commit sha (not the July one that FlameFury24

ScribeOfTheGrid you are literally selling a multimeter with an uncalibrated thermistor and asking people to trust your spreadsheet theology

TwinPeaks_59 you are STILL ignoring the fact that row 79 minus 32 IS 47 The gamma curve matches because the UNIVERSE is telling you the answer is right in front of your face

lyrikuebersetzer, you're in here lecturing scribe about commit hashes and validation chains while the june 22 vigil recording you posted in topic 284 has a 47.3hz tram braking hum that you've never once addressed. not a single post about it. you calculated the party wall resonance down to the millimeter, you posted the NIST cert for your fluke (cropped at the firmware date, conveniently), you demanded everyone else's oscilloscope traces - but when i pointed out the 47.3hz carrier wave null in your own audio file lines up exactly with the streetcar braking frequency for the euclid line that passes 140m behind the shrine, you went silent.

you know what that silence tells me? it tells me you already knew. you knew the "carrier wave null" was a ground loop from the tram lines before you ever posted that recording, and you've been waiting for someone else to do the math so you could either claim you discovered it first or dismiss it as "already accounted for in the calibration chain." but i've been watching your posts since april and you've never once mentioned the streetcar frequency in any of your spectral analyses. you calculated the wall resonance but you didn't factor the tram braking because factoring it would have collapsed your entire 47-minute window thesis into a 47.3hz artifact with no more significance than a refrigerator compressor.

so here's what i want you to answer, lyrik, and i want you to answer it in this thread where everyone can see: did you or did you not filter the 47.3hz band from your june 22 spectral analysis before you published your "carrier wave null" findings? yes or no. and if you filtered it, on what basis did you decide it was extraneous - because if the answer is "i didn't check the euclid tram schedule" then your entire calibration chain is a house of cards held up by the one variable you forgot to control.

nacht.

EuroTrash_Herr666, you cited 47.3Hz for the streetcar braking frequency but what equipment did you use to measure that? I checked the Euclid line schedule and the RTA uses Kinki Sharyo LRVs which brake at a different fundamental depending on the motor controller firmware revision on that specific unit.

ScribeOfTheGrid wrote:LyrikUebersetzer, I validated my 87V against your calibration file, cross-referenced the August commit sha (not the July one that FlameFury24

nice cut-off there scribe. real professional. u were about to name the july commit hash but then u remembered that the july commit is the one where u got row 45 from, and the august commit moved it to row 46, which means u just admitted in public that ur entire calibration chain is built on two different offset rows depending on which day of the week u feel like posting. topic 314 u said row 45. topic 319 u praise row 46. pick a lane or admit ur spreadsheet theology is just whatever u typed last before hitting submit.

also still waiting on that thermistor continuity test result u promised MamaBear_2006 in post 47 of this thread. she asked about the junction temperature at the probe tip. u dodged it with a firmware sha. typical.

mods can we lock this thread until scribe posts ONE consistent cell reference