Hello,

Has astropulse v6 been removed from the project? How to edit the app_info.xml to get rid of these server error messages?

15/07/2015 10:05:54 | SETI@home | Sending scheduler request: To fetch work.
15/07/2015 10:05:54 | SETI@home | Requesting new tasks for CPU and NVIDIA GPU
15/07/2015 10:05:54 | SETI@home | [sched_op] CPU work request: 5047.21 seconds; 0.00 devices
15/07/2015 10:05:54 | SETI@home | [sched_op] NVIDIA GPU work request: 101298.03 seconds; 0.35 devices
15/07/2015 10:05:54 | SETI@home | [sched_op] Intel GPU work request: 0.00 seconds; 0.00 devices
15/07/2015 10:05:57 | SETI@home | Scheduler request completed: got 1 new tasks
15/07/2015 10:05:57 | SETI@home | [sched_op] Server version 707
15/07/2015 10:05:57 | SETI@home | Message from server: Unknown app name astropulse_v6 in app_info.xml
15/07/2015 10:05:57 | SETI@home | Message from server: Unknown app name astropulse_v6 in app_info.xml
15/07/2015 10:05:57 | SETI@home | Message from server: Unknown app name astropulse_v6 in app_info.xml
15/07/2015 10:05:57 | SETI@home | Message from server: Unknown app name astropulse_v6 in app_info.xml
15/07/2015 10:05:57 | SETI@home | Message from server: Unknown app name astropulse_v6 in app_info.xml
15/07/2015 10:05:57 | SETI@home | Message from server: Unknown app name astropulse_v6 in app_info.xml
15/07/2015 10:05:57 | SETI@home | Message from server: Unknown app name astropulse_v6 in app_info.xml
15/07/2015 10:05:57 | SETI@home | Message from server: Unknown app name astropulse_v6 in app_info.xml
15/07/2015 10:05:57 | SETI@home | Project requested delay of 303 seconds
15/07/2015 10:05:57 | SETI@home | [sched_op] estimated total CPU task duration: 9905 seconds
15/07/2015 10:05:57 | SETI@home | [sched_op] estimated total NVIDIA GPU task duration: 0 seconds
15/07/2015 10:05:57 | SETI@home | [sched_op] estimated total Intel GPU task duration: 0 seconds
15/07/2015 10:05:57 | SETI@home | [work_fetch] backing off NVIDIA GPU 433 sec
15/07/2015 10:05:57 | SETI@home | [sched_op] Deferring communication for 00:05:03
15/07/2015 10:05:57 | SETI@home | [sched_op] Reason: requested by project
15/07/2015 10:05:57 | | [work_fetch] Request work fetch: RPC complete

---

Don't treat them as error messages (even if they're highlighted in scary red lettering).

Work for all applications that are listed in app_info will continue to be processed as normal (when available).

They're there for information - they're particularly useful if you write your own app_info.xml file, and want to check that you've got it right.

And yes - we stopped crunching Astropulse_v6 last year, and the final vestiges were cleaned out of the system earlier this month.

So would it be safe to remov all astopulse v6 insances from app_info.xml then? Has it been replaced with v7?

---

So would it be safe to remov all astopulse v6 insances from app_info.xml then? Has it been replaced with v7?

It was replaced by Astropulse_v7 in October last year.

If you understand the format of app_info.xml, and can remove the astropulse_v6 sections without violating the structural integrity of the file, then by all means do so. But others have tried and failed, losing all cached work in the process. app_info.xml is very unforgiving of finger-fumbles.

others have tried and failed, losing all cached work in the process. app_info.xml is very unforgiving of finger-fumbles.

Ahh so that's what happen'd get the syntax wrong even a little bit (i forgot to correct the syntax and had a space where i should not have ) and the dam thing throws a fit and losses all the units ......


GRRRRRRRRRRR

no worry's all ok now was just a bit peed of tho when it did it . Only problem now is i have to wait till they time out as the stats show i have more units in progress than i actually have .

---

Safest thing to do is put the whole app_info.xml file on the forums and wait for someone to post/pm you the revised version. Some of us do know how to edit the file correctly. :)

And yes, if you want, you can PM me the thing, I'll send you the revised version back.

---

Cliff and Chris S helped. Any others? ;-)

---

I'm a coward, I'll wait till lunatics comes out with their next installer. I learned a long time ago not to fix something that's not broken.

---

I use Notepad++ for this as it'll tell if I miss something. Had to do Cliff's version twice as even I got lost, his was huge. :)

---

Hi Jord,

With a bit of luck if Richard comes up with a new lunatics installer it will get shorter:-)
Thanks for your assistance.

Cheers,
Cliff

---

Cliff,
Been there, Done that, Still no damm T shirt!

Yea I know it's a big file.

I didn't have any problem removing the v6 coding, but would like to clean the file up.

I have 12 entries for AVX, and I use 1 of them ... but which one? LOL

