also with Math enhancements for the specific SSE the highest is something like SSE4...

---

Does anyone have a working x86_64 linux astropulse client? The one SETI@home sends out is useless as it constantly segfaults everytime boinc switches applications. I had a similar issue with Folding@homes client and the solution was to start nscd because they had compiled against some old glibc. I assume this is the same problem with the released x86_64 astropulse client. My system is running Gentoo ~amd64 branch and is 100% upto date. Memtest86 has run for 48 hours with no issues and I have no issues with other BOINC projects.

take a look here. you'll need to scroll down a bit to find it. it has both the MB and AP apps. You may need to create your own app_info though. Its been a while since I've installed mine so forgive me for not remembering all that well

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope

take a look here. you'll need to scroll down a bit to find it. it has both the MB and AP apps. You may need to create your own app_info though. Its been a while since I've installed mine so forgive me for not remembering all that well

I have app_info's included.

---

I'm interested in this thread too. Seti@Home has downloaded a 64 bit Linux AstroPulse app version astropulse_5.06_x86_64-pc-linux-gnu and it always errors out when reported. Is there any news about an official app that works or at least have a configuration that allows AstroPulse work to be done in other platforms that do work correctly and not try to do AP work in the 64bit Linux distro?

Also, the same goes for the official SetiEnhanced apps for 64 bit Linux distros, setiathome-5.28.x86_64-pc-linux-gnu. I see another app in the client file, setiathome_6.03_i686-pc-linux-gnu. What determines which client app gets used? I'm guessing that the last one mentioned is a 32bit app and it seems to produce valid results. Should I edit the app_info XML file to remove the Linux 64 bit apps since they produce only invalid results? What is the best way to remedy the problems? I want to produce valid science results only. I have built a new system using modern hardware and it is not overclocked or anything. My older first Seti@Home system with ancient hardware still produces good results, just MUCH, MUCH slower.

Any help or suggestion, comments??

Cheers, Keith

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

I have released a Astropulse 5.06 binary for FreeBSD 7.x/8.x on AMD64/x64 and also for FreeBSD i386 7.x/8.x on i386.

I have released a Astropulse 5.06 binary for Solaris/OpenSolaris x86 on i386/x64/AMD64.

I'm interested in this thread too. Seti@Home has downloaded a 64 bit Linux AstroPulse app version astropulse_5.06_x86_64-pc-linux-gnu and it always errors out when reported. Is there any news about an official app that works or at least have a configuration that allows AstroPulse work to be done in other platforms that do work correctly and not try to do AP work in the 64bit Linux distro?

Also, the same goes for the official SetiEnhanced apps for 64 bit Linux distros, setiathome-5.28.x86_64-pc-linux-gnu. I see another app in the client file, setiathome_6.03_i686-pc-linux-gnu. What determines which client app gets used? I'm guessing that the last one mentioned is a 32bit app and it seems to produce valid results. Should I edit the app_info XML file to remove the Linux 64 bit apps since they produce only invalid results? What is the best way to remedy the problems? I want to produce valid science results only. I have built a new system using modern hardware and it is not overclocked or anything. My older first Seti@Home system with ancient hardware still produces good results, just MUCH, MUCH slower.

Any help or suggestion, comments??

Cheers, Keith

I'm running Ubuntu 32 bit (10:10) on a Phenom x4 965 with a GT8800 GPU.
Every single Astropulse has returned a compute error so it's nothing to do whether it's 64 or 32 bit.

Astropulse error report

Just updated to Ubuntu 11.10 x86_64 and AstroPulse still fails.

task 2124047908 wu 842329755 for example. I turned AP off
once I saw the 4 failures (none of the 4 AP wu-s tried worked).

I downloaded and installed the Astropulse binary on my Solaris Virtual Machine, which was crunching a vlar SETI task. But I lost it when restarting the boinc client since there are minor differences in the name of the SETI executable contained in the app_info.xml by Dotsch and the executable in the setiathome.berkeley.edu folder. I then corrected the app_info.xml file, and restarted the boinc client. To my surprise, the vlar task was resent to me in a few hours and I am recrunching it. No astropulse task so far.
Tullio

---

Got one Astropulse task. It is running on my Solaris Virtual Machine. The vlar result has been uploaded. After a while the running task will report it. I have no BOINC manager, only a BOINC client by Dotsch.
Tullio

---

I don't know if this is the right place, but Astropulse has been doing this for awhile. I tried emailing someone on the project... well, a long time ago, but never heard back. Basically, when Astropulse workunits are processed, I see the following in my logs:

Wed 29 Feb 2012 07:16:39 AM MST | SETI@home | Starting task ap_03jn11ab_B1_P1_00028_20120222_27740.wu_0 using astropulse_v505 version 506 in slot 2
Wed 29 Feb 2012 07:16:41 AM MST | SETI@home | Computation for task ap_03jn11ab_B1_P1_00028_20120222_27740.wu_0 finished
Wed 29 Feb 2012 07:16:41 AM MST | SETI@home | Output file ap_03jn11ab_B1_P1_00028_20120222_27740.wu_0_0 for task ap_03jn11ab_B1_P1_00028_20120222_27740.wu_0 absent

If one looks at the time stamp of the above log, notice the workunit only took 2 seconds to finish? I don't have this problem with Seti@Home, just Astropulse. It has been doing this for about three versions of the boinc client now. Actually, I think it started when I got my new laptop (where I run BOINC from). Maybe a hardware compatibility issue??? I just tried deleting and redownloading the AP binary to see if maybe it was having a problem. I'm currently running with these hardware/software specs, in case that doesn't fix the problem:

