|Re: Timing HP Calculator Programs|
Message #4 Posted by Egan Ford on 30 Nov 2007, 12:27 p.m.,
in response to message #1 by Bill (Smithville, NJ)
The only timer the 35s has is the timeout timer. I like the beep idea, but there is no beep. Other calcs (71/41/48/49/50) have clocks and are easy to time.
One way to increase your accuracy with a stop watch is to not start the benchmark and the stopwatch in parallel. Use a mental metronome, start the benchmark, wait a sec, start stopwatch, wait for results, after you see them wait a sec, stop stopwatch. This will give you more time to react.
Run in a loop 100 times, time manually, then /100 the time. If your timing is off 1 sec, then its really only 1/100 off. Accurate but not automated.
For long programs, 10 times is good enough. In any case run once, time manually, *(nruns * .95) to get ETA, set alarm on your watch (or 41CX, 50g, etc...), go back to work, look at calc when alarm goes off.
For very long programs 1 time is good enough, you may need to time a subset of the problem to get an ETA. Or, write a 2nd program that runs for ~60 sec (you will need to time it to get better est.). Then after your program runs, run the 2nd program in a loop, increment a counter, make sure the program has a pause with message at the start or end, press cancel when message appears, stop stopwatch, time = totaltime - counter*60. Nice solution if your program completes when you are away from your desk.
If you have an emulator you can screen shot the results, then start the run continuously getting images, if a match to results, stop timer. I've done this with Linux/Nonpareil. If you want to do this with a physical device you'll need a web cam and some smart software.
Edited: 30 Nov 2007, 12:34 p.m.