I'm sure I can remove at least half of them confidently, but there's always the chance of screwing up :(

---

When I printed mine out it was 14 A4 pages long!! I'm sure Richard could explain why it needs to be that big. I mean it's basically a sort of sophisticated batch file setting up variables isn't it??

A batch file suggests starting at the top and working downwards. No, it doesn't really do that.

Think of it more like a loose-leaf binder of specifications, or recipes. Recipies would be good, because that implies both ingredients and cooking processing instructions.

The installer has to contain a recipe card for every possible task it might encounter on your system when it's first installed. That's any work allocated to a stock app, plus any work left over from a previous Lunatic. So the next one will be smaller (no AP_v6), but then again it will be larger, because somebody slipped in a stock version 7.07 for multibeam apps on ATI cards, with no fewer than six different plan classes. And we know the server likes to try every one of them when a new app is released...

Many thanks for that reply Richard, that allusion to menu cards explains it very well to me. Soooo who is this naughty somebody slipping thingies in then? And do we need six different plan classes anyway?

Edit - Apparently we do Plan Classes

To which add, SETIatHome Applications. Some people use BOINC clients that can schedule OpenCL applications themselves, some older clients have to be helped. Some ATI drivers can be identified by their CAL version, some can't. And so on.

Safest thing to do is put the whole app_info.xml file on the forums and wait for someone to post/pm you the revised version. Some of us do know how to edit the file correctly. :)

And yes, if you want, you can PM me the thing, I'll send you the revised version back.

No, the safest option is to go into your project directory, delete the AP6_win_***_***_CPU.aistub and/or the AP6_win_x86_SSE2_OpenCL_ATI.aistub and/or the AP6_win_x86_SSE2_OpenCL_NV.aistub and just run aimergeg.cmd, then restart Boinc.

Claggy

No, the safest option is to go into your project directory, delete the AP6_win_***_***_CPU.aistub and/or the AP6_win_x86_SSE2_OpenCL_ATI.aistub and/or the AP6_win_x86_SSE2_OpenCL_NV.aistub and just run aimergeg.cmd, then restart Boinc.

Claggy

Why nobody say this before ?

Thanks you Claggy !

---

Honorez la Sainte Spatule !

Safest thing to do is put the whole app_info.xml file on the forums and wait for someone to post/pm you the revised version. Some of us do know how to edit the file correctly. :)

And yes, if you want, you can PM me the thing, I'll send you the revised version back.

No, the safest option is to go into your project directory, delete the AP6_win_***_***_CPU.aistub and/or the AP6_win_x86_SSE2_OpenCL_ATI.aistub and/or the AP6_win_x86_SSE2_OpenCL_NV.aistub and just run aimergeg.cmd, then restart Boinc.

Claggy

But wouldn't that trash any manual edits, like for AP r2887, a requirement for NV driver 350.12 and above? If that reverts, then any APs in the queue get dumped, right?

Safest thing to do is put the whole app_info.xml file on the forums and wait for someone to post/pm you the revised version. Some of us do know how to edit the file correctly. :)

And yes, if you want, you can PM me the thing, I'll send you the revised version back.

No, the safest option is to go into your project directory, delete the AP6_win_***_***_CPU.aistub and/or the AP6_win_x86_SSE2_OpenCL_ATI.aistub and/or the AP6_win_x86_SSE2_OpenCL_NV.aistub and just run aimergeg.cmd, then restart Boinc.

Claggy

But wouldn't that trash any manual edits, like for AP r2887, a requirement for NV driver 350.12 and above? If that reverts, then any APs in the queue get dumped, right?

Yes, It's for a Pure Stock Lunatics Installation only, ie 99% of the users out there, If you're an Advanced user you're quite capable of making the edits without problems.

Claggy

Safest thing to do is put the whole app_info.xml file on the forums and wait for someone to post/pm you the revised version. Some of us do know how to edit the file correctly. :)

And yes, if you want, you can PM me the thing, I'll send you the revised version back.

No, the safest option is to go into your project directory, delete the AP6_win_***_***_CPU.aistub and/or the AP6_win_x86_SSE2_OpenCL_ATI.aistub and/or the AP6_win_x86_SSE2_OpenCL_NV.aistub and just run aimergeg.cmd, then restart Boinc.

Claggy

But wouldn't that trash any manual edits, like for AP r2887, a requirement for NV driver 350.12 and above? If that reverts, then any APs in the queue get dumped, right?

Yes, It's for a Pure Stock Lunatics Installation only, ie 99% of the users out there, If you're an Advanced user you're quite capable of making the edits without problems.

Claggy

Thanks. Appreciate the clarification/qualification.

EDIT: Of course, I thought Lunatics was only for Advanced Users in the first place! ;^)

i manually updated apps on my three computers. i had a dll problem a couple times before i figured it out. on one computer i had already run the cache down. on the other two i lost tasks probably due to a change in plan class couple with resend being turned off.

Thanks. Appreciate the clarification/qualification.

EDIT: Of course, I thought Lunatics was only for Advanced Users in the first place! ;^)

I think the installer is to make the apps accessible for those that are less technically inclined.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[