Welcome to MilkyWay@home

Again a lot of inconclusive WU


Advanced search

Message boards : Number crunching : Again a lot of inconclusive WU
Message board moderation

To post messages, you must log in.

AuthorMessage
ProfileMarsinph

Send message
Joined: 13 Nov 10
Posts: 21
Credit: 85,658,679
RAC: 429,825
50 million credit badge8 year member badge
Message 67541 - Posted: 27 May 2018, 16:03:19 UTC

I run several hosts, differents CPU/GPU and drivers. All are visible.
About 50% of my WU finish in "inconclusive"
Reset project not change anything.
Who can explain ?

Only one example on host 772323 task reported on 27 May 2018, 14:45:30 UTC:
WU : http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=2345832727

here the result :
<core_client_version>7.8.3</core_client_version>
<![CDATA[
<stderr_txt>
<search_application> milkyway_separation 1.46 Windows x86 double OpenCL </search_application>
Reading preferences ended prematurely
BOINC GPU type suggests using OpenCL vendor 'NVIDIA Corporation'
Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4'
Switching to Parameter File 'astronomy_parameters.txt'
<number_WUs> 4 </number_WUs>
<number_params_per_WU> 26 </number_params_per_WU>
Using AVX path
Found 2 platforms
Platform 0 information:
Name: Intel(R) OpenCL
Version: OpenCL 1.1
Vendor: Intel(R) Corporation
Extensions: cl_khr_fp64 cl_khr_icd cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_intel_printf cl_ext_device_fission cl_intel_exec_by_local_thread cl_khr_gl_sharing cl_intel_dx9_media_sharing
Profile: FULL_PROFILE
Platform 1 information:
Name: NVIDIA CUDA
Version: OpenCL 1.2 CUDA 9.1.84
Vendor: NVIDIA Corporation
Extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d9_sharing cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_nv_create_buffer
Profile: FULL_PROFILE
Using device 0 on platform 1
Found 1 CL device
Device 'GeForce GTX 660 Ti' (NVIDIA Corporation:0x10de) (CL_DEVICE_TYPE_GPU)
Board:
Driver version: 391.35
Version: OpenCL 1.2 CUDA
Compute capability: 3.0
Max compute units: 7
Clock frequency: 1019 Mhz
Global mem size: 2147483648
Local mem size: 49152
Max const buf size: 65536
Double extension: cl_khr_fp64
Build log:
--------------------------------------------------------------------------------

ptxas info : 0 bytes gmem
ptxas info : Compiling entry function 'probabilities' for 'sm_30'
ptxas info : Function properties for probabilities
ptxas . 88 bytes stack frame, 88 bytes spill stores, 88 bytes spill loads
ptxas info : Used 63 registers, 388 bytes cmem[0], 192 bytes cmem[2]
--------------------------------------------------------------------------------
Build log:
--------------------------------------------------------------------------------


--------------------------------------------------------------------------------
Estimated Nvidia GPU GFLOP/s: 457 SP GFLOP/s, 57 DP FLOP/s
Using a target frequency of 60.0
Using a block size of 7168 with 3 blocks/chunk
Using clWaitForEvents() for polling with initial wait of 12 ms (mode 0)
Range: { nu_steps = 320, mu_steps = 800, r_steps = 700 }
Iteration area: 560000
Chunk estimate: 25
Num chunks: 27
Chunk size: 21504
Added area: 20608
Effective area: 580608
Initial wait: 12 ms
Integration time: 103.951829 s. Average time per iteration = 324.849464 ms
Integral 0 time = 104.244788 s
Running likelihood with 105909 stars
Likelihood time = 3.284353 s
<background_integral> 0.000284743840772 </background_integral>
<stream_integral> 17.319658417097891 58.469920218966763 34.338911055615576 130.958487119280560 </stream_integral>
<background_likelihood> -3.848259408944410 </background_likelihood>
<stream_only_likelihood> -8.867280025413010 -7.113552895208501 -5.498261223672279 -4.738707394817920 </stream_only_likelihood>
<search_likelihood> -3.456982689289115 </search_likelihood>
Using AVX path
Found 2 platforms
Platform 0 information:
Name: Intel(R) OpenCL
Version: OpenCL 1.1
Vendor: Intel(R) Corporation
Extensions: cl_khr_fp64 cl_khr_icd cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_intel_printf cl_ext_device_fission cl_intel_exec_by_local_thread cl_khr_gl_sharing cl_intel_dx9_media_sharing
Profile: FULL_PROFILE
Platform 1 information:
Name: NVIDIA CUDA
Version: OpenCL 1.2 CUDA 9.1.84
Vendor: NVIDIA Corporation
Extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d9_sharing cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_nv_create_buffer
Profile: FULL_PROFILE
Using device 0 on platform 1
Found 1 CL device
Device 'GeForce GTX 660 Ti' (NVIDIA Corporation:0x10de) (CL_DEVICE_TYPE_GPU)
Board:
Driver version: 391.35
Version: OpenCL 1.2 CUDA
Compute capability: 3.0
Max compute units: 7
Clock frequency: 1019 Mhz
Global mem size: 2147483648
Local mem size: 49152
Max const buf size: 65536
Double extension: cl_khr_fp64
Build log:
--------------------------------------------------------------------------------

ptxas info : 0 bytes gmem
ptxas info : Compiling entry function 'probabilities' for 'sm_30'
ptxas info : Function properties for probabilities
ptxas . 88 bytes stack frame, 88 bytes spill stores, 88 bytes spill loads
ptxas info : Used 63 registers, 388 bytes cmem[0], 192 bytes cmem[2]
--------------------------------------------------------------------------------
Build log:
--------------------------------------------------------------------------------


--------------------------------------------------------------------------------
Estimated Nvidia GPU GFLOP/s: 457 SP GFLOP/s, 57 DP FLOP/s
Using a target frequency of 60.0
Using a block size of 7168 with 3 blocks/chunk
Using clWaitForEvents() for polling with initial wait of 12 ms (mode 0)
Range: { nu_steps = 320, mu_steps = 800, r_steps = 700 }
Iteration area: 560000
Chunk estimate: 25
Num chunks: 27
Chunk size: 21504
Added area: 20608
Effective area: 580608
Initial wait: 12 ms
Integration time: 103.838871 s. Average time per iteration = 324.496473 ms
Integral 0 time = 104.097595 s
Running likelihood with 105909 stars
Likelihood time = 3.301412 s
<background_integral1> 0.000208548877383 </background_integral1>
<stream_integral1> 7.183842826970896 6.050607607478074 131.116063954778440 136.069997376314350 </stream_integral1>
<background_likelihood1> -3.246748158608996 </background_likelihood1>
<stream_only_likelihood1> -156.747168167884980 -6.308060222467828 -4.498746132987833 -3.875166485076218 </stream_only_likelihood1>
<search_likelihood1> -2.985156551554780 </search_likelihood1>
Using AVX path
Found 2 platforms
Platform 0 information:
Name: Intel(R) OpenCL
Version: OpenCL 1.1
Vendor: Intel(R) Corporation
Extensions: cl_khr_fp64 cl_khr_icd cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_intel_printf cl_ext_device_fission cl_intel_exec_by_local_thread cl_khr_gl_sharing cl_intel_dx9_media_sharing
Profile: FULL_PROFILE
Platform 1 information:
Name: NVIDIA CUDA
Version: OpenCL 1.2 CUDA 9.1.84
Vendor: NVIDIA Corporation
Extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d9_sharing cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_nv_create_buffer
Profile: FULL_PROFILE
Using device 0 on platform 1
Found 1 CL device
Device 'GeForce GTX 660 Ti' (NVIDIA Corporation:0x10de) (CL_DEVICE_TYPE_GPU)
Board:
Driver version: 391.35
Version: OpenCL 1.2 CUDA
Compute capability: 3.0
Max compute units: 7
Clock frequency: 1019 Mhz
Global mem size: 2147483648
Local mem size: 49152
Max const buf size: 65536
Double extension: cl_khr_fp64
Build log:
--------------------------------------------------------------------------------

ptxas info : 0 bytes gmem
ptxas info : Compiling entry function 'probabilities' for 'sm_30'
ptxas info : Function properties for probabilities
ptxas . 88 bytes stack frame, 88 bytes spill stores, 88 bytes spill loads
ptxas info : Used 63 registers, 388 bytes cmem[0], 192 bytes cmem[2]
--------------------------------------------------------------------------------
Build log:
--------------------------------------------------------------------------------


--------------------------------------------------------------------------------
Estimated Nvidia GPU GFLOP/s: 457 SP GFLOP/s, 57 DP FLOP/s
Using a target frequency of 60.0
Using a block size of 7168 with 3 blocks/chunk
Using clWaitForEvents() for polling with initial wait of 12 ms (mode 0)
Range: { nu_steps = 320, mu_steps = 800, r_steps = 700 }
Iteration area: 560000
Chunk estimate: 25
Num chunks: 27
Chunk size: 21504
Added area: 20608
Effective area: 580608
Initial wait: 12 ms
Integration time: 103.803421 s. Average time per iteration = 324.385692 ms
Integral 0 time = 104.075746 s
Running likelihood with 105909 stars
Likelihood time = 3.456925 s
<background_integral2> 0.000281112050799 </background_integral2>
<stream_integral2> 55.476683483824004 143.577216720719750 132.522152232704260 145.004495759717860 </stream_integral2>
<background_likelihood2> -3.230824250373391 </background_likelihood2>
<stream_only_likelihood2> -8.346098555512612 -5.756739375965045 -4.539520916381097 -3.880423154679968 </stream_only_likelihood2>
<search_likelihood2> -2.985603626824625 </search_likelihood2>
Using AVX path
Found 2 platforms
Platform 0 information:
Name: Intel(R) OpenCL
Version: OpenCL 1.1
Vendor: Intel(R) Corporation
Extensions: cl_khr_fp64 cl_khr_icd cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_intel_printf cl_ext_device_fission cl_intel_exec_by_local_thread cl_khr_gl_sharing cl_intel_dx9_media_sharing
Profile: FULL_PROFILE
Platform 1 information:
Name: NVIDIA CUDA
Version: OpenCL 1.2 CUDA 9.1.84
Vendor: NVIDIA Corporation
Extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d9_sharing cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_nv_create_buffer
Profile: FULL_PROFILE
Using device 0 on platform 1
Found 1 CL device
Device 'GeForce GTX 660 Ti' (NVIDIA Corporation:0x10de) (CL_DEVICE_TYPE_GPU)
Board:
Driver version: 391.35
Version: OpenCL 1.2 CUDA
Compute capability: 3.0
Max compute units: 7
Clock frequency: 1019 Mhz
Global mem size: 2147483648
Local mem size: 49152
Max const buf size: 65536
Double extension: cl_khr_fp64
Build log:
--------------------------------------------------------------------------------

ptxas info : 0 bytes gmem
ptxas info : Compiling entry function 'probabilities' for 'sm_30'
ptxas info : Function properties for probabilities
ptxas . 88 bytes stack frame, 88 bytes spill stores, 88 bytes spill loads
ptxas info : Used 63 registers, 388 bytes cmem[0], 192 bytes cmem[2]
--------------------------------------------------------------------------------
Build log:
--------------------------------------------------------------------------------


--------------------------------------------------------------------------------
Estimated Nvidia GPU GFLOP/s: 457 SP GFLOP/s, 57 DP FLOP/s
Using a target frequency of 60.0
Using a block size of 7168 with 3 blocks/chunk
Using clWaitForEvents() for polling with initial wait of 12 ms (mode 0)
Range: { nu_steps = 320, mu_steps = 800, r_steps = 700 }
Iteration area: 560000
Chunk estimate: 25
Num chunks: 27
Chunk size: 21504
Added area: 20608
Effective area: 580608
Initial wait: 12 ms
Integration time: 103.831190 s. Average time per iteration = 324.472470 ms
Integral 0 time = 104.104368 s
Running likelihood with 105909 stars
Likelihood time = 3.473803 s
<background_integral3> 0.000233786273315 </background_integral3>
<stream_integral3> 1.713684006446096 22.928553856992149 130.035655743465500 121.103056620650020 </stream_integral3>
<background_likelihood3> -3.237119608366839 </background_likelihood3>
<stream_only_likelihood3> -206.802178374178740 -6.575508375141300 -4.561786794245808 -3.887084418890165 </stream_only_likelihood3>
<search_likelihood3> -2.985372620851952 </search_likelihood3>
16:45:21 (4168): called boinc_finish(0)

</stderr_txt>
]]>
ID: 67541 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Jim1348

