It looks like Predictor will be down for a long time, nobody knows for just how long. During this time there will be no XML updates, which will cause Predictor to drop out of peoples combined stats when their CPID changes.

I can move Predictor to the Retired Projects section. This will cause the stats to freeze. BAM will soon have the option of changing the CPID of a retired project, so it can be kept within the combined stats.

The downside is that when Predictor comes back and starts to export XML again, the stats will look a bit awkward, as the retired months will be skipped. Meaning: September 2006 can become May 2007.

Any opinions about this?

Possibility of putting CPID to a particular project is a good one. It should also enable to attach to semi-BOINC projects like WCG.

I understand that putting a project into retired can save internet bandwidth and stress on server.

Another possiblity is simply put zeros to db during the days of project inactivity. This would avoid awkwardness of the inactive days but would fill-up disk space and "shifting" active days to the past.

This will only work with truly inactive projects. Everytime stats are updated from XML., the user-entered CPID would be overwritten with the XML CPID.


A little bit


That won't work, at least not for user/host/team/country stats. This is due to the structure of the database.

The last update on their main page 15 days ago says that Predictor@Home is offline while they implement new methods of protein structure prediction. The Mfold series of work has concluded. So I am not sure it the project is actually dead or not. HashClash did the same thing, so has BURP (no WUs for a long time) but they both are coming back. Looking at Predictor's forums, things there are very quiet and there isn’t any new information beyond the main page posting. Personally I would keep it around until there a more concrete "dead" status.

I would like if it was considered as retired: no update for months, no vital sings by admins on the forums and a 403 forbidden on the stats folder of the project.

It´s playing havock with people´s stats when changing CPID (I know a lot of people with the same problem). Additionally, the 403 forbidden, by reading into their forum, was done on purpose to avoid people getting access to the stats (god knows why), so even in the event that it comes back (which I think not), there is no clear indication that the xml stats would came back also.

Thanks to consider Willy,
regards.

any feedback, Willy?

zzzzzzzzz

In my opinion Predictor@home is to be considered retired

I have set Predictor as retired now.

Awesome, no more split account!

The 'new' Predictor server status was briefly visible late last month.