Message boards :
SETI@home Enhanced :
WUs with very unusual Autocorr parameters
Message board moderation
Author | Message |
---|---|
Send message Joined: 14 Oct 05 Posts: 1137 Credit: 1,848,733 RAC: 0 ![]() |
Yesterday I got 4 tasks from the 10fe09ab.22806.* splitter run with short estimates, today 2 more from 10fe09ab.1847.* . All have <autocorr_thresh>1000</autocorr_thresh> <autocorr_per_spectrum>0</autocorr_per_spectrum> <autocorr_fftlen>8</autocorr_fftlen> rather than the usual settings. I suspect that's an accident. The splitter estimate has a term which depends on the autocorr_fftlen, and doing DCTs at those short lengths will actually be a lot faster, so the reduced estimates may be OK. In theory, all app versions ought to be able to handle the unusual processing, but probably none have actually been previously tested that way so there may be surprises. Beta testing is often interesting. I'll ask Eric to comment if he has time. Joe |
Send message Joined: 30 Dec 13 Posts: 258 Credit: 12,340,341 RAC: 0 ![]() |
Hey Joe, I think I ran across a bunch of those MB with the unusual auto correct. My 2 machines here both just hit the wall. Ok, found this. Now to decipher it slot 0 setiathome_CUDA: Found 3 CUDA device(s): Device 1: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 5, pciSlotID = 0 Device 2: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 1, pciSlotID = 0 Device 3: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 2, pciSlotID = 0 In cudaAcc_initializeDevice(): Boinc passed DevPref 1 setiathome_CUDA: CUDA Device 1 specified, checking... Device 1: GeForce GTX 780 is okay SETI@home using CUDA accelerated device GeForce GTX 780 pulsefind: blocks per SM 4 (Fermi or newer default) pulsefind: periods per launch 100 (default) Priority of process set to BELOW_NORMAL (default) successfully Priority of worker thread set successfully setiathome enhanced x41zc, Cuda 4.20 Detected setiathome_enhanced_v7 task. Autocorrelations enabled, size 0k elements. Work Unit Info: ............... WU true angle range is : 0.545577 Kepler GPU current clockRate = 1071 MHz re-using dev_GaussFitResults array for dev_AutoCorrIn, 256 bytes re-using dev_GaussFitResults+32x8 array for dev_AutoCorrOut, 256 bytes Thread call stack limit is: 1k Error on launch (ac_reducePartial<<<grid3, block3,blksize*sizeof(float3)>>>( (float *)dev_AutoCorrIn, dev_ac_partials )), file c:/[Projects]/__Sources/sah_v7_opt/Xbranch/client/cuda/cudaAcc_autocorr.cu, line 200: invalid configuration argument Exiting cudaAcc_free() called... cudaAcc_free() running... cudaAcc_free() PulseFind freed... cudaAcc_free() Gaussfit freed... cudaAcc_free() AutoCorrelation freed... cudaAcc_free() DONE. Cuda sync'd & freed. Preemptively acknowledging a safe temporary exit-> Exit Status: 0 boinc_exit(): requesting safe worker shutdown -> boinc_exit(): received safe worker shutdown acknowledge -> Cuda threadsafe ExitProcess() initiated, rval 0 setiathome_CUDA: Found 3 CUDA device(s): Device 1: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 5, pciSlotID = 0 Device 2: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 1, pciSlotID = 0 Device 3: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 2, pciSlotID = 0 In cudaAcc_initializeDevice(): Boinc passed DevPref 1 setiathome_CUDA: CUDA Device 1 specified, checking... Device 1: GeForce GTX 780 is okay SETI@home using CUDA accelerated device GeForce GTX 780 pulsefind: blocks per SM 4 (Fermi or newer default) pulsefind: periods per launch 100 (default) Priority of process set to BELOW_NORMAL (default) successfully Priority of worker thread set successfully setiathome enhanced x41zc, Cuda 4.20 Detected setiathome_enhanced_v7 task. Autocorrelations enabled, size 0k elements. Work Unit Info: ............... WU true angle range is : 0.545577 Kepler GPU current clockRate = 1071 MHz re-using dev_GaussFitResults array for dev_AutoCorrIn, 256 bytes re-using dev_GaussFitResults+32x8 array for dev_AutoCorrOut, 256 bytes Thread call stack limit is: 1k Error on launch (ac_reducePartial<<<grid3, block3,blksize*sizeof(float3)>>>( (float *)dev_AutoCorrIn, dev_ac_partials )), file c:/[Projects]/__Sources/sah_v7_opt/Xbranch/client/cuda/cudaAcc_autocorr.cu, line 200: invalid configuration argument Exiting cudaAcc_free() called... cudaAcc_free() running... cudaAcc_free() PulseFind freed... cudaAcc_free() Gaussfit freed... cudaAcc_free() AutoCorrelation freed... cudaAcc_free() DONE. Cuda sync'd & freed. Preemptively acknowledging a safe temporary exit-> Exit Status: 0 boinc_exit(): requesting safe worker shutdown -> boinc_exit(): received safe worker shutdown acknowledge -> Cuda threadsafe ExitProcess() initiated, rval 0 setiathome_CUDA: Found 3 CUDA device(s): Device 1: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 5, pciSlotID = 0 Device 2: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 1, pciSlotID = 0 Device 3: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 2, pciSlotID = 0 In cudaAcc_initializeDevice(): Boinc passed DevPref 1 setiathome_CUDA: CUDA Device 1 specified, checking... Device 1: GeForce GTX 780 is okay SETI@home using CUDA accelerated device GeForce GTX 780 pulsefind: blocks per SM 4 (Fermi or newer default) pulsefind: periods per launch 100 (default) Priority of process set to BELOW_NORMAL (default) successfully Priority of worker thread set successfully setiathome enhanced x41zc, Cuda 4.20 Detected setiathome_enhanced_v7 task. Autocorrelations enabled, size 0k elements. Work Unit Info: ............... WU true angle range is : 0.545577 Kepler GPU current clockRate = 1071 MHz re-using dev_GaussFitResults array for dev_AutoCorrIn, 256 bytes re-using dev_GaussFitResults+32x8 array for dev_AutoCorrOut, 256 bytes Thread call stack limit is: 1k Error on launch (ac_reducePartial<<<grid3, block3,blksize*sizeof(float3)>>>( (float *)dev_AutoCorrIn, dev_ac_partials )), file c:/[Projects]/__Sources/sah_v7_opt/Xbranch/client/cuda/cudaAcc_autocorr.cu, line 200: invalid configuration argument Exiting cudaAcc_free() called... cudaAcc_free() running... cudaAcc_free() PulseFind freed... cudaAcc_free() Gaussfit freed... cudaAcc_free() AutoCorrelation freed... cudaAcc_free() DONE. Cuda sync'd & freed. Preemptively acknowledging a safe temporary exit-> Exit Status: 0 boinc_exit(): requesting safe worker shutdown -> boinc_exit(): received safe worker shutdown acknowledge -> Cuda threadsafe ExitProcess() initiated, rval 0 slot 6 setiathome_CUDA: Found 3 CUDA device(s): Device 1: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 5, pciSlotID = 0 Device 2: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 1, pciSlotID = 0 Device 3: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 2, pciSlotID = 0 In cudaAcc_initializeDevice(): Boinc passed DevPref 1 setiathome_CUDA: CUDA Device 1 specified, checking... Device 1: GeForce GTX 780 is okay SETI@home using CUDA accelerated device GeForce GTX 780 pulsefind: blocks per SM 4 (Fermi or newer default) pulsefind: periods per launch 100 (default) Priority of process set to BELOW_NORMAL (default) successfully Priority of worker thread set successfully setiathome enhanced x41zc, Cuda 4.20 Detected setiathome_enhanced_v7 task. Autocorrelations enabled, size 0k elements. Work Unit Info: ............... WU true angle range is : 0.545577 Kepler GPU current clockRate = 1071 MHz re-using dev_GaussFitResults array for dev_AutoCorrIn, 256 bytes re-using dev_GaussFitResults+32x8 array for dev_AutoCorrOut, 256 bytes Thread call stack limit is: 1k Error on launch (ac_reducePartial<<<grid3, block3,blksize*sizeof(float3)>>>( (float *)dev_AutoCorrIn, dev_ac_partials )), file c:/[Projects]/__Sources/sah_v7_opt/Xbranch/client/cuda/cudaAcc_autocorr.cu, line 200: invalid configuration argument Exiting cudaAcc_free() called... cudaAcc_free() running... cudaAcc_free() PulseFind freed... cudaAcc_free() Gaussfit freed... cudaAcc_free() AutoCorrelation freed... cudaAcc_free() DONE. Cuda sync'd & freed. Preemptively acknowledging a safe temporary exit-> Exit Status: 0 boinc_exit(): requesting safe worker shutdown -> boinc_exit(): received safe worker shutdown acknowledge -> Cuda threadsafe ExitProcess() initiated, rval 0 setiathome_CUDA: Found 3 CUDA device(s): Device 1: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 5, pciSlotID = 0 Device 2: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 1, pciSlotID = 0 Device 3: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 2, pciSlotID = 0 In cudaAcc_initializeDevice(): Boinc passed DevPref 2 setiathome_CUDA: CUDA Device 2 specified, checking... Device 2: GeForce GTX 780 is okay SETI@home using CUDA accelerated device GeForce GTX 780 pulsefind: blocks per SM 4 (Fermi or newer default) pulsefind: periods per launch 100 (default) Priority of process set to BELOW_NORMAL (default) successfully Priority of worker thread set successfully setiathome enhanced x41zc, Cuda 4.20 Detected setiathome_enhanced_v7 task. Autocorrelations enabled, size 0k elements. Work Unit Info: ............... WU true angle range is : 0.545577 Kepler GPU current clockRate = 1123 MHz re-using dev_GaussFitResults array for dev_AutoCorrIn, 256 bytes re-using dev_GaussFitResults+32x8 array for dev_AutoCorrOut, 256 bytes Thread call stack limit is: 1k Error on launch (ac_reducePartial<<<grid3, block3,blksize*sizeof(float3)>>>( (float *)dev_AutoCorrIn, dev_ac_partials )), file c:/[Projects]/__Sources/sah_v7_opt/Xbranch/client/cuda/cudaAcc_autocorr.cu, line 200: invalid configuration argument Exiting cudaAcc_free() called... cudaAcc_free() running... cudaAcc_free() PulseFind freed... cudaAcc_free() Gaussfit freed... cudaAcc_free() AutoCorrelation freed... cudaAcc_free() DONE. Cuda sync'd & freed. Preemptively acknowledging a safe temporary exit-> Exit Status: 0 boinc_exit(): requesting safe worker shutdown -> boinc_exit(): received safe worker shutdown acknowledge -> Cuda threadsafe ExitProcess() initiated, rval 0 setiathome_CUDA: Found 3 CUDA device(s): Device 1: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 5, pciSlotID = 0 Device 2: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 1, pciSlotID = 0 Device 3: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 2, pciSlotID = 0 In cudaAcc_initializeDevice(): Boinc passed DevPref 2 setiathome_CUDA: CUDA Device 2 specified, checking... Device 2: GeForce GTX 780 is okay SETI@home using CUDA accelerated device GeForce GTX 780 pulsefind: blocks per SM 4 (Fermi or newer default) pulsefind: periods per launch 100 (default) Priority of process set to BELOW_NORMAL (default) successfully Priority of worker thread set successfully setiathome enhanced x41zc, Cuda 4.20 Detected setiathome_enhanced_v7 task. Autocorrelations enabled, size 0k elements. Work Unit Info: ............... WU true angle range is : 0.545577 Kepler GPU current clockRate = 1123 MHz re-using dev_GaussFitResults array for dev_AutoCorrIn, 256 bytes re-using dev_GaussFitResults+32x8 array for dev_AutoCorrOut, 256 bytes Thread call stack limit is: 1k Error on launch (ac_reducePartial<<<grid3, block3,blksize*sizeof(float3)>>>( (float *)dev_AutoCorrIn, dev_ac_partials )), file c:/[Projects]/__Sources/sah_v7_opt/Xbranch/client/cuda/cudaAcc_autocorr.cu, line 200: invalid configuration argument Exiting cudaAcc_free() called... cudaAcc_free() running... cudaAcc_free() PulseFind freed... cudaAcc_free() Gaussfit freed... cudaAcc_free() AutoCorrelation freed... cudaAcc_free() DONE. Cuda sync'd & freed. Preemptively acknowledging a safe temporary exit-> Exit Status: 0 boinc_exit(): requesting safe worker shutdown -> boinc_exit(): received safe worker shutdown acknowledge -> Cuda threadsafe ExitProcess() initiated, rval 0 slot 9 setiathome_CUDA: Found 3 CUDA device(s): Device 1: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 5, pciSlotID = 0 Device 2: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 1, pciSlotID = 0 Device 3: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 2, pciSlotID = 0 In cudaAcc_initializeDevice(): Boinc passed DevPref 1 setiathome_CUDA: CUDA Device 1 specified, checking... Device 1: GeForce GTX 780 is okay SETI@home using CUDA accelerated device GeForce GTX 780 pulsefind: blocks per SM 4 (Fermi or newer default) pulsefind: periods per launch 100 (default) Priority of process set to BELOW_NORMAL (default) successfully Priority of worker thread set successfully setiathome enhanced x41zc, Cuda 4.20 Detected setiathome_enhanced_v7 task. Autocorrelations enabled, size 0k elements. Work Unit Info: ............... WU true angle range is : 0.545577 Kepler GPU current clockRate = 1071 MHz re-using dev_GaussFitResults array for dev_AutoCorrIn, 256 bytes re-using dev_GaussFitResults+32x8 array for dev_AutoCorrOut, 256 bytes Thread call stack limit is: 1k Error on launch (ac_reducePartial<<<grid3, block3,blksize*sizeof(float3)>>>( (float *)dev_AutoCorrIn, dev_ac_partials )), file c:/[Projects]/__Sources/sah_v7_opt/Xbranch/client/cuda/cudaAcc_autocorr.cu, line 200: invalid configuration argument Exiting cudaAcc_free() called... cudaAcc_free() running... cudaAcc_free() PulseFind freed... cudaAcc_free() Gaussfit freed... cudaAcc_free() AutoCorrelation freed... cudaAcc_free() DONE. Cuda sync'd & freed. Preemptively acknowledging a safe temporary exit-> Exit Status: 0 boinc_exit(): requesting safe worker shutdown -> boinc_exit(): received safe worker shutdown acknowledge -> Cuda threadsafe ExitProcess() initiated, rval 0 setiathome_CUDA: Found 3 CUDA device(s): Device 1: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 5, pciSlotID = 0 Device 2: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 1, pciSlotID = 0 Device 3: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 2, pciSlotID = 0 In cudaAcc_initializeDevice(): Boinc passed DevPref 1 setiathome_CUDA: CUDA Device 1 specified, checking... Device 1: GeForce GTX 780 is okay SETI@home using CUDA accelerated device GeForce GTX 780 pulsefind: blocks per SM 4 (Fermi or newer default) pulsefind: periods per launch 100 (default) Priority of process set to BELOW_NORMAL (default) successfully Priority of worker thread set successfully setiathome enhanced x41zc, Cuda 4.20 Detected setiathome_enhanced_v7 task. Autocorrelations enabled, size 0k elements. Work Unit Info: ............... WU true angle range is : 0.545577 Kepler GPU current clockRate = 1071 MHz re-using dev_GaussFitResults array for dev_AutoCorrIn, 256 bytes re-using dev_GaussFitResults+32x8 array for dev_AutoCorrOut, 256 bytes Thread call stack limit is: 1k Error on launch (ac_reducePartial<<<grid3, block3,blksize*sizeof(float3)>>>( (float *)dev_AutoCorrIn, dev_ac_partials )), file c:/[Projects]/__Sources/sah_v7_opt/Xbranch/client/cuda/cudaAcc_autocorr.cu, line 200: invalid configuration argument Exiting cudaAcc_free() called... cudaAcc_free() running... cudaAcc_free() PulseFind freed... cudaAcc_free() Gaussfit freed... cudaAcc_free() AutoCorrelation freed... cudaAcc_free() DONE. Cuda sync'd & freed. Preemptively acknowledging a safe temporary exit-> Exit Status: 0 boinc_exit(): requesting safe worker shutdown -> boinc_exit(): received safe worker shutdown acknowledge -> Cuda threadsafe ExitProcess() initiated, rval 0 setiathome_CUDA: Found 3 CUDA device(s): Device 1: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 5, pciSlotID = 0 Device 2: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 1, pciSlotID = 0 Device 3: GeForce GTX 780, 3072 MiB, regsPerBlock 65536 computeCap 3.5, multiProcs 12 pciBusID = 2, pciSlotID = 0 In cudaAcc_initializeDevice(): Boinc passed DevPref 1 setiathome_CUDA: CUDA Device 1 specified, checking... Device 1: GeForce GTX 780 is okay SETI@home using CUDA accelerated device GeForce GTX 780 pulsefind: blocks per SM 4 (Fermi or newer default) pulsefind: periods per launch 100 (default) Priority of process set to BELOW_NORMAL (default) successfully Priority of worker thread set successfully setiathome enhanced x41zc, Cuda 4.20 Detected setiathome_enhanced_v7 task. Autocorrelations enabled, size 0k elements. Work Unit Info: ............... WU true angle range is : 0.545577 Kepler GPU current clockRate = 1071 MHz re-using dev_GaussFitResults array for dev_AutoCorrIn, 256 bytes re-using dev_GaussFitResults+32x8 array for dev_AutoCorrOut, 256 bytes Thread call stack limit is: 1k Error on launch (ac_reducePartial<<<grid3, block3,blksize*sizeof(float3)>>>( (float *)dev_AutoCorrIn, dev_ac_partials )), file c:/[Projects]/__Sources/sah_v7_opt/Xbranch/client/cuda/cudaAcc_autocorr.cu, line 200: invalid configuration argument Exiting cudaAcc_free() called... cudaAcc_free() running... cudaAcc_free() PulseFind freed... cudaAcc_free() Gaussfit freed... cudaAcc_free() AutoCorrelation freed... cudaAcc_free() DONE. Cuda sync'd & freed. Preemptively acknowledging a safe temporary exit-> Exit Status: 0 boinc_exit(): requesting safe worker shutdown -> boinc_exit(): received safe worker shutdown acknowledge -> Cuda threadsafe ExitProcess() initiated, rval 0 I'm going to install the new version of BOINC, as Richard states it keeps a record for you all to look at. Right now both machines have 50 of these MB in a wait exit. I've not aborted them yet but not sure what to do with them |
Send message Joined: 29 May 06 Posts: 1037 Credit: 8,440,339 RAC: 0 ![]() |
http://setiathome.berkeley.edu/forum_thread.php?id=76350&postid=1617018 Edit.. I'm benching this Wu on my i5-3210M/GT650M/HD_Graphics_4000 host, just with the Stock 7.00 app, the AVX_2549 app, and the Intel_r2489 app, I expect it to take 6 to 7 hours. Claggy |
Send message Joined: 14 Oct 05 Posts: 1137 Credit: 1,848,733 RAC: 0 ![]() |
Hey Joe, I think just aborting them is sensible at this point. All attempts at processing them with CUDA app versions seem to get that same "...cudaAcc_autocorr.cu, line 200: invalid configuration argument" error which leads to 100 temporary exits, then BOINC kills the task for too many. OpenCL app versions seem to be processing at least some of them correctly, but not all. The stock CPU app versions seem to be the only ones which are really unaffected. There will probably be many resends, and quite likely many of these WUs will end up with too many error tasks. ================= I did get an email reply from Eric, possibly a recent cleanup in the pfb_splitter code introduced a bug. Joe |
Send message Joined: 3 Jan 07 Posts: 1451 Credit: 3,272,268 RAC: 0 ![]() |
I did get an email reply from Eric, possibly a recent cleanup in the pfb_splitter code introduced a bug.Joe My initial concern was the various straws in the wind we've had lately about Green Bank telescope data - staff working hard on GBT splitters, and the GPUUG buying new hardware for the recorder. If the changed parameters had been needed to match the GB telescope and recorder characteristics, then we might need to start work on an app refresh smartish. But 10fe09ab looks like a standard Arecibo tape from here, though at an unusual AR (0.545576...) |
Send message Joined: 29 May 06 Posts: 1037 Credit: 8,440,339 RAC: 0 ![]() |
My Bench completed quicker than expected, Stock 7.00 and AKv8c_r2549 are Strongly similar: ------------ The Intel r2489 app didn't run properly: ------------ Claggy |
![]() ![]() Send message Joined: 16 Jun 05 Posts: 2530 Credit: 1,074,556 RAC: 0 ![]() |
The server is sending out those units again. 10fe09ab.4848.25021.140733193388047 All created today. I get driver restarts so had to abort them. With each crime and every kindness we birth our future. |
![]() Send message Joined: 10 Feb 12 Posts: 107 Credit: 305,151 RAC: 0 ![]() |
Can someone please shoot me a PM over on main when this stops? Had to abort a few tasks too and set Beta to NNT. Thanx and Happy New Year!!:D |
Send message Joined: 30 Dec 13 Posts: 258 Credit: 12,340,341 RAC: 0 ![]() |
Yup they are still here. 150 of them today. None of them would start, Checked the stderr report, all had the same problems. Gave up and had to abort all of them, now the server won't sent anymore of them. Looks like going to have to be a daily event till they are all gone. |
![]() ![]() Send message Joined: 16 Jun 05 Posts: 2530 Credit: 1,074,556 RAC: 0 ![]() |
I`ve been told Jeff is working on a fix. With each crime and every kindness we birth our future. |
Send message Joined: 29 May 06 Posts: 1037 Credit: 8,440,339 RAC: 0 ![]() |
I`ve been told Jeff is working on a fix. It might have already been fixed and deployed, My PIII has a fresh task that has been completed and validated by my wingmen: http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=6799436 Can someone cancel all that broken work please. Claggy |
![]() Send message Joined: 6 Apr 11 Posts: 13 Credit: 205,673 RAC: 0 ![]() |
Had several of the 10fe09ab.*.vlar_8 task yesterday show up in my list. Looking at the list they were marked as Invalid for EVERYONE who crunched them. Wonder if they all have been sent out? ![]() ![]() |
Send message Joined: 14 Oct 05 Posts: 1137 Credit: 1,848,733 RAC: 0 ![]() |
Had several of the 10fe09ab.*.vlar_8 task yesterday show up in my list. No, recent splitter runs have also shown the problem. Tasks I've been sent which were split yesterday, such as WU 6806063 are examples. It seems maybe whenever a new splitter run starts, the first group of 256 WUs have a correct analysis_cfg section but subsequent groups have the bad parameters. Joe |
![]() Send message Joined: 15 Mar 05 Posts: 1547 Credit: 27,183,456 RAC: 0 ![]() |
Sorry, Jeff was supposed to have fixed those analysis configs last week. Either it never got applied or it didn't work. I'll try it again. Turns out it didn't work when he tried it. I fixed the problem, so newly generated results should be OK. I'll try to cancel existing results. ![]() |
Send message Joined: 3 Jan 07 Posts: 1451 Credit: 3,272,268 RAC: 0 ![]() |
Sorry, Jeff was supposed to have fixed those analysis configs last week. Either it never got applied or it didn't work. I'll try it again. It might be a good idea to check the Main project splitters too - I've just reported a couple of very strange WUs. WU 1669833986 WU 1669840794 I noticed an unusual deadline, and very short processing time. CUDA applications are processing in v6 mode, without autocorr processing. OpenCL doesn't report any autocorr signal count. Analysis_cfg: <analysis_cfg> <spike_thresh>24</spike_thresh> <spikes_per_spectrum>1</spikes_per_spectrum> <autocorr_thresh>0</autocorr_thresh> <autocorr_per_spectrum>0</autocorr_per_spectrum> <autocorr_fftlen>0</autocorr_fftlen> <gauss_null_chi_sq_thresh>2.47139668</gauss_null_chi_sq_thresh> <gauss_chi_sq_thresh>1.41999996</gauss_chi_sq_thresh> <gauss_power_thresh>3</gauss_power_thresh> <gauss_peak_power_thresh>3.20000005</gauss_peak_power_thresh> <gauss_pot_length>64</gauss_pot_length> <pulse_thresh>24.1975803</pulse_thresh> <pulse_display_thresh>0.5</pulse_display_thresh> <pulse_max>40960</pulse_max> <pulse_min>16</pulse_min> <pulse_fft_max>8192</pulse_fft_max> <pulse_pot_length>256</pulse_pot_length> <triplet_thresh>13.1977901</triplet_thresh> <triplet_max>131072</triplet_max> <triplet_min>16</triplet_min> <triplet_pot_length>256</triplet_pot_length> <pot_overlap_factor>0.5</pot_overlap_factor> <pot_t_offset>1</pot_t_offset> <pot_min_slew>0.00209999993</pot_min_slew> <pot_max_slew>0.0104999999</pot_max_slew> <chirp_resolution>0.333</chirp_resolution> <analysis_fft_lengths>262136</analysis_fft_lengths> <bsmooth_boxcar_length>8192</bsmooth_boxcar_length> <bsmooth_chunk_size>32768</bsmooth_chunk_size> <chirps> <chirp_parameter_t> <chirp_limit>20</chirp_limit> <fft_len_flags>262136</fft_len_flags> </chirp_parameter_t> <chirp_parameter_t> <chirp_limit>50</chirp_limit> <fft_len_flags>65528</fft_len_flags> </chirp_parameter_t> </chirps> <pulse_beams>1</pulse_beams> <max_signals>30</max_signals> <max_spikes>8</max_spikes> <max_autocorr>0</max_autocorr> <max_gaussians>0</max_gaussians> <max_pulses>0</max_pulses> <max_triplets>0</max_triplets> <keyuniq>-5170219</keyuniq> <credit_rate>2.8499999</credit_rate> </analysis_cfg> |
Send message Joined: 14 Oct 05 Posts: 1137 Credit: 1,848,733 RAC: 0 ![]() |
LoL, that's delightfuly retro! Chirp limits which date back before setiathome_enhanced, etc. The reason the results are being marked invalid is because the SaH v7 validator insists that a v7 result which did not overflow must have a best_autocorr signal. That feature was implemented to keep anonymous platform users from processing v7 tasks with v6 applications. If there were a good reason to run tasks without autocorrelation, it might make sense to remove that validator feature. The protection is probably no longer needed. Joe |
Send message Joined: 3 Jan 07 Posts: 1451 Credit: 3,272,268 RAC: 0 ![]() |
The original reports - see Strange, utterly strange MB v7 run as MB v6 with MB v7 app.... all seemed to come from a single tape/channel: 19ap11ad.19368.xxxxx.140733193388035.12.xxx but today more channels (still from the same tape) are reaching the front of the queue. 19ap11ad.18067.xxxxx.140733193388039.12.xxx 19ap11ad.22063.xxxxx.140733193388041.12.xxx 19ap11ad.23016.xxxxx.140733193388045.12.xxx 19ap11ad.23606.xxxxx.140733193388046.12.xxx 19ap11ad.24546.xxxxx.140733193388042.12.xxx 19ap11ad.25864.xxxxx.140733193388043.12.xxx Not all have been processed and returned, but many (not all) have the same oddly short deadlines - just slightly over the current 'shorty' timespan. I've also had a couple of overflows validate, as we might expect from the known validator checks. |
Send message Joined: 29 May 06 Posts: 1037 Credit: 8,440,339 RAC: 0 ![]() |
Eric, Any progress in getting the splitters fixed for this issue? Still getting freshly split work that errors on the GPU apps, and goes inconclusive, then invalid on the CPU apps: http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=6887134 http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=6887134 although some Wu's are O.K: http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=6887091 Claggy |
Send message Joined: 14 Oct 05 Posts: 1137 Credit: 1,848,733 RAC: 0 ![]() |
I checked recent splitter runs to see how many were bad. Group AR keyuniq autocorr triplet_thresh 27my12ac.28863.2120 0.0127258 -117761 bad 10.97682 27my12ac.11211.2529 0.0115601 -1325057 good 9.73841 27my12ac.11211.2938 0.0109193 -1328129 good 10.97682 27my12ac.11211.3347 0.0134823 -1747969 good 12.21523 27my12ac.11211.3756 0.0124419 -1758209 good 13.45364 27my12ac.11211.4165 0.0109803 -1925121 good 14.692049928753 27my12ac.11211.4574 0.0101923 -1 bad 9.73841 27my12ac.5321.4983 0.0133141 -1325057 good 9.73841 27my12ac.5321.5392 0.0143072 -1328129 good 10.97682 27my12ac.5321.5801 0.0139497 -1747969 good 12.21523 27my12ac.5321.6619 0.0143122 -1925121 good 14.69205 27my12ac.5321.7028 0.0142447 -1926145 good 15.930459928753 27my12ac.4033.7437 0.0125166 -1325057 good 9.73841 27my12ac.4033.7846 0.0110970 -1328129 good 10.97682 27my12ac.4033.8255 0.0132942 -1747969 good 12.21523 27my12ac.4033.8664 0.0157456 -1758210 good 13.453639928753 27my12ac.4033.9073 0.1029475 -10 bad 13.3834276 27my12ac.2218.9482 0.0143417 -1325057 good 9.73841 27my12ac.2218.9891 0.0150630 -1328130 good 10.976819928753 27my12ac.2218.10300 0.0128078 -1 bad 9.73841 27my12ac.2218.10709 0.0109577 -117761 bad 10.97682 27my12ac.2218.11118 0.0129995 -118785 bad 12.21523 Looks like something approaching 1/3 have the bad autocorr parameters. But they're all VLAR WUS, and if we include those with triplet_thresh differing from the expected 9.73841, only 4 of those 22 groups had proper analysis_cfg. At main, all recent SaH v7 WUs I've checked have had keyuniq values between -9417729 and -9418728. They're all magnitude 9197*1024 + 100*AR. Joe |
Send message Joined: 3 Jun 12 Posts: 64 Credit: 2,532,468 RAC: 0 ![]() |
Some of these units are still floating around. I just aborted 7 of them (fortunately most of them were cancelled because they had been sent out too many times, but some of them are still out there). Its the first 7 tasks from this list: http://setiweb.ssl.berkeley.edu/beta/results.php?userid=17981&offset=0&show_names=0&state=6&appid= Tom |
©2023 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.