Send message
Joined: 9 Jul 17
Posts: 59
Credit: 6,779,381
RAC: 5,146
5 million credit badge2 year member badge
Message 67542 - Posted: 27 May 2018, 16:29:01 UTC - in response to Message 67541.  

I run several hosts, differents CPU/GPU and drivers. All are visible.
About 50% of my WU finish in "inconclusive"
Reset project not change anything.
Who can explain ?

The proper phrase is "Validation inconclusive". It means they have not been compared with the results from other users. About half of mine are in that status too. That will eventually be compared, and usually validated.
ID: 67542 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
ROSSOTRON

Send message
Joined: 28 Sep 17
Posts: 17
Credit: 58,038,932
RAC: 0
50 million credit badge2 year member badge
Message 67543 - Posted: 28 May 2018, 0:58:01 UTC - in response to Message 67542.  

^ this.

it’s the “invalid” and “error” you need to worry about.
ID: 67543 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Elvis

Send message
Joined: 9 Feb 11
Posts: 11
Credit: 39,885,909
RAC: 54,566
30 million credit badge8 year member badge
Message 67566 - Posted: 4 Jun 2018, 20:07:16 UTC

Hello
I have an Amd Radeon 380X graphic card and I have lot's of computation errors almost 50%
Once again It seams that this project has unsolved computation issues on amd/ati graphic cards.

