From: Jacob Fugal Date: 2006-08-21T23:23:26+09:00 Subject: Re: Been there, done that - language shootout On 8/18/06, Isaac Gouy wrote: > > Jacob Fugal wrote: > > On 8/10/06, Caleb Clausen wrote: > > > On 8/10/06, Eric Hodel wrote: > > > > My assertion is correct. The fasta benchmark says: > > > > > > > > > Each program should: > > > > > [...] > > > > > * generate DNA sequences, by weighted random selection from the > > > > > alphabets (using the pseudo-random number generator from the random > > > > > benchmark) > > > > > > > > And the implemenation: > > > > > > > > http://shootout.alioth.debian.org/gp4/benchmark.php? > > > > test=fasta&lang=ruby&id=0 > > > > > > > > Contains the random number generator from the random benchmark: > > > > > > > > http://shootout.alioth.debian.org/old/benchmark.php? > > > > test=random&lang=ruby&id=0 > > > > > > I did not see this test named 'random' when I looked through the > > > alioth site earlier today... and I still don't see any links to it > > > from that site. (I did find it by following your link, however.) > > > > > > I notice that your second link contains the word 'old'. Perhaps this > > > benchmark has been withdrawn? If so, I submit that your criticism was > > > true in the past, but no longer is. > > > > I agree that the presence of "/old/" (vs. "/gc4/") in the URL probably > > indicates that the "random" benchmark has been removed from most > > locations. There was an actual link to it, however, from the FASTA > > benchmark description page. Specifically, on this page: > > > > http://shootout.alioth.debian.org/gp4/benchmark.php?test=fasta&lang=all > > > > At the bottom, under "about the fasta benchmark", in the second bullet > > point. That's the *current* page for the FASTA benchmark, so maybe > > that page just needs to be updated to remove that constraint? > > > > Jacob Fugal > > There was and is an actual link to it from the FASTA benchmark > description > http://shootout.alioth.debian.org/gp4/benchmark.php?test=fasta&lang=all#about > > Jacob, why would we want to remove that constraint? Either remove or update to point to a current (not "/old/") benchmark. I don't care either way... Jacob Fugal