HMS> & >HMS Prog. for 12C

01102018, 05:18 AM
Post: #1




HMS> & >HMS Prog. for 12C
I am inspired by Gamo to post some HP12C programs! I have honed these 2 programs for a couple of months now. Since I collect driving times everyday, I need to convert the DD.MMSSSS into a number and vice versa.
Here is HMS to decimal format Code:
Now here is my other program that converts from decimal to DD.MMSSSS Code:
I even dare say this program is better than Eddie Shore's program (I ran into his program as I was scouring the forums to check for a similar post as this one) This is because it is shorter, doesn't use any registers, and both of our (Me & Eddie) programs completely wipe any intermediate results stored in the stack before program execution. However, I can't say who's is better in the contest of speed, as I only have a modern HP12C. The only reason why I bring up Eddie's program is because he writes a lot of programs and seems experienced. So I'm comparing my first programs with his. And I wrote this program completely on my own, with refinements over time. I also expect Deiter (I think I spelled his name right) to check and cirque my program. Just like with Gamo's programs. 

01102018, 05:22 AM
Post: #2




RE: HMS> & >HMS Prog. for 12C
I just realized that programs should generally be posted in the General Software Library. I'll make sure to do so next time. I also didn't check that section of the forum for a similar post. My apologies. I'm learning.


01102018, 06:49 AM
Post: #3




RE: HMS> & >HMS Prog. for 12C
Thank You Carsen
That will be better to provide example for both programs. Gamo 

01102018, 10:37 AM
(This post was last modified: 01102018 10:56 AM by Dieter.)
Post: #4




RE: HMS> & >HMS Prog. for 12C
(01102018 05:18 AM)Carsen Wrote: I am inspired by Gamo to post some HP12C programs! I have honed these 2 programs for a couple of months now. Since I collect driving times everyday, I need to convert the DD.MMSSSS into a number and vice versa. I like the formulas shown in this thread on the old forum. The following program adapts Werner's 42s implementation. Code: 01 ENTER Rule: values in hh.mmss format are entered and returned with negative sign. Code: 3,1234 [R/S] => 3:07'24.24" Edit: I just noticed... (01102018 05:18 AM)Carsen Wrote: I also expect Deiter (I think I spelled his name right) Well.... but at least it sounds right if you say it in English. ;) (01102018 05:18 AM)Carsen Wrote: to check and cirque my program. Just like with Gamo's programs. You can still improve it. For instance, in your first program you can save two steps if you replace lines 01–04 and 08–11 (as well as the first lines of you second program) with Code: INTG In your second program you first multiply by 60 and then divide by 10000. Here a simple multiplication by ,006 will do. And finally: welcome to the club. ;) Dieter 

01112018, 04:46 AM
Post: #5




RE: HMS> & >HMS Prog. for 12C
(01102018 10:37 AM)Dieter Wrote: The following program adapts Werner's 42s implementation. I LOVE this program simply because I don't have to switch program lines to convert from HH.MMSS to decimal and vice versa. It's pretty cool. I'll end up using this program. The formulas it uses is also unique and fun. But I'm still going to keep and work on my own HMS programs. I made the suggested changes and that's so cool because now the program takes up one less register. I also tried to make some more amends but to no avail. HMS to decimal program V3. Code:
And the decimal to HMS program V3 Code:
Examples Gamo? No problem. I'll use the driving times I collected today... Example #1: Carsen's takes a trip to his job. He times himself on how fast he gets to his job and back home. Trip #1 is his venture to his job and trip #2 is his drive back home. Convert the times Carsen collected on both of his trips from HH.MMSS to decimal format. Then figure out his total time he spent getting back and forth from his job that day. Assume that the HMS to decimal prog. is entered into the 12C first. Then the decimal to HMS prog. is entered second. Thus decimal to HMS prog. starts on line #19. Trip #1: 0 hr 55 min & 53 sec 0.5553 [R/S] > 0.931388889 [STO] [+] 1 Trip #2: 0 hr 53 min & 00 sec 0.53 [R/S] > 0.883333333 [STO] [+]. Then... [RCL] 1 > 1.814722222. Finally... [GTO] 19 [R/S] > 1.4853 which is 1 hr 48 min & 53 sec. Sweet! I'm in the club! 

01112018, 06:08 AM
Post: #6