The team of this...so called "project" is probably not up to the task for fixing their own issues with graphic card computation. It is happenning very often, I mean very very often!

So it's a shit project for me !
I won't waste computation time and electricity on Milkyway anymore despite my respectable score and history.

If, like me you have lot's of computation errors with this...?project?
Crunch on Einstein at home wich is issue and error free !

Sincerly
Elvis
ID: 67566 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Profilemikey
Avatar

Send message
Joined: 8 May 09
Posts: 2254
Credit: 350,109,407
RAC: 950,528
300 million credit badge10 year member badgeextraordinary contributions badge
Message 67572 - Posted: 5 Jun 2018, 10:46:59 UTC - in response to Message 67566.  

Hello
I have an Amd Radeon 380X graphic card and I have lot's of computation errors almost 50%
Once again It seams that this project has unsolved computation issues on amd/ati graphic cards.

The team of this...so called "project" is probably not up to the task for fixing their own issues with graphic card computation. It is happenning very often, I mean very very often!

So it's a shit project for me !
I won't waste computation time and electricity on Milkyway anymore despite my respectable score and history.

If, like me you have lot's of computation errors with this...?project?
Crunch on Einstein at home wich is issue and error free !

Sincerly
Elvis


I've been using an AMD 5870 here for a LONG time and it works just fine, when I look at my pc it says this: AMD ATI Radeon HD 5800/5900 series (Cypress/Hemlock) (1024MB) driver: 1.4.1848 OpenCL: 1.2