OS: Linux: 3.2.0-1-amd64 (Debian Testing)
BOINC client version 7.0.15 for x86_64-pc-linux-gnu
Memory: 7.74 GB physical, 0 bytes virtual
Disk: 78.00 GB total, 59.14 GB free
Processor: 8 GenuineIntel Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz [Family 6 Model 42 Stepping 7]
NVIDIA GPU 0: GeForce GT 550M (driver version unknown, CUDA version 4.20, compute capability 2.1, 1024MB, 997MB available, 274 GFLOPS peak)
log flags: file_xfer, sched_ops, task
Libraries: libcurl/7.24.0 OpenSSL/1.0.0g zlib/1.2.6 libidn/1.23 libssh2/1.2.8 librtmp/2.3
Data directory: /var/lib/boinc-client

I'm including my computer ID so folks can look at my workunit history to see how long this has been going on:

Computer ID 6112139

Basically, I'm wondering what is wrong and what do I do to fix it? I rather enjoyed crunching AP workunits...

Thanks for any info that helps!

---

See this post for the the relevant bits
http://setiathome.berkeley.edu/forum_thread.php?id=66433&nowrap=true#1179807
and this post for a better work around if you want faster processing.
http://setiathome.berkeley.edu/forum_thread.php?id=66433&nowrap=true#1179722

Now if you want to go optimized you will need this package
http://www.arkayn.us/forum/index.php?action=downloads;sa=view;down=12
and this one.
http://www.arkayn.us/forum/index.php?action=downloads;sa=view;down=45

That will also allow you to use the GT 550M if you want to as well.

Be advised that as you have a laptop, GPU crunching can make the machine extra hot.

The combined app_info needed to keep all current WU is below.

<app_info>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_V8_linux64_ssse3</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>528</version_num>
<file_ref>
<file_name>AK_V8_linux64_ssse3</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<file_ref>
<file_name>AK_V8_linux64_ssse3</file_name>
<main_program/>
</file_ref>
</app_version>
	<file_info>
		<name>setiathome_x41g_x86_64-pc-linux-gnu_cuda32</name>
		<executable/>
	</file_info>
	<file_info>
		<name>libcudart.so.3</name>
		<executable/>
	</file_info>
	<file_info>
		<name>libcufft.so.3</name>
		<executable/>
	</file_info>
	<app_version>
		<app_name>setiathome_enhanced</app_name>
		<version_num>611</version_num>
		<platform>x86_64-pc-linux-gnu</platform>
		<plan_class>cuda_fermi</plan_class>
		<avg_ncpus>0.05</avg_ncpus>
		<max_ncpus>1.0</max_ncpus>
		<coproc>
			<type>CUDA</type>
			<count>1.0</count>
		</coproc>
		<file_ref>
			<file_name>setiathome_x41g_x86_64-pc-linux-gnu_cuda32</file_name>
			<main_program/>
		</file_ref>
		<file_ref>
			<file_name>libcudart.so.3</file_name>
		</file_ref>
		<file_ref>
			<file_name>libcufft.so.3</file_name>
		</file_ref>
	</app_version>

	<app_version>
		<app_name>setiathome_enhanced</app_name>
		<version_num>609</version_num>
		<platform>x86_64-pc-linux-gnu</platform>
		<plan_class>cuda_fermi</plan_class>
		<avg_ncpus>0.05</avg_ncpus>
		<max_ncpus>1.0</max_ncpus>
		<coproc>
			<type>CUDA</type>
			<count>1.0</count>
		</coproc>
		<file_ref>
			<file_name>setiathome_x41g_x86_64-pc-linux-gnu_cuda32</file_name>
			<main_program/>
		</file_ref>
		<file_ref>
			<file_name>libcudart.so.3</file_name>
		</file_ref>
		<file_ref>
			<file_name>libcufft.so.3</file_name>
		</file_ref>
	</app_version>

	<app_version>
		<app_name>setiathome_enhanced</app_name>
		<version_num>608</version_num>
		<platform>x86_64-pc-linux-gnu</platform>
		<plan_class>cuda_fermi</plan_class>
		<avg_ncpus>0.05</avg_ncpus>
		<max_ncpus>1.0</max_ncpus>
		<coproc>
			<type>CUDA</type>
			<count>1.0</count>
		</coproc>
		<file_ref>
			<file_name>setiathome_x41g_x86_64-pc-linux-gnu_cuda32</file_name>
			<main_program/>
		</file_ref>
		<file_ref>
			<file_name>libcudart.so.3</file_name>
		</file_ref>
		<file_ref>
			<file_name>libcufft.so.3</file_name>
		</file_ref>
	</app_version>
    <app>
        <name>astropulse_v505</name>
    </app>
    <file_info>
        <name>ap_5.06r411_sse3_linux64</name>
        <executable/>
    </file_info>
    <app_version>
        <app_name>astropulse_v505</app_name>
        <version_num>506</version_num>
        <file_ref>
            <file_name>ap_5.06r411_sse3_linux64</file_name>
            <main_program/>
        </file_ref>
    </app_version>
</app_info>

---

Astropulse by Dotsch is running on my Solaris Virtual machine. Here is an excerpt from the stderr.txt file:
In ap_gfx_main.cpp: in ap_graphics_init(): Starting client.
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_client_main.cpp: in mainloop(): at dm_chunk_large 3072
Tullio

---

Solaris 10 x86