Posts by Adam Alexander

1) Message boards : Number crunching : Astropulse Errors-Optimized version 5 (Message 843646)
Posted 22 Dec 2008 by Profile Adam Alexander
Post:
I've got an AP 5.0 wu running that has time to completion as 450 hours on a Core 2 Quad Q6700. Is that normal? I've never noticed a SETI work unit that took that long to crunch.

No, it's because you've been running CUDA setiathome_enhanced work and the Duration Correction Factor is high. Crunch time wlll probably be a tenth or less of that estimate. Astropulse does take considerably longer than setiathome_enhanced though, even on hosts running both with CPU. 
                                                              Joe


Thanks. I noticed after I posted that just under 4 hours in the WU is 12% complete so I thought there must be something like that going on,


The work unit finished with a compute error. Here's the message:

<core_client_version>6.4.5</core_client_version>
<![CDATA[
<message>
- exit code -202 (0xffffff36)
</message>
<stderr_txt>
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 896
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1024
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1152
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1280
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1408
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1536
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1664
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1792
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 1920
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2048
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2048
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2176
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2304
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2432
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2432
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2560
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2560
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2688
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2688
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2816
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2944
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 2944
In ap_client_main.cpp: in mainloop(): at dm_chunk_large 3072
No heartbeat from core client for 30 sec - exiting
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
boinc_graphics_make_shmem failed: 0

</stderr_txt>
]]>

What happened and how do I stop it from happening again? This WU took up 21871.03 of processor time, I'd rather this didn't happen again.
2) Message boards : Number crunching : Astropulse Errors-Optimized version 5 (Message 843402)
Posted 22 Dec 2008 by Profile Adam Alexander
Post:
I've got an AP 5.0 wu running that has time to completion as 450 hours on a Core 2 Quad Q6700. Is that normal? I've never noticed a SETI work unit that took that long to crunch.

No, it's because you've been running CUDA setiathome_enhanced work and the Duration Correction Factor is high. Crunch time wlll probably be a tenth or less of that estimate. Astropulse does take considerably longer than setiathome_enhanced though, even on hosts running both with CPU. 
                                                              Joe


Thanks. I noticed after I posted that just under 4 hours in the WU is 12% complete so I thought there must be something like that going on,
3) Message boards : Number crunching : Astropulse Errors-Optimized version 5 (Message 843325)
Posted 22 Dec 2008 by Profile Adam Alexander
Post:
This thread is to post errors and address concerns regarding the new Optimised AP v5.00 Astropulse application.

Please do not open new threads but post errors and commentary here.

Please, upgrade your optimized AP version to ap_5.00r69 !

Thanks!


I've got an AP 5.0 wu running that has time to completion as 450 hours on a Core 2 Quad Q6700. Is that normal? I've never noticed a SETI work unit that took that long to crunch.





 
©2024 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.