But when I look at your pc it says this: AMD AMD Radeon (TM) R9 380 Series (4096MB) OpenCL: 2.0

It looks like the AMD driver is not loaded or didn't take if you did load it. You have to manually load the AMD drivers, Nvidia ones too if you have an Nvidia card, as Windows does NOT load any drivers that can be used to crunch with.
ID: 67572 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Jake Weiss
Volunteer moderator
Project developer
Project tester
Project scientist

Send message
Joined: 25 Feb 13
Posts: 580
Credit: 75,271,794
RAC: 1
50 million credit badge6 year member badgeextraordinary contributions badge
Message 67576 - Posted: 5 Jun 2018, 16:55:47 UTC

Hey Elvis,

I looked through your workunit history and it seems as though the problem occurs on the second to last, or last workunit in a bundle. Can you please look to see if your GPU is running out of memory, or if there is another issue where you drivers are crashing late in the workunit?

I am sorry you are having issues with your project and I understand your frustration.

Jake
ID: 67576 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote
Magiceye04

Send message
Joined: 14 Feb 10
Posts: 2
Credit: 11,131,137
RAC: 40
10 million credit badge9 year member badge
Message 67584 - Posted: 9 Jun 2018, 18:20:47 UTC - in response to Message 67542.  

I run several hosts, differents CPU/GPU and drivers. All are visible.
About 50% of my WU finish in "inconclusive"
Reset project not change anything.
Who can explain ?

The proper phrase is "Validation inconclusive". It means they have not been compared with the results from other users. About half of mine are in that status too. That will eventually be compared, and usually validated.

But the correct state for this would be "waiting for validation" like in other projects. Why is using Milkyway this misunderstanding state that is normally used, when 2 PCs deliver different results - and therfore really need a 3rd or 4th run?
ID: 67584 · Rating: 0 · rate: Rate + / Rate - Report as offensive     Reply Quote

Message boards : Number crunching : Again a lot of inconclusive WU

©2019 Astroinformatics Group