Nvidia Astropulse Minimum driver version

Message boards : AstroPulse : Nvidia Astropulse Minimum driver version
Message board moderation

To post messages, you must log in.

AuthorMessage
Claggy
Volunteer tester

Send message
Joined: 29 May 06
Posts: 1037
Credit: 8,440,339
RAC: 21
United Kingdom
Message 49962 - Posted: 15 Mar 2014, 19:03:08 UTC

@Eric,

The minimum driver version for the Nvidia Astropulse app needs to be 263.00, anything lower always produces repetitive pulses: 30,
it did several years ago when I tested the 260.99 driver, and still does as you can see from this Wu:

http://setiathome.berkeley.edu/workunit.php?wuid=1429520347

<core_client_version>7.2.33</core_client_version>
<![CDATA[
<stderr_txt>
Running on device number: 0
DATA_CHUNK_UNROLL at default:2
DATA_CHUNK_UNROLL at default:2
Priority of worker thread raised successfully
Priority of process adjusted successfully, below normal priority class used
OpenCL platform detected: NVIDIA Corporation
BOINC assigns device 0
Info: BOINC provided device ID used
Used GPU device parameters are:
Number of compute units: 4
Single buffer allocation size: 128MB
max WG size: 512
FERMI path used: no

Build features: Non-graphics OpenCL USE_OPENCL_NV COMBINED_DECHIRP_KERNEL FFTW USE_INCREASED_PRECISION USE_SSE2 x86
CPUID: Intel(R) Core(TM)2 Duo CPU T8100 @ 2.10GHz

Cache: L1=64K L2=3072K

CPU features: FPU TSC PAE CMPXCHG8B APIC SYSENTER MTRR CMOV/CCMP MMX FXSAVE/FXRSTOR SSE SSE2 HT SSE3
AstroPulse v.6
Non-graphics FFTW USE_CONVERSION_OPT
Windows x86 rev 1316, V6 match, by Raistmer with support of Lunatics.kwsn.net team. SSE2

OpenCL version by Raistmer

ffa threshold mods by Joe Segur
SSE3 dechirping by JDWhale
Combined dechirp kernel by Frizz
Number of OpenCL platforms: 1


OpenCL Platform Name: NVIDIA CUDA
Number of devices: 1
Max compute units: 4
Max work group size: 512
Max clock frequency: 950Mhz
Max memory allocation: 134217728
Cache type: None
Cache line size: 0
Cache size: 0
Global memory size: 251199488
Constant buffer size: 65536
Max number of constant args: 9
Local memory type: Scratchpad
Local memory size: 16384
Queue properties:
Out-of-Order: Yes
Name: GeForce 8600M GT
Vendor: NVIDIA Corporation
Driver version: 260.99
Version: OpenCL 1.0 CUDA
Extensions: cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_d3d9_sharing cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics


state.fold_buf_size_short=65536; state.fold_buf_size_long=262144
Info : Building Program (binary, clBuildProgram):main kernels: OK code 0

: Considering profile 'compute_11' for gpu='sm_11' in 'cuModuleLoadDataEx_4'

single pulses: 5
repetitive pulses: 30
percent blanked: 2.44
class T_remove_radar: total=2.92e+009, N=1, <>=2.92e+009, min=2.92e+009, max=2.92e+009
class T_main_loop_L1: total=4.51e+013, N=111, <>=4.07e+011, min=3.92e+011, max=4.60e+011
class T_FFT_forward: total=3.01e+010, N=909312, <>=3.31e+004, min=1.87e+004, max=7.58e+007
class T_remove_radar_randomize: total=4.80e+011, N=1817736, <>=2.64e+005, min=6.82e+002, max=1.11e+009
class T_build_chirp_table: total=0.00e+000, N=0, <>=0.00e+000, min=1.84e+019, max=0.00e+000
class T_DataWrite: total=8.52e+008, N=22200, <>=3.84e+004, min=9.20e+003, max=2.63e+007
class T_DataWrite_ns: total=0, N=0, <>=0, min=0 max=0
class T_oclReadBuf: total=3.19e+007, N=909312, <>=3.50e+001, min=3.10e+001, max=1.53e+004
class T_ChirpWrite: total=0.00e+000, N=0, <>=0.00e+000, min=1.84e+019, max=0.00e+000
class T_ChirpWrite_ns: total=0, N=0, <>=0, min=0 max=0
class T_dechirp: total=4.04e+010, N=909312, <>=4.44e+004, min=3.16e+004, max=1.23e+008
class Dechirp_ns: total=0, N=0, <>=0, min=0 max=0
class Half_ns: total=0, N=0, <>=0, min=0 max=0
class T_PC_single_pulse_kernel_FFA_update: total=4.45e+013, N=909312, <>=4.89e+007, min=4.40e+007, max=1.33e+010
class PC_ns: total=0, N=0, <>=0, min=0 max=0
class T_oclReadBuf: total=3.19e+007, N=909312, <>=3.50e+001, min=3.10e+001, max=1.53e+004
class T_oclWriteBuf: total=8.62e+008, N=22200, <>=3.88e+004, min=9.49e+003, max=2.63e+007
class T_FFT_inverse: total=2.46e+010, N=909312, <>=2.70e+004, min=1.99e+004, max=6.66e+007
class T_ffa: total=1.87e+010, N=1, <>=1.87e+010, min=1.87e+010, max=1.87e+010
class T_GPU_buffer_read_backs: total=6, N=6, <>=1, min=1 max=1
USE_OPENCL OPENCL_WRITE USE_INCREASED_PRECISION SMALL_CHIRP_TABLE COMBINED_DECHIRP_KERNEL
rev 1316
00:59:39 (3788): called boinc_finish

</stderr_txt>
]]>


And if you look at other Nv AP results from this host, they all find repetitive pulses: 30 too:

http://setiathome.berkeley.edu/result.php?resultid=3366224905
http://setiathome.berkeley.edu/result.php?resultid=3390710980
http://setiathome.berkeley.edu/result.php?resultid=3391541078
http://setiathome.berkeley.edu/result.php?resultid=3400657608
http://setiathome.berkeley.edu/result.php?resultid=3400667074
http://setiathome.berkeley.edu/result.php?resultid=3401035330

The host has subsequently moved up to 334.89 drivers, but since it did it's compilations under the 260.99 driver it'll continue producing inconclusives until,
a) a new Nv AP app is released and the app does compilations under a driver that works.
b) the user does a detach, then reattach project (remove/add project).
c) the user manually deletes the compilations produced by the Nv AP app, and the app produces fresh compilations on a driver later than 263.00

Claggy
ID: 49962 · Report as offensive

Message boards : AstroPulse : Nvidia Astropulse Minimum driver version


 
©2019 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.