Update on This Weeks Errors
log in

Advanced search

Message boards : News : Update on This Weeks Errors

Previous · 1 · 2
Author Message
Jake Weiss
Volunteer moderator
Project developer
Project tester
Project scientist
Send message
Joined: 25 Feb 13
Posts: 438
Credit: 9,338,855
RAC: 138,986

Message 66750 - Posted: 23 Oct 2017, 23:46:05 UTC

Yes, it seems like it is functioning normally now. It is common to have 70+ results waiting for validation as each workunit it crunched 2-3 times each to ensure no one is running faulty hardware or trying to cheat for credits. I see you do have one mistakenly marked as invalid. This must have happened in the weird in-between period after I told the server to revalidate those types of workunit. I'll have the server revalidate that one tomorrow.

Jake

HassanShebli
Send message
Joined: 2 Oct 10
Posts: 72
Credit: 17,079,518
RAC: 2

Message 66751 - Posted: 24 Oct 2017, 1:36:29 UTC - in response to Message 66750.

Let's hope everything run smoothly

Thanks for your efforts

Cameron
Send message
Joined: 16 Dec 07
Posts: 19
Credit: 386,042
RAC: 64

Message 66755 - Posted: 29 Oct 2017, 4:42:48 UTC - in response to Message 66726.


Our project has been running for upwards of 10 years now and we have been crunching literally billions of workunits over those years. As a result of all of your hard work and dedication, we have actually calculated enough results that we have run out of room to store the IDs of all of these results in a normal unsigned integer value (the default data type used for storing IDs in BOINC databases). As a result, on Tuesday night, I updated our database to be able to store IDs in a much larger data type to prevent this issue from happening again during the remaining life of the project. As a result, I also had to quickly patch the BOINC code we run on the server to allow it to use this newly available data type in the database.


Just wondering If you know how much longer the project plans to run?

Leif
Send message
Joined: 9 Apr 15
Posts: 1
Credit: 428,113
RAC: 1,029

Message 66768 - Posted: 5 Nov 2017, 10:28:06 UTC

Hi,

I get lots of computational errors

MW@Home 1.46 (opencl_ati_101) de_modfit_fast_19_3s_146_bundle5_ModfitConstraintsWithDiskandUpdateStreams_1_//different IDs//

I7-4930K 3.4GHz
Win 10 Pro version 1709 Build 16299.19 64bit
AMD Radeon HD 6900 Series
Boinc 7.8.3 WxWidgets 3.0.1
____________

Tom*
Send message
Joined: 4 Oct 11
Posts: 33
Credit: 267,865,743
RAC: 398,213

Message 66772 - Posted: 6 Nov 2017, 4:25:01 UTC

Leif

Your GPU does not support double precision so cannot be used for this project.
from STDERR

Board: AMD Radeon HD 6800 Series
Driver version: 1800.11 (VM)
Version: OpenCL 1.2 AMD-APP (1800.11)
Compute capability: 0.0
Max compute units: 12
Clock frequency: 820 Mhz
Global mem size: 1073741824
Local mem size: 32768
Max const buf size: 65536
Double extension: (none)
Device doesn't support double precision

HassanShebli
Send message
Joined: 2 Oct 10
Posts: 72
Credit: 17,079,518
RAC: 2

Message 66773 - Posted: 8 Nov 2017, 2:48:35 UTC - in response to Message 66772.

Leif

Your GPU does not support double precision so cannot be used for this project.
from STDERR

Board: AMD Radeon HD 6800 Series
Driver version: 1800.11 (VM)
Version: OpenCL 1.2 AMD-APP (1800.11)
Compute capability: 0.0
Max compute units: 12
Clock frequency: 820 Mhz
Global mem size: 1073741824
Local mem size: 32768
Max const buf size: 65536
Double extension: (none)
Device doesn't support double precision


His card is 6900 not 6800 so it does support Milkyway

Tom*
Send message
Joined: 4 Oct 11
Posts: 33
Credit: 267,865,743
RAC: 398,213

Message 66776 - Posted: 8 Nov 2017, 17:36:14 UTC

Not if the card reports or BOINC thinks its a 6800 series

AMD AMD Radeon HD 6790/6850/6870 series (Barts) (1024MB) driver: 1.4.1848 OpenCL: 1.2

Previous · 1 · 2
Post to thread

Message boards : News : Update on This Weeks Errors


Main page · Your account · Message boards


Copyright © 2017 AstroInformatics Group