I thought that for v7 the stock app was going to be the same as the optimised app? If so why do we need a separate installer for optimised app? Is it not possible for current optimised app users like myself to uninstall it, revert to stock and then let that update automatically?

The stock apps for NVidia GPUs will indeed be identical to the installer-supplied apps after the v7 launch.

For AMD(ATI) GPUs, it is - provisionally - possible that the installer will supply a bug-fix version of the stock app designed to avoid the (rare) problem of AP tasks continuing to run when they are supposed to be suspended. That depends on two (independent) decisions - by Eric, and by the installer team - which will be made next week: has the bugfix version been tested enough, and does it cure the problem it's designed to address?

For CPU work, the installer will contain optimised apps for both AP and MB v7: anyone using their CPU for SETI alongside one or more GPUs, and wishing to retain the benefit of optimisation, will need to stay on the anonymous platform path: that will be the main motivator for using the installer in future.

Will the v7 stock app handle GPU as well as CPU processing and will it let me run multiple WU at the same time on my GPU?

Provided you use a version of BOINC later than v7.0.40 - preferably the recommended v7.0.64 - you can run multiple GPU tasks via an app_config.xml file, yes. It's much simpler than going down the whole anonymous platform route.

Looks like the kittyman shall just have to let the chips fall and see what shakes out.

I am way too tired, nasty, and P'd off to do much more these days.

Oh, for reference about tnp......

I'll pass on that for now. Most of you folks don't get my humor anyway.

Meowgrumblemumble.

---

"Time is simply the mechanism that keeps everything from happening all at once."

OK, now I'm a bit confused...

jason_gee wrote:

CPU multibeam received Joe Segur's AVX along with adaptations of Alex Kan's pulsefinding etc. I understand Lunatics already have some customised CPU builds, for example, which may be better suited for third party distribution, rather than stock which has a slower update cycle by necessity.

Richard Haselgrove wrote:

For CPU work, the installer will contain optimised apps for both AP and MB v7: anyone using their CPU for SETI alongside one or more GPUs, and wishing to retain the benefit of optimisation, will need to stay on the anonymous platform path: that will be the main motivator for using the installer in future.

So for someone like me, who is using only CPUs for SETI and currently running both optimized AP & MB, do I need to stay with optimized applications or can I just switch to stock apps now since they apparently have all the optimizations included?

---

So for someone like me, who is using only CPUs for SETI and currently running both optimized AP & MB, do I need to stay with optimized applications or can I just switch to stock apps now since they apparently have all the optimizations included?

Up to you, but the new stock CPU apps don't have all the optimisations. The discussion about stock and third-party applications being the same only applies to GPU apps.

One thing is certain - you'll have to do something if you want to continue crunching SETI MB. The servers won't send v7 work to a host currently optimised with the previous cycle of apps: you would be reduced to AP only, plus an ever-diminishing supply of MB v6 resends.

From Jason's post, note that AVX has a very high minimum system requirement - a second generation Intel Core i5 or Core i7 manufactured no earlier than 2011, or an AMD Bulldozer of the same vintage. Plus, in addition, Windows 7 Service Pack 1.

So for someone like me, who is using only CPUs for SETI and currently running both optimized AP & MB, do I need to stay with optimized applications or can I just switch to stock apps now since they apparently have all the optimizations included?

Up to you, but the new stock CPU apps don't have all the optimisations. The discussion about stock and third-party applications being the same only applies to GPU apps.

OK,thanks. Than I'll stay with optimized apps, let's hope there will be enough AP and MBv6 resends untill the release of the new opt apps (my CPUs are slow, so with a bit of luck it might be enough for them).

---

So for someone like me, who is using only CPUs for SETI and currently running both optimized AP & MB, do I need to stay with optimized applications or can I just switch to stock apps now since they apparently have all the optimizations included?

Up to you, but the new stock CPU apps don't have all the optimisations. The discussion about stock and third-party applications being the same only applies to GPU apps.

One thing is certain - you'll have to do something if you want to continue crunching SETI MB. The servers won't send v7 work to a host currently optimised with the previous cycle of apps: you would be reduced to AP only, plus an ever-diminishing supply of MB v6 resends.

From Jason's post, note that AVX has a very high minimum system requirement - a second generation Intel Core i5 or Core i7 manufactured no earlier than 2011, or an AMD Bulldozer of the same vintage. Plus, in addition, Windows 7 Service Pack 1.

I truly hope the vintage of the user is not a factor....LOL.

---

"Time is simply the mechanism that keeps everything from happening all at once."

I truly hope the vintage of the user is not a factor....LOL.

Well if you think you're too young, you can always step aside and let an olde man take a whack at it -- youngster!! lol

---

I don't buy computers, I build them!!

I truly hope the vintage of the user is not a factor....LOL.

Well if you think you're too young, you can always step aside and let an olde man take a whack at it -- youngster!! lol

LOL...
I wuz erring in the other direction, kid.

---

"Time is simply the mechanism that keeps everything from happening all at once."

I truly hope the vintage of the user is not a factor....LOL.

Well if you think you're too young, you can always step aside and let an olde man take a whack at it -- youngster!! lol

LOL...
I wuz erring in the other direction, kid.

Last time I checked I was closer to 70 than 60.

---

I don't buy computers, I build them!!

I thought that for v7 the stock app was going to be the same as the optimised app? If so why do we need a separate installer for optimised app? Is it not possible for current optimised app users like myself to uninstall it, revert to stock and then let that update automatically?

