Whilst searching my account and checking it I came across this wu which is my next one to report. Will I get zero credit, if so what a waist of two hours crunching time.
Here is a copy of its file, so can anyone help;
<core_client_version>4.43</core_client_version>
<stderr_txt>
Can't set up shared mem: -1
Will run in standalone mode.
setiathome_enhanced 6.03 Revision: 306 g++ (Debian 4.3.1-6) 4.3.1
libboinc: BOINC 6.3.8

Work Unit Info:
...............
WU true angle range is : 0.379137
Optimal function choices:
-----------------------------------------------------
name
-----------------------------------------------------
v_BaseLineSmooth (no other)
v_vGetPowerSpectrumUnrolled2 0.00070 0.00000
sse3_ChirpData_ak 0.02577 0.00000
v_vTranspose4x8ntw 0.01392 0.00000
BH SSE folding 0.00250 0.00000

Flopcounter: 23006084687689.144531

Spike count: 2
Pulse count: 0
Triplet count: 7
Gaussian count: 0
called boinc_finish

</stderr_txt>

Validate state Initial
Claimed credit 0
Granted credit 0
application version 6.03

Forgot to add wu numbe it is 321702376 if anyone wants to look.

---

Hmmm...

This is kind of curious. The wingman looks like the task was run in standalone (testing) mode and got 'transplanted' back in for reporting purposes.

Maybe they are working on their own compiled app version for some reason.

In any event, if it validates against yours when it finishes, yep, you get the big goose egg.

Alinator

If you return result that differs from your wingmate's, the wu will be sent to someone else and the one with 0 credit wont be you.

---

Hmmm...

This is kind of curious. The wingman looks like the task was run in standalone (testing) mode and got 'transplanted' back in for reporting purposes.

Maybe they are working on their own compiled app version for some reason.

In any event, if it validates against yours when it finishes, yep, you get the big goose egg.

Alinator

yep that is what I got for two hours work a goose egg instead of 61.16. Can this be sorted out, if things like this happen I can understand why people are leaving. I am not leaving at this moment I have decided at the end of the year to split my Boinc time with another project or just have the other project and have Seti share down to a minimum

---

Hmmm...

This is kind of curious. The wingman looks like the task was run in standalone (testing) mode and got 'transplanted' back in for reporting purposes.

Maybe they are working on their own compiled app version for some reason.

In any event, if it validates against yours when it finishes, yep, you get the big goose egg.

Alinator

yep that is what I got for two hours work a goose egg. Can this be sorted out, if things like this happen I can understand why people are leaving. I am not leaving at this moment I have decided at the end of the year to split my Boinc time with another project or just have the other project and have Seti share down to a minimum

Well I'd look at it pragmatically.

If my speculation of working up their own app is true, then this should be just an isolated case, and I wouldn't worry about it too much.

People do have the right to roll their own application, but this kind of testing should not be done on the production project for any extended length of time. That's why they call it standalone! :-)

I know it's annoying to crunch and get zip, but that's just an occupational hazard when you're talking about an open source app on a public project. ;-)

Alinator

@ [B^S] madmac


Normally with BOINC V3.x you will get no Credits. [SETI@home V5.28]

If you let run BOINC V4.x you will get much variation [+/- 50 % or whatever].. [SETI@home V5.28]

Now maybe with SETI@home V6.03 you will get also no Credits with BOINC V4.x ??


BTW.
You are a 'credit-hunter' or you would like to support the project? ;-D

---

@ [B^S] madmac


Normally with BOINC V3.x you will get no Credits. [SETI@home V5.28]

If you let run BOINC V4.x you will get much variation [+/- 50 % or whatever].. [SETI@home V5.28]

Now maybe with SETI@home V6.03 you will get also no Credits with BOINC V4.x ??


BTW.
You are a 'credit-hunter' or you would like to support the project? ;-D

LOL...

Well, they could do something about 3x'ers in theory. ;-)

It shouldn't make any difference to scoring what app you run (except for the claim) as long as it completes successfully, and validates properly. After that, the server side quorum rules apply to decide what gets granted.

So I guess the best case for a 3x or 'standalone' wingman is that the output is weakly similar and the WU has to go to another replication. :-)

Alinator

I am not a credit hunter what got me mad was this person had been already granted zero credits when mine had not gone up. Can anyone explain this little thing why was it granted zero without me his wingman sending in my report.

---

I am not a credit hunter what got me mad was this person had been already granted zero credits when mine had not gone up. Can anyone explain this little thing why was it granted zero without me his wingman sending in my report

I can't seem to find it in this thread: what's the WU ID number?

I am not a credit hunter what got me mad was this person had been already granted zero credits when mine had not gone up. Can anyone explain this little thing why was it granted zero without me his wingman sending in my report

All WU's show "granted credit 0" before validation...

I can't seem to find it in this thread: what's the WU ID number?

wuid=321702376

JD - you beat me to posting, but I don't think it's a validation thing. Here's some comments on the host that claimed zero...

<core_client_version>4.43</core_client_version>
<stderr_txt>
Can't set up shared mem: -1
Will run in standalone mode.
setiathome_enhanced 6.03 Revision: 306 g++ (Debian 4.3.1-6) 4.3.1
libboinc: BOINC 6.3.8

Not sure if that is part of the problem or not.

---

Wendy



Click Here for BOINC FAQ Service

Just checked the results of my wingman everyone he has done has claimed zero credit, sois something wrong with his computer? With this other piece that web03 mention I have got another one where I got half of the credit that I claimed with this Can't set up shared mem: -1, is this a problem with Linux

---

Just checked the results of my wingman everyone he has done has claimed zero credit, sois something wrong with his computer? With this other piece that web03 mention I have got another one where I got half of the credit that I claimed with this Can't set up shared mem: -1, is this a problem with Linux

wuid=319707490

I think this the WU you refer... Another case of your wingman running BOINC 4.43.
We know all hosts running BOINC 4.xx underclaim credit with MultiBeam WU... Not just a problem with Linux.

Just checked the results of my wingman everyone he has done has claimed zero credit, sois something wrong with his computer? With this other piece that web03 mention I have got another one where I got half of the credit that I claimed with this Can't set up shared mem: -1, is this a problem with Linux

wuid=319707490

I think this the WU you refer... Another case of your wingman running BOINC 4.43.
We know all hosts running BOINC 4.xx underclaim credit with MultiBeam WU... Not just a problem with Linux.

I don't think the question here is about the fact that 4x clients will claim using BM-T, the question is why is the app running in standalone mode instead of normally?

Alinator

Ohh.. sh**.. *%$/&§"$%$§$%* ;-D

A wingman have now the same 'problem', so soon I'll get also 0 Credits for a 0.377648 AR-WU.

I think it's an other rig, because now it's BOINC V4.19 and not BOINC V4.43.

wuid=322079010

AMD Athlon(tm) XP 1800+

CPU time 0 
stderr out <core_client_version>4.19</core_client_version>
<stderr_txt>
Can't set up shared mem: -1
Will run in standalone mode.
setiathome_enhanced 6.03 Revision: 306 g++ (Debian 4.3.1-6) 4.3.1
libboinc: BOINC 6.3.8

Work Unit Info:
...............
WU true angle range is :  0.377648
Optimal function choices:
-----------------------------------------------------
name                
-----------------------------------------------------
              v_BaseLineSmooth (no other)
           v_vGetPowerSpectrum 0.00165 0.00000 
             sse1_ChirpData_ak 0.02600 0.00000 
           v_vTranspose4x16ntw 0.01160 0.00000 
                BH SSE folding 0.00310 0.00000 

Flopcounter: 23085180378860.839844

Spike count:    0
Pulse count:    0
Triplet count:  0
Gaussian count: 0
called boinc_finish

</stderr_txt>
 
Validate state Initial 
Claimed credit 0 
Granted credit 0 
application version 6.03

---

I just noticed this WU where my valid result claimed 43.87 but was granted zero. Seems my wingman also returned a valid result but his result claimed zero. And, looking at his Tasks for computer, it seems he is doing that a lot. Anybody know what his problem may be?

---

<core_client_version>4.43</core_client_version>
The above is probably the reason. Good time to get that person to upgrade.

---

My movie https://vimeo.com/manage/videos/502242

Stick found now an other rig also..

Host returning valid results but claiming zero credit

It's look like there is a prob with SETI@home V6.x and BOINC V4.x ??

---

A mod combined the two threads..

Not that you think I'm crazy.. ;-D

---

Pooh Bear 27 wrote:

<core_client_version>4.43</core_client_version>
The above is probably the reason. Good time to get that person to upgrade.

Good time to get all BOINC 4.xx users to upgrade...
Question remains... How?

---