I just recently got Einstein@Home and SETI@Home to crunch four WU's at a time on my GTX760, using an "app_config.xml" file. Can I do the same thing for SETI Beta; or, am I limited to one WU at a time for Beta?

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

I just recently got Einstein@Home and SETI@Home to crunch four WU's at a time on my GTX760, using an "app_config.xml" file. Can I do the same thing for SETI Beta; or, am I limited to one WU at a time for Beta?

Yes, an app_config.xml file can be used for this project and could be very similar to one for the main SETI@home project.

For SETI@home v7 tasks, be aware that the .vlar ones which are not sent to GPUs at the main project are sent here. Those Very Low Angle Range tasks present some challenges for parallel processing which at the least mean they run somewhat slowly on GPU and on some systems cause lags in normal screen presentation. And tasks here are split from a single file so work fetches will get a group of very similar tasks. Running multiple tasks which all happen to be .vlar might compound their difficulty. I doubt that will be a major problem, just felt you should be pre-warned.

                                                                   Joe

I just recently got Einstein@Home and SETI@Home to crunch four WU's at a time on my GTX760, using an "app_config.xml" file. Can I do the same thing for SETI Beta; or, am I limited to one WU at a time for Beta?

Yes, an app_config.xml file can be used for this project and could be very similar to one for the main SETI@home project.

For SETI@home v7 tasks, be aware that the .vlar ones which are not sent to GPUs at the main project are sent here. Those Very Low Angle Range tasks present some challenges for parallel processing which at the least mean they run somewhat slowly on GPU and on some systems cause lags in normal screen presentation. And tasks here are split from a single file so work fetches will get a group of very similar tasks. Running multiple tasks which all happen to be .vlar might compound their difficulty. I doubt that will be a major problem, just felt you should be pre-warned.

                                                                   Joe

Joe,

This is the app_config.xml I currently have for SETI Main:

app_config.xml

<app_config>
<app>
<name>astropulse_v6</name>
<max_concurrent>1</max_concurrent>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>1</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v7</name>
<max_concurrent>4</max_concurrent>
<gpu_versions>
<gpu_usage>0.25</gpu_usage>
<cpu_usage>0.05</cpu_usage>
</gpu_versions>
</app>
</app_config>

I've noticed; however, that "cpu_usage" here at Beta varies. One WU currently being worked on by my system is stating "0.275 CPU". First, will the above app_config.xml work here, and second, do I need to change the "cpu_usage" from the "0.05" that I have to "0.275"?

Thanks for the assistance.


TL

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

This is the app_config.xml I currently have for SETI Main:

app_config.xml

<app_config>
<app>
<name>astropulse_v6</name>
<max_concurrent>1</max_concurrent>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>1</cpu_usage>
</gpu_versions>
</app>
<app>
<name>astropulse_v7</name>
<max_concurrent>1</max_concurrent>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>1</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v7</name>
<max_concurrent>4</max_concurrent>
<gpu_versions>
<gpu_usage>0.25</gpu_usage>
<cpu_usage>0.05</cpu_usage>
</gpu_versions>
</app>
</app_config>

I've noticed; however, that "cpu_usage" here at Beta varies. One WU currently being worked on by my system is stating "0.275 CPU". First, will the above app_config.xml work here, and second, do I need to change the "cpu_usage" from the "0.05" that I have to "0.275"?

Thanks for the assistance.


TL

It should work here, and from your ~2200 seconds Run time and ~96 seconds CPU time for the same setup at main, the 0.05 is about right. The 0.275 is just an estimate produced by the servers.

Note that we're transitioning from astropulse_v6 to astropulse_v7 here. Although there are no Windows apps yet for AP v7 you might want to duplicate the AP v6 section with the new name as I've indicated in green.. There won't be any new WUs for AP v6 but resends for tasks which error or are inconclusive, etc. are possible.

                                                                  Joe

Joe,

Thank you VERY, VERY much! :-) I put in the app_config.xml as you had it; I did get a message from BOINC stating that it "does not recognize the 'AP v7'" - yet, however, it did start crunching multiple WU's. The bizarre thing was, that it started crunching two Beta MB and two SETI Main MB at the same time. So, I stopped all crunching, and changed the app_config.xml to crunch only three WU's at a time, restarted BOINC again and had to pause SETI Main to stop the two WU's from crunching there, then BOINC started crunching three Beta MB's. Very strange; however, it is working. :-)

[EDIT]

9:20 AM - PDT

Caught Beta crunching another Main task... I don't understand why it is doing this. I can't have it doing that, because soon Lunatics software will be taking over control of Main WU's... I don't think Beta can make a Main WU on Lunatics crunch properly, can it???