The stock apps for NVidia GPUs will indeed be identical to the installer-supplied apps after the v7 launch.

For AMD(ATI) GPUs, it is - provisionally - possible that the installer will supply a bug-fix version of the stock app designed to avoid the (rare) problem of AP tasks continuing to run when they are supposed to be suspended. That depends on two (independent) decisions - by Eric, and by the installer team - which will be made next week: has the bugfix version been tested enough, and does it cure the problem it's designed to address?

For CPU work, the installer will contain optimised apps for both AP and MB v7: anyone using their CPU for SETI alongside one or more GPUs, and wishing to retain the benefit of optimisation, will need to stay on the anonymous platform path: that will be the main motivator for using the installer in future.

Will the v7 stock app handle GPU as well as CPU processing and will it let me run multiple WU at the same time on my GPU?

Provided you use a version of BOINC later than v7.0.40 - preferably the recommended v7.0.64 - you can run multiple GPU tasks via an app_config.xml file, yes. It's much simpler than going down the whole anonymous platform route.

OK so I have 4 PCs running just about each combination of CPU and Nividea GPU processing.

My main rig crunches seti on a GTX460 currently using BOINC 6 to avoid long back offs. Sounds like my best option is to upgrade BOINC to 7.0.64 then revert it to stock SETI app. Do I need to worry about tasks being abandoned during the BOINC upgrade? What is involved in reverting to stock? Do I just reinstall the stock app or do I need to remove the lunatics files? Again will I risk loosing tasks during this? Once the stock app is released then edit the app_config file to run 2 WU at a time?

My other 2 work based machines are both CPU only crunchers, so leave them on annonymous app and hope they have enough v6 and ap work to keep them going till I get back?

My home PC crunches seti on both CPU and Nividea GPU. Sounds like I have no choice but to leave it until I get back. The GPU will run out of work and will have to process Einstein, but the CPU may survive on v6 and AP.

---

I truly hope the vintage of the user is not a factor....LOL.

Well if you think you're too young, you can always step aside and let an olde man take a whack at it -- youngster!! lol

LOL...
I wuz erring in the other direction, kid.

Last time I checked I was closer to 70 than 60.

Then I defer to the elder gentleman from Pokipski.

---

"Time is simply the mechanism that keeps everything from happening all at once."

The APv6 r555 & r557 CPU apps of LIv0.4 will be replaced through new apps in/of LIv0.41?

Thanks.


* Best regards! :-) * Philip J. Fry, team seti.international founder. * Optimize your PC for higher RAC. * SETI@home needs your help. *

---

The APv6 r555 & r557 CPU apps of LIv0.4 will be replaced through new apps in/of LIv0.41?

Thanks.

Wait and see ;-)

From Jason's post, note that AVX has a very high minimum system requirement - a second generation Intel Core i5 or Core i7 manufactured no earlier than 2011, or an AMD Bulldozer of the same vintage. Plus, in addition, Windows 7 Service Pack 1.

The second generation i3 also has AVX.

---

<Snip>

From Jason's post, note that AVX has a very high minimum system requirement - a second generation Intel Core i5 or Core i7 manufactured no earlier than 2011, or an AMD Bulldozer of the same vintage. Plus, in addition, Windows 7 Service Pack 1.

So older cpus that don't have AVX aren't going to be able to crunch
V7 MB work units?

No Jason's post does NOT say that without AVX you won't be able to crunch v7. It says support for AVX will be built in.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

No Jason's post does NOT say that without AVX you won't be able to crunch v7. It says support for AVX will be built in.

So is that a 'YES', older processors will be able to
crunch V7 MB work units, or 'NO' they won't be able to
crunch V7 MB work units?

I would dearly love to see more unambiguous answers in this forum.
A lot of misinterpretation of answers occurs here, IMO,
for many reasons. Non-English speaking members, use of 'jargon' instead
of plain language, and the lack of technical knowledge/skills on the part
of some members being among them.

Yes but they wont be able to take advantage of the avx enhancements is the general gist, i believe

---

No Jason's post does NOT say that without AVX you won't be able to crunch v7. It says support for AVX will be built in.

So is that a 'YES', older processors will be able to
crunch V7 MB work units, or 'NO' they won't be able to
crunch V7 MB work units?

I would dearly love to see more unambiguous answers in this forum.
A lot of misinterpretation of answers occurs here, IMO,
for many reasons. Non-English speaking members, use of 'jargon' instead
of plain language, and the lack of technical knowledge/skills on the part
of some members being among them.

LOL...I am among those usually skilled in such things.
And I, right now, don't have a clue.
I got a the long version on our team forum that somehow eluded me.

Something about detaching and everything would be OK from there.

What I got out of it is this.
Those who have never given a rat's petoot about their rig's configuration should come out better.

Those of us who did might suffer a bit.

You all win, the kitties lose a bit of their edge.

---

"Time is simply the mechanism that keeps everything from happening all at once."

No Jason's post does NOT say that without AVX you won't be able to crunch v7. It says support for AVX will be built in.

So is that a 'YES', older processors will be able to
crunch V7 MB work units, or 'NO' they won't be able to
crunch V7 MB work units?

I would dearly love to see more unambiguous answers in this forum.
A lot of misinterpretation of answers occurs here, IMO,
for many reasons. Non-English speaking members, use of 'jargon' instead
of plain language, and the lack of technical knowledge/skills on the part
of some members being among them.

Yes older processors will still be able to process V7 workunits it's just that newer ones with on die graphics that support AVX extensions will benefit more.

Cheers.