BOINC 3.20 available - all standard platforms

[BC]

BOINC 3.20 is available for all platforms now. all -110s are fixed, etc as promised.

If you wish, you may now also compile it yourself and install as a service.
(The service "CLI" is not pre-compiled.... I asked that it be for windows)
Installing as a service eliminates lots of problems.

If anyone has Visual Studio .NET and is willing to compile it for us, I would appreciate it... I don't have the ".NET" software... just the regular.

3.20 is doing well so far. Only had one failure and that was MY fault..
3.20 performance is better... benchmark appears more stable/reliable.
3.20 BOINC upgrades all existing BOINCS, including Predictor,
and runs on win/98 and up.

It is available at my site ( http://www.tumoeng.com/boinc_320.zip )
if the main site at Berkeley is down until all sites get it.

I would make a backup of your existing BOINC directory as a failsafe just in case you uncover a weird error (standard procedure) and then delete it after 2-3 days of normal ops...



BC

[Ototero]

BOINC 3.20 now running. Easy peasy. Thanks BC.

It's running seti 3.08. I've been running seti for some years now. Just joined AMD Users, my id is MOLE but I'm changing that to OTOTERO, that's a bad word in Tagalog ;)

What position is our team in? The seti site keeps having database errors. so I can't update my id.

[BC]

The Seti site is going nuts... and quite unstable. We are pushing (I believe) more on Predictor. http://predictor.scripps.edu

(don't download their released version of CC) just signup and get the URL and key. Then go to the web page and set your prefs. After that... Attach and join the fun.

On Predictor, last I saw, from 9th up to solid 8th, knocking on 7th's door...

but I did hardware damage here last night... or munged the BIOS
and will be forced to clear it and start over and have not paid much attention to predictor otherwise.

I've been busy with the machine... it LOOKS like a bios bug, but i cannot go back to 'auto' mode now from manual settings.... I will fuss more later.
I'm starting to get sleep deprived..... pushing only 1.5G out of a 1.6G memory bus and not keeping it stable... obvious sign of needing sleep... LOL


BC

PS: my BF taught me both good and bad words, hope I don't ever slip up! ..... LOL

[Ototero]

Cheers BC,

Joined and started. Should I move from D2OL to Predictor? Where are our excess parity bits being used?

I'll follow the leader.

[BC]

Cheers BC,

Joined and started. Should I move from D2OL to Predictor? Where are our excess parity bits being used?

I'll follow the leader.

I'm honestly not sure.... I think we are being a bit dynamic at the moment. One of the more senior members is probably better qualified to answer the D2OL vs Predictor question. I am spearheading Predictor for us because I'm also now on the development team.

Personally, if you had two processors, I would run 1 on each for now.. BOINC has that capability and it works very nicely.

I simply know that predictor is a front end (of sorts) to D2OL (which actually helps find the protease inhibitor).

Would one of the 'real' scientists please speak up here? (my foot is terribly close to my mouth!!!! HAHA)

BC.

[chaz]

I am running about 75% predictor now, mainly to get a jump on the stats. Whats left is on SOB, since we fell a rung or two.

[AMDave]

Thanks BC.
Always keen to give it a go.
With backup done, installed 3.20 over 3.19 successfully and it picked up the Predictor work unit that was half way through and has started moving on.
Benchmarks and time estimates as you say.
Looks like a success.
Will report if anything wierd happens.

I still have a foot in a couple of projects but it looks like we lost a lot of grunt in D2OL over the last few days. I had trouble with 2 of my machines due to me messing around with my network, but the difference is way more than my contribution.

** edit ** sorry, forgot to add that it refreshed my Predictor Stats OK. Seti handler not responding again, but it looks like the comms, are ok.

[BC]

Thanks BC.
Always keen to give it a go.
With backup done, installed 3.20 over 3.19 successfully and it picked up the Predictor work unit that was half way through and has started moving on.
Benchmarks and time estimates as you say.
Looks like a success.
Will report if anything wierd happens.

I still have a foot in a couple of projects but it looks like we lost a lot of grunt in D2OL over the last few days. I had trouble with 2 of my machines due to me messing around with my network, but the difference is way more than my contribution.

** edit ** sorry, forgot to add that it refreshed my Predictor Stats OK. Seti handler not responding again, but it looks like the comms, are ok.

Thanks Dave,
I think seti is down or still in the 'overloaded' state.
I also think the help we've got on predictor will slide back over to D2OL
once we're caught back up.... but thats their decisions.

BC

[bwhite]

I have Predictor on a couple of machines just to get my foot in the door and see how it goes :thumbleft: Major effort is still twords D2OL for me at least for a little while longer.

[BC]

First: Bwhite: Welcome aboard.

Second: To all who have Seti/boinc and Predictor/boinc... please remember to balance your loading for each project.. it helps keep the point count up if the scheduler knows how you are running, which will minimize your 'pending' list and the loss of points due to aging.

Lastly: I'm trying to figure out how to manage this, but with
two slower machines about to come online this weekend from me,

I will need to make a decision how to best compliment the support
Chaz is giving us on Predictor.

I miss having both 3200's here & online full time, but will have to live
with it for the moment.

Would someone suggest what would be the most effective split between D2OL and Predictor? I'm thinking of doing a simple 'Mips count' and split the Mips 50/50. Chaz being 75% on Predictor is providing more help than my other machines would. Maybe I can at least back fill a little bit until he's ready to move back, or he & I trade off.

Chaz? Anyone? .... Comments, Suggestions?


BC