RE: HMS> & >HMS Prog. for 12C
... and this thread for mathematical proof of my formulas, but beware of rounding ...


01112018, 07:03 PM
(This post was last modified: 01112018 08:06 PM by Dieter.)
Post: #7




RE: HMS> & >HMS Prog. for 12C
(01112018 06:08 AM)Pekis Wrote: ... and this thread for mathematical proof of my formulas, Ah, so it was you who started that thread. (01112018 06:08 AM)Pekis Wrote: but beware of rounding ... Definitely. Calculating with base60numbers in the decimal world can be tricky. This reminds me of a 2016 thread where such problems were discussed in detail. Here even in such a powerful language as Fortran. But with binary floating point operations... #) Pekis: take a look at post #28 in the linked thread. ;) Carsen: here is an improved version that adapts the formulas in that thread. It also preserves the Yregister so that simple hh.mmss arithmetics can be done without storing intermediate results. And it's even one step shorter. ;) Code: 01 ENTER Re. your example: Code: 0,5553 [R/S] => 0,913888889 Dieter 

01112018, 09:22 PM
Post: #8




RE: HMS> & >HMS Prog. for 12C
...
Could you show the result of converting 8/60 to HMS with your program ? It's the "acid" test ... Thanks 

01122018, 09:13 AM
(This post was last modified: 01122018 09:49 AM by Dieter.)
Post: #9




RE: HMS> & >HMS Prog. for 12C
(01112018 09:22 PM)Pekis Wrote: ... The program returns 0,07599999999. Which is displayed as 0,0760. ;) But actually this is the correct (!) result. Here's why: You do not enter 8/60, but 0,1333333333 – a number slightly less than 8/60. And the exact HMS value for this is 7'59,99999988" which is correctly rounded to 7'59,9999999". Try it: 0,1333333333 h times 3600 s/h equals 479,99999988 s. Or 7 minutes and 59,99999988 seconds. Which is what the above implementation returns. For the same reason HMS(7/60) should (and here does) return 7'00,0000001" on a 10digit calculator. Simply because 0,1166666667 is a tiny bit more than 7/60. So yes, this indeed is an acid test: if the result is exactly 8'00" or 7'00" the function would be wrong and do some kind of "cosmetic rounding". Which is not what a decent calculator should do. ;) Dieter 

01122018, 12:36 PM
Post: #10




RE: HMS> & >HMS Prog. for 12C
Thanks for the answer.
DEG>DMS(8/60) would be evaluated as 0.08 (expected result) on an infinite precision machine with my formula DEG>DMS(x)=(90*x+INT(60*x)+100*INT(x))/250 ( DMS>DEG(x)=(250*xINT(100*x)60*INT(x))/90 ) Look at the result on a limited precision machine as the argument tends to 8/60: 0.13 > 0.0748 0.133 > 0.07588 0.1333 > 0.075988 0.13333 > 0.0759988 0.133333 > 0.07599988 0.1333333 > 0.075999988 ... "8/60" > 0.076 Is there something wrong seeing 0.075999999999.... naturally rounded to 0.076 by the machine ? What do you think of it ? 

01122018, 12:50 PM
Post: #11




RE: HMS> & >HMS Prog. for 12C
(01122018 12:36 PM)Pekis Wrote: Thanks for the answer. Which one? (01122018 12:36 PM)Pekis Wrote: Is there something wrong seeing 0.075999999999.... naturally rounded to 0.076 by the machine ? If the result actually was exactly 7'60" I'd say that this should not occur. But here we are talking about 0,07599999999 which is only displayed as 0,0760. And that's fine by me: it can even serve as a hint that the result is a tiny bit less than 8 minutes. ;) Dieter 

01132018, 01:26 AM
Post: #12




RE: HMS> & >HMS Prog. for 12C
(01112018 07:03 PM)Dieter Wrote: Carsen: here is an improved version that adapts the formulas in that thread. It also preserves the Yregister so that simple hh.mmss arithmetics can be done without storing intermediate results. And it's even one step shorter. ;) Dieter! This. New. Version. Is. Amazing. Thanks a lot. And I'm sure you know why its so cool. Preserving the Y register is SO useful for what I do 5 days a week, collecting that sort of data. And rather than using my 50g, the Voyager series is just perfect with its size and power consumption. 

« Next Oldest  Next Newest »

User(s) browsing this thread: 1 Guest(s)