On my Lunatics 6 core cruncher I run 4 threads of GPU (2 per GTX 460) and 2 of CPU (remember, NV AP requires pretty much a core of CPU per GPU thread).

Also, CPU AP takes a looonnggg time, so I decided to abort all the AP 6.1 guys to avoid them. Lo and behold, I found that when I did so my AP 6.04s were being changed by BOINC to 6.1!

Is this a bug? feature? It is certainly NOT advertised, to the best of my knowledge...

ANd how do I stop it?

---

All AP WUs are the same when they leave the factory. They are 8 MB of data, with no v6.04 or v6.1 labelling.

They are labelled when they arrive on your computer, to give you a visual clue as to which application is going to process them. The label applies to the application, not the data.

Since you run anonymous platform, the figure you see - the label - is drawn from your app_info.xml file. There should be no v6.1 (or v6.10) labelling for AP tasks - that will cause you problems (cache trashing) when you update your applications in the future. Sounds like there's a typo in an app_info file or aistub flying around somewhere. Would you mind telling me where you got yours, so I can beat the author over the head with William's rolling pin?

btw if you don't want AP on CPU rerun the installer with AP for CPU unticked or delete the relevant section from app_info.xml.

Could you post a screenshot?

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

btw if you don't want AP on CPU rerun the installer with AP for CPU unticked or delete the relevant section from app_info.xml.

Could you post a screenshot?

Of what?

And I thought I HAD unticked AP for CPU when installing.

To fix it, should I just stop BOINC, re-install Lunatics (as is) - checking the AP CPU is unticked - and then redo the count from 1 -> .5 in the (I presume) wholly new app_info.xml?

And (Richard, I'm looking at you) how on Earth would it switch them from GPU to APU here, anyway? Never behaved like this before. To answer your question, I d/l the installer from Crunchers Anonymous.

---

And (Richard, I'm looking at you) how on Earth would it switch them from GPU to APU here, anyway? Never behaved like this before. To answer your question, I d/l the installer from Crunchers Anonymous.

Are you saying that you have an application for APU with assigned version number 6.1? BOINC can't switch like that - other things than just the version number would have to be changed (that's what Fred's old ReScheduler used to do).

The only way for it to happen would be by making a mistake during an app_info edit, with the result that the task could be discarded as unusable at restart. Then, the server might re-issue the task as a "resent lost task", but assign it to the different processor the second time round.

But my question would remain - where did you get an APU app_info with a v6.1 version number from? That isn't in the installer - only CPU and GPU apps there.

btw if you don't want AP on CPU rerun the installer with AP for CPU unticked or delete the relevant section from app_info.xml.

Could you post a screenshot?

Of what?

And I thought I HAD unticked AP for CPU when installing.

To fix it, should I just stop BOINC, re-install Lunatics (as is) - checking the AP CPU is unticked - and then redo the count from 1 -> .5 in the (I presume) wholly new app_info.xml?

And (Richard, I'm looking at you) how on Earth would it switch them from GPU to APU here, anyway? Never behaved like this before. To answer your question, I d/l the installer from Crunchers Anonymous.

A screenshot of the manager showing units marked as 6.1 :D

If you are getting AP on CPU you have an entry for it in app_info.xml.
Either rerun and reedit counts (yes wholly new app_info) or delete the AP section from app_info.xml
If you'd used Jason preferred method of editing the aistub for counts, you could just delete AP6_win_x86_SSE_CPU.aistub and rerun aimerge.
Still can do that instead of rerunning installer but one way or the other you need to edit the counts again.

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

And (Richard, I'm looking at you) how on Earth would it switch them from GPU to APU here, anyway? Never behaved like this before. To answer your question, I d/l the installer from Crunchers Anonymous.

Are you saying that you have an application for APU with assigned version number 6.1? BOINC can't switch like that - other things than just the version number would have to be changed (that's what Fred's old ReScheduler used to do).

The only way for it to happen would be by making a mistake during an app_info edit, with the result that the task could be discarded as unusable at restart. Then, the server might re-issue the task as a "resent lost task", but assign it to the different processor the second time round.

But my question would remain - where did you get an APU app_info with a v6.1 version number from? That isn't in the installer - only CPU and GPU apps there.

On that machine:

1) I look down the list of "ready to run" AP WUs.
2) I Ctrl-click to select all the 6.1s.
3) I hit the abort button
4) I watch and see some 6.04s change to 6.1

And, no, I haven't been drinking or smoking dope or eating mushrooms.

And, no matter how the app_info.xml may be mangled THAT shouldn't happen, right?

As far as the app_info.xml, it MAY be mangled because I had a problem (see earlier thread http://setiathome.berkeley.edu/forum_thread.php?id=71970) and just screwed it up somehow when copying back-and-forth from various backups trying to get it to work.

Come to think of it, when I finally got the app_info "straightened out" it had some 20 instances of the <count> in it. It should have been something like 6, right?

---

On that machine:

1) I look down the list of "ready to run" AP WUs.
2) I Ctrl-click to select all the 6.1s.
3) I hit the abort button
4) I watch and see some 6.04s change to 6.1

Are you sure you see 6.1 and not 6.01 (which is the right number for CPU AP from the installer AP6_win_x86_SSE_CPU.aistub) ?

Do you have this part in your app_info.xml (you see it is <version_num>601</version_num> and not 610=6.1)
(you can just delete this part to not do CPU AP)

    <app>
        <name>astropulse_v6</name>
    </app>
    <file_info>
        <name>AP6_win_x86_SSE_CPU_r1797.exe</name>
        <executable/>
    </file_info>
    <file_info>
        <name>libfftw3f-3.dll</name>
        <executable/>
    </file_info>
    <file_info>
        <name>ap_cmdline_win_x86_SSE_CPU.txt</name>
    </file_info>
    <app_version>
        <app_name>astropulse_v6</app_name>
        <version_num>601</version_num>
        <file_ref>
            <file_name>AP6_win_x86_SSE_CPU_r1797.exe</file_name>
            <main_program/>
        </file_ref>
        <file_ref>
            <file_name>libfftw3f-3.dll</file_name>
        </file_ref>
        <file_ref>
            <file_name>ap_cmdline_win_x86_SSE_CPU.txt</file_name>
            <open_name>ap_cmdline.txt</open_name>
        </file_ref>
    </app_version>

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Sorry - I meant to say 6.01

BTW, I redid the Lunatics install, and now all is OK - made sure CPU AP was unticked this time. Pretty sure now, seeing the install interface again, that I DID tick it the first time I installed...my bad.

However, still don't know why some 6.04s changed their spots to 6.01 whilst "Ready to Start" when I aborted all the previous 6.01s. AFAIK, this is new behavior for BOINC/SETI...eFMer lives!

---

However, still don't know why some 6.04s changed their spots to 6.01 whilst "Ready to Start" when I aborted all the previous 6.01s.

Again, are you sure that these new appeared 6.01 APs are the same old '6.04' tasks and not just new ones?

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

Absolutely. I watched them change in the tasks list; nothing was downloading at the time.

---