No credit from BOINC?!

[PieDerro]

I completed 2 BOINC Wu's right back on about the 24th June, and received something like 59 credits for them. Since then (with all the outages crap), I have completed at least 6 more units. However, those 6 units were returned on about 29th June, and I have STILL not received any credit for them?

What's the deal?

 

[salvorhardin]

I would have to guess that since the seti servers have been down for a couple of days, no one else has been able to download your Wus and confirm your results. I would give it a couple more days since the servers have recently been giving wu's out to be crunched.

 

[PieDerro]

ahhh so that's how it works?

I have a better handle on it now thanks, though I do admit BOINC still confuses me somewhat :roll:

 

[CiSmAXz]

Yea, I have also completed a few WU's and show 0 credit. What ever happened to if it aint broke don't fix it. Seti classic workd fine...

 

[Rattledagger]

Well, the most likely cases is:
1; someone grabbed a full 14-day-cache while the system was up, and has of course not managed crunching all yet.
2; someone is only crunching a couple of hours/day, and since the "active-frac" on install is always 1 he's got assigned too many wu to manage crunching these within the deadline.
3; someone for various reasons just dumped their cache.
4; due to server-problems verifying results is either disabled or goes currently very slowly...


The important thing to remember is that if you yourself crunches correctly you should get credit after some days, but due to the anti-cheating-measures & more fair crediting added to BOINC it can take a couple weeks to get this credit.
Then all the initial server-problems & database-optimizations is fixed, expect a more constant credit-flow, but you'll still lag some days. Except in team-races this really isn't a problem.

edit... "if it ain't broke, don't fix it..."

Well, the seti@home-classic-crediting is really broke, remember the doublet-cheaters & the 99%-"give-to-friends"-cheaters. Also, even with switching from v3.03 to v3.08 it's already a 10% difference, not to mention v3.00. Even the normal time-difference due to AngleRange is fairly huge, add on top some "turbowu" taking under a minute to crunch. Remember, before v3.03 was released Anandtech was being beaten by MURC and just look there they're today...
So anything that removes the cheaters & gives more differential crediting than "1 wu = credit" really is an improvement.
Of course the benchmarking can be better, but even with 10% variance here it's better than the old seti@home. AFAIK atleast on the same machine the benchmark-variance is under 1%, so the only huge difference is between machines.

Oh, lastly, with only delivering the same wu to 3 crunchers BOINC is over 100% more effective than "classic"...

(edit... fixing tyipgn errro)

 

[CiSmAXz]

Is there a command line version for BOINC or is it just the GUI?

 

[Rattledagger]

The windows-cli is called boinc_cli.exe and is residing in the BOINC-directory after install.

 

[CiSmAXz]

Do you just run that exe?

 

[dmcowen674]

Originally posted by: Rattledagger
Well, the most likely cases is:
1; someone grabbed a full 14-day-cache while the system was up, and has of course not managed crunching all yet.
2; someone is only crunching a couple of hours/day, and since the "active-frac" on install is always 1 he's got assigned too many wu to manage crunching these within the deadline.
3; someone for various reasons just dumped their cache.
4; due to server-problems verifying results is either disabled or goes currently very slowly...


The important thing to remember is that if you yourself crunches correctly you should get credit after some days, but due to the anti-cheating-measures & more fair crediting added to BOINC it can take a couple weeks to get this credit.
Then all the initial server-problems & database-optimizations is fixed, expect a more constant credit-flow, but you'll still lag some days. Except in team-races this really isn't a problem.

edit... "if it ain't broke, don't fix it..."

Well, the seti@home-classic-crediting is really broke, remember the doublet-cheaters & the 99%-"give-to-friends"-cheaters. Also, even with switching from v3.03 to v3.08 it's already a 10% difference, not to mention v3.00. Even the normal time-difference due to AngleRange is fairly huge, add on top some "turbowu" taking under a minute to crunch. Remember, before v3.03 was released Anandtech was being beaten by MURC and just look there they're today...
So anything that removes the cheaters & gives more differential crediting than "1 wu = credit" really is an improvement.
Of course the benchmarking can be better, but even with 10% variance here it's better than the old seti@home. AFAIK atleast on the same machine the benchmark-variance is under 1%, so the only huge difference is between machines.

Oh, lastly, with only delivering the same wu to 3 crunchers BOINC is over 100% more effective than "classic"...

(edit... fixing tyipgn errro)

Well said Rattle.

Hmmmm, running both sets of servers, didn't think they'd do that. Any ETA on decommissioning of SETI classic???

 

[Rattledagger]

Originally posted by: CiSmAXz
Do you just run that exe?

Run boinc_cli /?
for switches. Except for setting proxy-settings, everything can be done by the cli, but it's easier to use the gui to make sure everything is working 1st.

Note, if you're installing as service, on some OS you must change what user the service is running as (localsystem) works, and if you logs off the computer unfortunately the service stops.


As for turning off old seti-classic, 1st they must get stable servers, 2nd they must finnish programming the separate gui for all platforms & 3rd fix any important bugs. They're currently optimizing the database & server-programs, but atleast it seems they've fixed some of the problems since wu has started pouring in now, just grabbed 50 wu that is the days limit for a machine. As for the separate gui, no idea...

 

[RaySun2Be]

Note, if you're installing as service, on some OS you must change what user the service is running as (localsystem) works, and if you logs off the computer unfortunately the service stops

Grr. That defeats the whole purpose of why I want it installed as a service. :|

If I, or anyone else (IE WORK environments) log off the PC, the PC can keep crunching. The only benefit to running the CLI as a service currently is that it is hidden.

I sure hope it's on their TO DO list.

I know they have been busting their humps, but they also have a long way to go to have a fully usable app. I would think that they could at least start out with the functionality of the SETI1 CLI client.

Ah well, just means I won't be rolling it out for awhile.

Say what you will about the DNET folks, but still most DC projects don't come close to the excellence and functionality of their RC5 client.

 

[Rattledagger]

Service-install has always been a M2-task, so there at all being a service included now is unexpected, even the windows-cli being included is before schedule.