HI-

I went to my Seti preference Web Page, and changed the options there as you suggested. I exited Boinc & restarted it again. I aborted the APv5 8 meg file/208 hours to complete, and I am still downloading the huge unwanted AP v5 files.

Any suggestions?

Thanks.

---

WE Are Not Alone!

All I can say is recheck the page. you have to unclick astropulse v5 and "run other applications" If you don't unclick the "other applications..." you'll continue to get astropulse

---

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

Got a bunch of errors on this host.
AK SSE2 works well but the latest AP SSE2 obviously doesn't.

PS: don't wait for the "in progess" Wu - that one got lost somewhere...

---

mic.

Got a bunch of errors on this host.
AK SSE2 works well but the latest AP SSE2 obviously doesn't.

PS: don't wait for the "in progess" Wu - that one got lost somewhere...

There isn't an SSE2 AP application, only SSE and SSE3, and your errors are:

FFTW USE_CONVERSION_OPT USE_SSE2->SSE3_EMU
SIGILL: illegal instruction

So use the Optimised SSE AP app instead.

Claggy

Got a bunch of errors on this host.
AK SSE2 works well but the latest AP SSE2 obviously doesn't.

PS: don't wait for the "in progess" Wu - that one got lost somewhere...

There isn't an SSE2 AP application, only SSE and SSE3, and your errors are:

FFTW USE_CONVERSION_OPT USE_SSE2->SSE3_EMU
SIGILL: illegal instruction

So use the Optimised SSE AP app instead.

Claggy

Hmmm... This post suggests there is one.
The link is dead now, but I'm quite sure I got it there...

Well, I'll try the SSE version.

---

mic.

Have you looked at your app_info file

If you used the one that came with the download, you will only get 5.03 wu's. You need to merge it with your existing app_info file so that you continue to get MB units as well as astropulse.
There are plenty of people more qualified than me who can help you with that..

It's not about app_info. It is about the fact that when I tick the option to receive AP 5.03, I am receiving ONLY those units on ALL my computers. When I tick that option off I am receiving MB and occasionally AP 5.0 WU.
It is about the way the servers assign WU's - there are "biased" towards sending AP 5.03.

Got a bunch of errors on this host.
AK SSE2 works well but the latest AP SSE2 obviously doesn't.

PS: don't wait for the "in progess" Wu - that one got lost somewhere...

There isn't an SSE2 AP application, only SSE and SSE3, and your errors are:

FFTW USE_CONVERSION_OPT USE_SSE2->SSE3_EMU
SIGILL: illegal instruction

So use the Optimised SSE AP app instead.

Claggy

Hmmm... This post suggests there is one.
The link is dead now, but I'm quite sure I got it there...

Well, I'll try the SSE version.

You know, you're right, there is an 32bit SSE2 AP version, for Linux only,
don't know whether you got the SSE3 version, or if the SSE2 version tried to use SSE3.

Claggy

My first statefile is 0'd 100 times reset for opti 5.03, at about 61%.

Task 1186821065
Just curious and I'm sure it's been answered before. So why again is it when it does the repeated 61%, it does it faster than the first time?

---

The naming of the new AP application is not very smart.

Message from server: Your app_info.xml file doesn't have a version of Astropulse v5.

well, I had AP version 5.00 and have been trying to figure out what's wrong with my app_info ...

but then I found it here in the board ... AP version 5.00 is not a AP v5

~:-/

I started getting SETI units on both my crunching computers today. Didn't update BOINC or change anything really.

---

The naming of the new AP application is not very smart.

Message from server: Your app_info.xml file doesn't have a version of Astropulse v5.

well, I had AP version 5.00 and have been trying to figure out what's wrong with my app_info ...

but then I found it here in the board ... AP version 5.00 is not a AP v5

~:-/

They had to do this to avoid validation issues. This mistake was made when there was a change to AP v4, the newer apps and older apps weren't validating together, causing lots of resends.

The only way around that problem was to publish AP v5.03 as a new application so that they would not attempt to validate with AP v5.00 apps.

---

The naming of the new AP application is not very smart.

Message from server: Your app_info.xml file doesn't have a version of Astropulse v5.