Maybe I should delete the app_info.xml from Beta...???... Any suggestions?

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

When you have multiple resources and are attached to multiple projects, it's normal for BOINC to start tasks for both projects. The way it decides what to run is complicated, but basically after having decided to run one task with 0.33 GPU it goes on to see what else can be run and may choose a task from the other project.

If you click a project on the projects tab, then the properties button, there's a "Scheduling priority" line shown. That's probably nearly the same for both projects, if one project had much higher priority then only tasks for that project would be run until the balance was restored.

                                                                   Joe

OK; so, knowing this helps. I've restored the app_config.xml for Beta to crunch 4 WU's at a time. I will monitor this and see what happens. Hopefully, as you say, it will sort itself out.

Right now; however, it's back to crunching two Main and two Beta WU's. :-/ (Weird...)

Thanks, again.


TL

[EDIT]

Yes, the "Priorities" are close. SETI Main is at -0.88; and, Beta is -0.87.


TL

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

Crunching four units on your GPU is a waste of time TL.
Your card performs better running 3 instances.

---

With each crime and every kindness we birth our future.

Crunching four units on your GPU is a waste of time TL.
Your card performs better running 3 instances.

Yes, I just noticed the times from three to four... I have changed it back to three; however, it is now crunching one Beta and two SETI Main MB's at a time... I'm hoping BOINC will correct and start crunching three Beta MB's at a time... We'll see.

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

I have read in "News" about the recent release of AP v7 for GPU's; however, BOINC, (upon startup with my new "app_config.xml"), keeps popping up a message:

SETI@home Beta Test: Notice from BOINC

Your app_config.xml file refers to an unknown application 'astropulse_v7'. Known applications: 'setiathome_v7', 'astropulse_v6'
7/4/2014 9:24:38 AM

app_config.xml

<app_config>
<app>
<name>astropulse_v6</name>
<max_concurrent>1</max_concurrent>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>1</cpu_usage>
</gpu_versions>
</app>
<app>
<name>astropulse_v7</name>
<max_concurrent>1</max_concurrent>
<gpu_versions>
<gpu_usage>1</gpu_usage>
<cpu_usage>1</cpu_usage>
</gpu_versions>
</app>
<app>
<name>setiathome_v7</name>
<max_concurrent>3</max_concurrent>
<gpu_versions>
<gpu_usage>0.33</gpu_usage>
<cpu_usage>0.04</cpu_usage>
</gpu_versions>
</app>
</app_config>

If my "app_config.xml" is incorrect; how should I correct it to properly run AP v7? (I got the AP v7 config settings from Joe; as mentioned by him, earlier in this Thread.)

[EDIT]

Or, do I just ignore BOINC, and see if I get an AP v7 sent to me???

[/EDIT]


Thanks,

TL

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

If my "app_config.xml" is incorrect; how should I correct it to properly run AP v7? (I got the AP v7 config settings from Joe; as mentioned by him, earlier in this Thread.)

Your app_config.xml is correct, you just don't have any astropulse_v7 work, the app_config can't override what's in your client_state.xml cause there's no mention of astropulse_v7, So get Ap v7 work.

Claggy

...
[EDIT]

Or, do I just ignore BOINC, and see if I get an AP v7 sent to me???

[/EDIT]


Thanks,

TL

Ignore the message, but it would be wise to check your SETI@home/AstroPulse Beta preferences to be sure Astropulse v7 applications are allowed. Eric did run a script to enable it for hosts which already had Astropulse v6 enabled, but if your host has asked for work recently I'm surprised it didn't get AP v7.

                                                                   Joe

It won't be getting AP 7 work right now; because it is crunching Einstein. Once through with Einstein, there are a lot of MB v7 WU's for it to go through. I'm sure that once it is caught up on what I already have that it will download AP v7.

Yes, AP v7 is checked in my preferences; so, again, once my current work is caught up, I should get some AP v7.

Thanks guys. :-)


TL

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

Update:

7-6-2014, 6:30 PM - PDT: Downloaded my first AP v7 WU. I will let you know when my system gets to crunching it, and when it finishes. :-)

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

Update 2:

Well, my Anti-Virus program seems to be ignoring the exclusions I set for BOINC, BOINC Project Folders, and BOINC ".exe" files. It persists in scanning running files and crashing them.

The AP v7 v7.00 that I've been waiting weeks for to run has crashed because of my Comodo Internet Security AV package. I don't know what to do with it anymore. They are based in New Jersey. If there is anything Eric can send to them to update C.I.S. it would greatly be appreciated.

Because I was at the computer to catch and manually exclude the second AP v7 v7.01; that file ran fine. I really don't know what else I can do with this AV Program.

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos