Prev: (Sorry for the non french speaking peoples) Un logiciel de géométrie dynamique pour HP
Next: Dust inside 50g. How to clean? How to prevent?
From: Han on 24 Mar 2010 20:38
On Mar 24, 7:29 pm, Han <handuongs...(a)gmail.com> wrote:
> On Mar 24, 3:41 pm, Wes <wjltemp...(a)yahoo.com> wrote:
>
>
>
> > On Mar 24, 10:02 pm, Wes <wjltemp...(a)yahoo.com> wrote:
>
> > > On Mar 24, 8:21 pm, Wes <wjltemp...(a)yahoo.com> wrote:
>
> > > > On Mar 24, 3:19 am, Han <handuongs...(a)gmail.com> wrote:
>
> > > > > > My HP 49G+ just confirmed Jim's answer. Using TIME and HMS-:
> > > > > > 0.0429166382 (just under 4.5 minutes). I'm working on improving the
> > > > > > algorithm. Let's see how quickly this time is destroyed. =)
>
> > > > > Current speed: 0.0256074341 (2 minutes 56 seconds)
>
> > > > I've got 124.5 seconds (2 minutes 4.5 seconds) using TEVAL.
>
> > > > -wes
>
> > > Make that 102.4 seconds (1 minute 42.4 seconds)
>
> > > -wes
>
> > Down to 97.6 seconds
>
> > -wes
>
> Very impressive... I've only managed to get down to about 115 seconds.

New time: 92.10 seconds; program size: 181 bytes, checksum # 41D9h
From: Virgil on 24 Mar 2010 21:43
In article
<12d20a2c-e16e-4d24-9688-bf54989ed519(a)g4g2000yqa.googlegroups.com>,
Han <handuongster(a)gmail.com> wrote:

> On Mar 24, 3:41�pm, Wes <wjltemp...(a)yahoo.com> wrote:
> > On Mar 24, 10:02�pm, Wes <wjltemp...(a)yahoo.com> wrote:
> >
> >
> >
> > > On Mar 24, 8:21�pm, Wes <wjltemp...(a)yahoo.com> wrote:
> >
> > > > On Mar 24, 3:19�am, Han <handuongs...(a)gmail.com> wrote:
> >
> > > > > > My HP 49G+ just confirmed Jim's answer. Using TIME and HMS-:
> > > > > > 0.0429166382 (just under 4.5 minutes). I'm working on improving the
> > > > > > algorithm. Let's see how quickly this time is destroyed. =)
> >
> > > > > Current speed: 0.0256074341 (2 minutes 56 seconds)
> >
> > > > I've got 124.5 seconds (2 minutes 4.5 seconds) using TEVAL.
> >
> > > > -wes
> >
> > > Make that 102.4 seconds (1 minute 42.4 seconds)
> >
> > > -wes
> >
> > Down to 97.6 seconds
> >
> > -wes
>
> Very impressive... I've only managed to get down to about 115 seconds.

91.4 seconds. #306Dh 141 bytes.
From: Han on 24 Mar 2010 22:02

>
> 91.4 seconds. #306Dh 141 bytes.

I am really enjoying this MC.
72.8 seconds, #A937h, 176 bytes
From: John H Meyers on 25 Mar 2010 06:30
On 3/24/2010 7:38 PM, Han wrote:

> New time: 92.10 seconds; program size: 181 bytes, checksum # 41D9h

How about adding a second category -- shortest program?

80.5 thus far here.

What happens when time spent writing and entering a program
is added to the time spent running it, to produce
"time spent getting the answer" ?

[r->] [OFF]
From: John H Meyers on 25 Mar 2010 08:22
> 80.5 thus far here.

That's bytes, not seconds -- on Emu48,
the "real time" (4-5 seconds with this Intel CPU)
is not "real calculator" time,
so comparison with calculator times is not available.

Individual calculators may also vary,
as may repeated results on even the same calculator
(try forcing a GC before each timing,
via MEM or even just ON/Cancel,
and run several times to ignore "outlier" times,
which seem to occur at random in the ARM emulator).

Byte counts seem to be more stable,
even though most of are paid by the hour, rather than by the byte
(hence the longest-running program may make the most money,
as do some of the most wasteful and poorly crafted
applications, operating systems, and political decisions :)

That's why I think we should have some "challenges" take the form
of devising the most convoluted and wasteful way to do something,
to be more like real life :)

http://www.rubegoldberg.com/ (Contest finals only two days from today!)

http://en.wikipedia.org/wiki/Rube_Goldberg_machine

http://en.wikipedia.org/wiki/Rube_Goldberg

[r->] [OFF]
First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5 6 7 8 9 10
Prev: (Sorry for the non french speaking peoples) Un logiciel de géométrie dynamique pour HP
Next: Dust inside 50g. How to clean? How to prevent?