[plans] distributed.net .plan update

plans at nodezero.distributed.net plans at nodezero.distributed.net
Sat Dec 18 19:00:01 EST 1999

.plan updates in the last 24 hours: 
vetere :: 18-Dec-1999 08:02 (Saturday) ::

Today is variety day as regards Mac OS port status updates. 

The 'cli' client (for lack of a better term to describe what is
currently in beta) will not after all contain an Edit menu for copypaste
purposes. The SIOUX window is something to look at and (in configure
mode) use with the keyboard; it is not part of a graphical user
interface. A planned GUI app will gleefuly accept to all the clicks you
hurl at it. Until then, you can copypaste from a log. 

Pre-8.0 compatibility is in the works. All linkages to Appearance stuff
has just been chucked, though networking issues remain. Bless Open

Fractional build 449 of the Mac client does not contain the AltiVec CSC
core. That is why your CSC rates on G4s suck. It is also (I think) why
the client chooses the wrong CSC core on your cute little grey machines.
Rest assured this will change prior to the release. 

More news as it happens, or very slightly delayed...

decibel :: 18-Dec-1999 23:09 (Saturday) ::

Well, something compelled me to investigate whether all of the tables
in stats that contain block totals (there's 3 of them) matched or not.
Unfortunately, I discovered that they don't.

In addition to the master table, which contains 1 record for each day
that each participant has submitted blocks, there is a platform table,
which contains a row for each cpu/os/client version combination for each
day, and a dailies table, that contains info like how many total blocks
were completed on that day, how many participants, how many teams, etc.

Naturally, if you sum the blocks from all these tables, the totals should
match. Unfortunately, this isn't the case for rc5-64.

Bruce and I have managed to correct many of these errors (including one
bad day for CSC). This means that our most astute of stats observers will
probably notice that our total blocks done will go down for both contests.
This does *not* mean that we've lost work, it only means that there were
some days when the statsrun goofed up and essentially double-counted the
blocks for that day. Also, from what we've seen, there are no cases of
errors in the master table, so personal stats shouldn't be affected.

The bad news is that we haven't fixed all the errors. It seems that there
was some kind of bug in the old stats code that ran on statsbox-I which
resulted in minor differences between the master and platform tables, 
differences on the order of a few thousand blocks per day. These errors
will be much more difficult to track down and fix, and since they should
only affect cpu/os information, we might just leave them alone.

The good news is that, by and large, these errors disappeared when we
cut over to statsbox-II. There's only 12 days since Feb. 1, 1999 that
have errors.

We're beginning to work on what will amount to stats, version 3. We'll
be adding some processes that will continuously scan through stats in
the background, looking for any anomalies like this, so hopefully we'll
be able to quickly catch anything like this in the future.

Sorry for the confusion... keep cracking!

To unsubscribe, send 'unsubscribe plans' to majordomo at lists.distributed.net

More information about the plans mailing list