Re: [TI30] When all else fails ... Message #2 Posted by Karl Schneider on 21 Jan 2007, 2:44 a.m., in response to message #1 by Palmer O. Hanson, Jr.
Hello, Palmer 
Quote:
When all else fails ...
Er, "... read the manual"? You seem to reproach me for allegedly not having done so, yet you couldn't have known whether I actually had one. The LED TI30 I bought was from eBay; the one I damaged a quartercentury ago has long since been discarded, manual and all.
But, I'll admit it: The package did include manuals in English and French. I had quickly flipped through the English manual, but didn't see the need for perusing it in detail, since I already knew my way around the TI30, and  well  it's so simple, it ought to be intuitive.
BTW, the manual is quite a bit better than what one typically receives nowadays for lowend calculators. Of course, US$25 (1976) is substantial by modern standards for a lowend calculator.
Now, on to the topics you discussed:
Quote:
Page 25 of the Owner's Manual for the TI30 discusses the guard digit methodology implemented in the TI30.
...
There no doubt that the thirteen digit methodology used by TI (before the TI95) is different from the ten digit methodology used by the HP35 and subsequent HP calculators prior to the HP28. Each methodology has both advantages and limitations. The fans of either side have been arguing about it for over thirty years.
It's on page 24 in my manual; my real point, however, was, "Why make three extra (but unreliable) digits available to the user in the complete result for accurate rounding, when one guard digit would suffice?" It's like providing eleven significant digits when only eight are justified (the last one being uncertain and rounded). I showed that the extra digits for e^1 were unreliable. 2.71828183 would have been acceptable; 2.7182818301 was an incorrect calculation, although the displayed result was accurate to eight digits as advertised.
Casio took a sensible approach in the same era: The 1981 fx3600P provides one guard digit to help ensure accurate displayed answers. The modern fx115MS provides two guard digits, and both are correct (last one rounded) for e^x and 10/7. (Both of these calculators display 10 digits.)
The three guard digits didn't seem to help the trigonometric calculations on the old TI30's. Here's a comparison:
Sine of "almostpi" radians:
Value of pi TI30 Casio fx3600P HP41 HP32SII
3.14159265359    2.068E13
3.1415926536 4.778E09 0  1.021E11
3.141592654 4.096E10 4.E10 4.1E10 4.102E10
It is curious that the TI30's error is larger with the 11digit value of pi, than with the 10digit value.
The results from the HP32SII, with its rigorous math, are exactly correct to its 12 digits (but rounded in the table).
The Casio's result of exactly zero may utilize rounding for user "reassurance", much as the HP30S does.
Quote:
I agree with Karl's result for pi / 10 . I have been unable to get his result for pi / 1 EE 1 . I get the correct 3.141601 using three different TI30's and two different SR40's. I cannot explain why we should get different results. I do note that the display "3.1416 00 " is NOT 3.1416 x 100 but IS 3.1416 x 10^00.
I made several editing errors, after noticing similar behavior using 1.0 as the divisor as well as 10. My statement should have read,
"pi / 10 displays .31415927. pi / 1 [EE]1 displays "3.141601" (3.1416 x 10^{1})."
Quote:
Karl then writes "Now, just try to get out of scientificformat display mode!"
That really isn't too hard. You can do it by multiplying the displayed value by the sequence 1 INV EE = as illustrated on page 12 of the Owner's Manual .
The fundamental problem is that [EE] combines the functions of [EEX] and [SCI]. There was no specific operation to escape scientificnotation display mode (such as [FIX] or [ALL]) while preserving the displayed number.
To do so, the user could multiply or divide a result by "1 [INV][EE]", but not "1" or "1 [EE]", or "45 [tan]", or ....). That was included within an example on page 12, but was not an explicitly stated procedure. It's not very intuitive; a better method would have been hitting [=][=].
Another workaround is to [STO] the result, then hit [ON/C] and [RCL].
Quote:
Karl also writes: " Move the decimal place repeatedly to the left using [INV][EE], and watch the mantissa be obliterated, as significant digits fall into the "bit bucket" until "0 06" ( 0 x 106) (sic, after Palmer's quoting) is displayed. Not good."
NOT SO! The paragraph "Exponential Shift" on pages 1314 of the Owner's Manual explain that the technique can be used to change the displayed value without changiing the value in the display register. To get back to the normalized display a user can simply press =, or if the user does not want to disturb any pending operations he can press EXC EXC.
(Please don't neglect to reinstate formatting codes (e.g, [super]) when using [quote]. They don't copy over, so "10^{6}" is turned into "106".)
Now, please try this on your vintage TI's. Is this what you see?
keystrokes display
pi / 1 [EE] = 3.1416 00
[INV][EE] .31416 01
[INV][EE] .03141 02
[INV][EE] .00314 03
[INV][EE] .00031 04
[INV][EE] .00003 05
[INV][EE] 0 06
[INV][EE] 0 07
[EE] 0 06
[EE] 0 05
[=] 3.1416 00
Displaying a number as "zero times a nonzero power of ten" ain't very good, and neither is to apparently display "zero equals pi". It led me to an incorrect conclusion regarding actual loss of digits.
BTW, I can't force any of my HP's to accept or display " 0 [EE]" to any exponent other than zero  not even the HP35, which had been in production for four years by 1976. The Casios convert an entered 0Enn to zero upon any operation. They also won't "squeeze out" all the significant digits in a display when the user moves the decimal place to the left with "<ENG".
Quote:
Finally, Karl writes: "Perhaps TI's youthful customers didn't care, but HP's professional customers certainly would have."
Some professional customers would have decided to read the Owner's Manual when they received results that they didn't understand.
One can only hope and trust that HP's professional customers would have done the same.
Karl now writes, "Please refrain from chiding, sir." Documentation of unsound implementations, or of arcane procedures that ought to be simple and intuitive, does not excuse either the unsoundness or the arcaneness.
This applies to modern products, as well as to 30yearold vintage ones.
Best regards,
 KS
Edited: 22 Jan 2007, 1:21 a.m.
