. . Hi raistmer,

. . I have an update ...

. . I found a link on the Beta home page that leads to the results and ALL those tasks ARE HAR with a value of 0.94nnn and all about the same value. I also realised that machine is host #80139 on Beta. This machine I am using shows as host #80138 but is not being used and there is NO Beta project on this machine.

. . Sorry if I caused any confusion.

Stephen

.

Dr. K increased the size of the work units on Beta to 700KB to see if they had any impact on the processing of the work units.

Originally MB work units were cut down to smaller sizes to allow for better computations long time ago when they were sent out.

So the question was, did the work units need to be "cut down" or could the larger size work units be crunched and if so, how would it affect they times.

There is no problems crunching the larger work units and the times did not change significantly.

. . hi Zalster,

. . Yes I have seen the announcements about changing to the 4bit format, so that explains why the files are 700KB now. It turns out the WUs I have been getting are all HAR with values pretty much all 0.94nnn and that explains why their runtimes are so short. I get excited really easily sometimes :). But it does mean, as you said, that runtimes are pretty much the same as for 2bit WUs which is a good thing. They give much better resolution to the analysis apparently and the only detriment is twice the data to download. I wonder when they will make it to main.

. . r3528 is looking pretty good, it is running well on my small unit. I look forward to Richard achieving his intention to release it as Lunatics 0.45 Beta(5), then I can run it on my other rig without having to port that rig across to Beta :).

. . I am hoping it will work even better than r3430 which I am running ATM.

Stephen

.

"host #7972413" is the number here.
What it is on S@H-Beta?
Because no other projects are shown still for you here to click on them:
http://setiathome.berkeley.edu/show_user.php?userid=9780569

EDIT:
OK, you posted the S@H-Beta hostid=80139 while I was writing this post:
http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=80139

    I can't see a tasks or computers button to check the results for task AR so I am in the dark there

If you can see the stderr.txt you can see the AR

1) For reported tasks:
http://setiathome.berkeley.edu/result.php?resultid=5156999889
Lines:
ar=3.056596
WU true angle range is : 3.056596

2) For running tasks:
(the same lines as above) look in {BOINC-Data}\slots\ for stderr.txt

3) For not started tasks:
look in the WU file:
<true_angle_range>0.012198483347679</true_angle_range>


P.S.
You don't need to abort tasks here to run S@H-Beta
http://setiathome.berkeley.edu/results.php?hostid=7972413&offset=0&show_names=0&state=6&appid=

You may put a project on "pause" by [Suspend] button on Projects tab:
BOINC Manager Advanced view

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

If you can see the stderr.txt you can see the AR

3) For not started tasks:
look in the WU file:
<true_angle_range>0.012198483347679</true_angle_range>

. . Hi, thanks for that detail. I actually knew where to find it in the results for each task, but in main I get there by pressing the "Computers" button. That button doesn't show up for Beta so I could not navigate to that info. I eventually worked out that I could get there by going to Beta home page and there is a link there to take me to the right place.

You don't need to abort tasks here to run S@H-Beta
http://setiathome.berkeley.edu/results.php?hostid=7972413&offset=0&show_names=0&state=6&appid=

You may put a project on "pause" by [Suspend] button on Projects tab:
BOINC Manager Advanced view

. . I am still running MainWUs on the CPU and beta on the GPU. But even though I set up specs for location "Work" to do only CPU tasks and changed that rig to location "Work", for some reason it continued to send me GPU tasks for the first couple of updates. Since I couldn't "reschedule" them with Beta running I took the easy way out and aborted them. At first I just suspended them but that stops you getting new work, so I went postal on them.

Stephen

.

Do apps produce the right answer for every possible case that the radio telescopes and data recorders - themselves subject to error and failure - throw at us?

If you can design a testing regime that answers that last question, you've probably talked yourself into a job.

WAY beyond my pay grade, Richard :) Appreciate the info ...

---

It seems you registered as separate entity on beta site. Different E-mail used perhaps.
So, your main and beta accounts did not linked together. No "volunteer tester" tag, no beta project link in your participated projects list and so on.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

But even though I set up specs for location "Work" to do only CPU tasks and changed that rig to location "Work", for some reason it continued to send me GPU tasks for the first couple of updates.

Yes, there are some web settings that 'don't take' if the local BOINC don't know about them.

To avoid confusion in the future:
- set [No New Tasks]
- change web Settings
- click [Update] (usually one update is enough but you may try two if you wish)
- set [Allow New Tasks]

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

It seems you registered as separate entity on beta site. Different E-mail used perhaps.
So, your main and beta accounts did not linked together. No "volunteer tester" tag, no beta project link in your participated projects list and so on.

. . Thanks for letting me know about that. That was unintentional. I tried the email address I thought I used in main but it was rejected for some reason so I tried the one it said was used in main. I must have been right the first time.

Stephen

.

But even though I set up specs for location "Work" to do only CPU tasks and changed that rig to location "Work", for some reason it continued to send me GPU tasks for the first couple of updates.

Yes, there are some web settings that 'don't take' if the local BOINC don't know about them.

To avoid confusion in the future:
- set [No New Tasks]
- change web Settings
- click [Update] (usually one update is enough but you may try two if you wish)
- set [Allow New Tasks]

. . Yes, that would have been a good idea. A shame I did not think to do that :(.

. . I will try to remember that if the occasion arises in the future.

Stephen

.

It seems you registered as separate entity on beta site. Different E-mail used perhaps.
So, your main and beta accounts did not linked together. No "volunteer tester" tag, no beta project link in your participated projects list and so on.

. . Would it be more useful if I was to correct that? That is would I be able to see that machines results in Beta-Test from the other machines?

. . And perhaps a more important question. Is it possible to correct that?


Stephen

.

WARNING - the latest round of 64-bit Windows 10 updates appears to have blocked BOINC from finding the OpenCL interface to my GT 440. The CUDA interface does not seem to be affected.

WARNING - the latest round of 64-bit Windows 10 updates appears to have blocked BOINC from finding the OpenCL interface to my GT 440. The CUDA interface does not seem to be affected.

Cross posting (spamming) threads tends to annoy people more than help.

---

Grant
Darwin NT

And its off topic in this case as well.

---

With each crime and every kindness we birth our future.

WARNING - the latest round of 64-bit Windows 10 updates appears to have blocked BOINC from finding the OpenCL interface to my GT 440. The CUDA interface does not seem to be affected.

Robert, I posted a message about this in the Windows 10 Yea or Nay thread. Might check there for an explanation, if applicable.

---

WARNING - the latest round of 64-bit Windows 10 updates appears to have blocked BOINC from finding the OpenCL interface to my GT 440. The CUDA interface does not seem to be affected.

Robert, I posted a message about this in the Windows 10 Yea or Nay thread. Might check there for an explanation, if applicable.

Thanks - I applied that change.

WARNING - the latest round of 64-bit Windows 10 updates appears to have blocked BOINC from finding the OpenCL interface to my GT 440. The CUDA interface does not seem to be affected.

. . I suspect it haas changed your video driver in some way, you may want to re-install from an Nvidia download rather than trust the MS drivers.

Stephen

.

WARNING - the latest round of 64-bit Windows 10 updates appears to have blocked BOINC from finding the OpenCL interface to my GT 440. The CUDA interface does not seem to be affected.

. . I suspect it haas changed your video driver in some way, you may want to re-install from an Nvidia download rather than trust the MS drivers.

Stephen

.

That's what worked. Apparently, the MS version of the Nvidia graphics drivers often don't include the OpenCL portion.

I think we finished with massive testing of 8.19.
Hope Eric will have some time for release after returning from conference.
Next version not ready for beta for now, I'll make announcement when it will be ready.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

I have installed the GTX 750 on my Linux box and it works. But it still uses 8.10. CPU usage is very high, near 100% on one of the 2 cores of the Opteron 1210, vintage 2008. The other is shared by Einstein, LHC@home and Atlas@home.
Tullio

---

A 8.01 version with CUDA 60 instead of opencl_nvidia_sah lowers the CPU usage to 7%.
Tullio

---