well, I had AP version 5.00 and have been trying to figure out what's wrong with my app_info ...

but then I found it here in the board ... AP version 5.00 is not a AP v5

~:-/

They had to do this to avoid validation issues. This mistake was made when there was a change to AP v4, the newer apps and older apps weren't validating together, causing lots of resends.

The only way around that problem was to publish AP v5.03 as a new application so that they would not attempt to validate with AP v5.00 apps.

But they didn't have to call it Astropulse v5, which I agree was a poor choice and certain to cause confusion. Water under the bridge, perhaps the next one will be clearer. There have already been enough changes to require another new name, though they haven't provided one for the 5.04 being tested at SETI Beta.

                                                             Joe

The naming of the new AP application is not very smart.

Message from server: Your app_info.xml file doesn't have a version of Astropulse v5.

well, I had AP version 5.00 and have been trying to figure out what's wrong with my app_info ...

but then I found it here in the board ... AP version 5.00 is not a AP v5

~:-/

They had to do this to avoid validation issues. This mistake was made when there was a change to AP v4, the newer apps and older apps weren't validating together, causing lots of resends.

The only way around that problem was to publish AP v5.03 as a new application so that they would not attempt to validate with AP v5.00 apps.

But they didn't have to call it Astropulse v5, which I agree was a poor choice and certain to cause confusion. Water under the bridge, perhaps the next one will be clearer. There have already been enough changes to require another new name, though they haven't provided one for the 5.04 being tested at SETI Beta.

                                                             Joe

I agree that it was certain to cause confusion, but how was it a poor choice? If they didn't have to call it AP v5, what else could they have done? If there was a better choice, why did they choose publishing it as a new application over a better option?

---

... If they didn't have to call it AP v5, what else could they have done? ...

A message like

Message from server: Your app_info.xml file doesn't have a version of Astropulse II.

would have led me to the solution much faster :-)

Anyway, it's crunching a few of those now, no trouble so far.

... If they didn't have to call it AP v5, what else could they have done? ...

A message like

Message from server: Your app_info.xml file doesn't have a version of Astropulse II.

would have led me to the solution much faster :-)

Anyway, it's crunching a few of those now, no trouble so far.

That naming would have been less confusing, but it still would have to be published as a new app (AstroPulse II, v5.03) so the end effect is the same.

---

... If they didn't have to call it AP v5, what else could they have done? ...

A message like

Message from server: Your app_info.xml file doesn't have a version of Astropulse II.

would have led me to the solution much faster :-)

Anyway, it's crunching a few of those now, no trouble so far.

That naming would have been less confusing, but it still would have to be published as a new app (AstroPulse II, v5.03) so the end effect is the same.

I think everyone accepts that the installation as a new application was a good idea (and should have been done for the previous transition in November, too): it's only the confusing name which people are questioning.

... If they didn't have to call it AP v5, what else could they have done? ...

A message like

Message from server: Your app_info.xml file doesn't have a version of Astropulse II.

would have led me to the solution much faster :-)

Anyway, it's crunching a few of those now, no trouble so far.

That naming would have been less confusing, but it still would have to be published as a new app (AstroPulse II, v5.03) so the end effect is the same.

I think everyone accepts that the installation as a new application was a good idea (and should have been done for the previous transition in November, too): it's only the confusing name which people are questioning.

Ah, ok. I was getting the impression that there were more objections than that.

---

Just found this WU in my list.
As you can imagine I'm the one getting nothin'.
Up to now this is the first invalid on all my rigs...

---

mic.

Just found this WU in my list.
As you can imagine I'm the one getting nothin'.
Up to now this is the first invalid on all my rigs...

bad sign indeed.
Maybe it's worth to start saving AP workunits on HDD at least until it pass validation.
W/o original WU we can't do anything cause stock even doesn't report how many pulses it found...

Just found this WU in my list.
As you can imagine I'm the one getting nothin'.
Up to now this is the first invalid on all my rigs...

bad sign indeed.
Maybe it's worth to start saving AP workunits on HDD at least until it pass validation.
W/o original WU we can't do anything cause stock even doesn't report how many pulses it found...

But if you feel like digging, it hasn't been purged yet, so you can still go to fanout and find the WU before it is deleted.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)