|
|
NEWS Hardware freaks trying to make some sense out of a bunch of numbers |
|
Site Stuff SETI Benchmarking Team Moves Random SETI News
So what does that mean? Well to make a long story short. For the members in the top 100 their stats on the Team page and their contribution to the total team numbers are updated real time. For those members not in the top 100, their work units received may not get added to the team total immediately, and it may take a week or more for them to get added. This is the reason why we have seen sort of sudden "jumps" to our team totals. The backlog of work units from team members not in the top 100 get added all at once, and it seems we get a huge bonus. This also explains why it seems that all the work units were being contributed by the top 100 members. It isnt that the teams not in the top 100 are "weekend warriors", it is all just the way the servers handle the data (did i lose you yet? :-). There has been talk of a new version of the SETI client(s). Yes it is true. They are working on a version 2.0 of the client, and will hopefully have it ported for different OSes and machine types and will all be released at the same time. Will this new client be radically different and lead to different work unit times? Apparently the answer is no. The main reason for this new version is for security. There are alot of SETI hacks out there, and they are trying to push this new version out the door so they can stop results coming from all these unauthorized hacks. It may be true that the results from these hacks may be identical if you used an "authorized" client, but the problem is that the SETI Berkeley guys do not have the time and resources to test and confirm all the results from unauthorized clients. To get the security contained in the new version, the ability to extract more results from the data has been sacrificed. When the new version hits the street, you will need to update the client, or the Berkeley servers will refuse the work unit results. I will keep you informed when the new version will be released. Ok....I cant think of anything else now....catch ya next time...
#5 with a bullet .....other top 20 movement: C. Eric Smith passes tron for the #13 position. FluffyPants hopped into the top 20, passing the defunct Rat Bastard along the way. .....top 100 news: Moving back into the top 100 after a short absence, Other slides back in at #100. Also new to the top 100 is The Weeblows at #95. To make room for them, Rob and mickey352 dropped out of the top 100.
ALL HAIL guru! Sometime in the late hours last night guru passed up the SouthPark Admin Crew for the #1 spot on Team Lamb Chop. Congrats to guru! Other stuff... .....C. Eric Smith is also in position to move past tron.....the inevitable should happen sometime tonight. .....making a reappearance in the Team Lamb Chop Top 100 is alank. he hops in at the #99 spot today. A new spot was opened up in the Top 100, because apparently The Digital Dan left the team....taking with him 411+ work units. Sorry to see you go Dan.
Weekly Stuff The SouthPark Halloween Nighmare More SETI Problems? Team Update Funniness with the Team Stats Lesson #1
First off you may take a look at the total work units processed per day, and notice that they dont match with the numbers from the Club Teams page. This is simple....the data I get for this graph is updated sort of in "real time" and all depends on the time of day I update this graph. The data from the Club Teams page is updated only once per day (around 2pm EST). This is the source for the discrepancy. Secondly, you may wonder why it seems that all of the work units processed for 10/22 and 10/23 are coming from members in the top 100. Well this isnt necessarily so. Team Lamb Chop is constantly adding and (unfortunately) losing members. When a team member leaves, he/she takes with them the work units associated with that account. For example on 10/22 team members not in the top 100 may have processed 450 WUs for that day....but on that same day, we may have lost 2 members which were not in the top 100. The total work units that those two members left with may be, say....460 WUs. This is 460 WUs lost from the team.....and from the calculations of the graph, there wouldnt appear to be any contribution from the members not in the top 100 (i.e. 450-460 = -10WUs). In addition.....It appears that the SETI Servers do not update WUs from the top 100 members of a team the same way as they do the rest of the team. WUs for members in the top 100 seem to get processed and added immediately to team stats, while it may take several days for work units for the rest of the team to get processed. This can be shown in the WUs processed for today (10/24). There seems to be a huge amount of work units processed for the bottom of the team for the day.....but it is more likely that there was a backlog from the servers and it finally got flushed out. Over the past day our team only added 1 member, and all of the work units couldnt have come from them. They most likely came from the backlog for the past couple of days, days that it appeared the only WUs processed came from the top 100 team members. Lesson #2
Why are there huge spikes and valleys in the daily average time? This all comes from team members being added and leaving. The spikes on the graph for the dates, 10/21, 10/12, and 10/8 can directly be attributed to a team member joining or leaving. On 10/8 we added member Darkmage who came in with 409 WUs and an average time of 23.5 hrs/WU. This caused a large upwards spike for that day. the downward spike for 10/12 can be traced to Fragmommy joining with 755 WUs and an average of 10.5 hrs/WU. Finally the large spike on 10/21 is from jackal651 leaving the team with 864 WUs and and average of 13 hrs/WU. Hope that makes things alittle clearer :-). There will be a quiz next Sunday!
|