I'm stopping work generation temporarily to try and get the assimilator/validator to catch up. Not quite sure what the problem is but hopefully will figure it out tonight.

---

Is that the cause of this error message I've been getting?

24/11/2010 03:34:23 Milkyway@home Sending scheduler request: To fetch work.
24/11/2010 03:34:23 Milkyway@home Requesting new tasks
24/11/2010 03:34:24 Milkyway@home Started upload of de_separation_16_3s_fix_1_59087_1290539160_0_0
24/11/2010 03:34:24 Milkyway@home Scheduler request completed: got 0 new tasks
24/11/2010 03:34:24 Milkyway@home Message from server: No work sent
24/11/2010 03:34:24 Milkyway@home Message from server: Your app_info.xml file doesn't have a version of MilkyWay@Home N-Body Simulation.
24/11/2010 03:34:26 Milkyway@home Finished upload of de_separation_16_3s_fix_1_59087_1290539160_0_0
24/11/2010 03:35:30 Milkyway@home Sending scheduler request: To fetch work.
24/11/2010 03:35:30 Milkyway@home Reporting 1 completed tasks, requesting new tasks
24/11/2010 03:35:32 Milkyway@home Scheduler request completed: got 0 new tasks
24/11/2010 03:35:32 Milkyway@home Message from server: No work sent
24/11/2010 03:35:32 Milkyway@home Message from server: Your app_info.xml file doesn't have a version of MilkyWay@Home N-Body Simulation.
24/11/2010 03:36:37 Milkyway@home Sending scheduler request: To fetch work.
24/11/2010 03:36:37 Milkyway@home Requesting new tasks
24/11/2010 03:36:38 Milkyway@home Scheduler request completed: got 0 new tasks
24/11/2010 03:36:38 Milkyway@home Message from server: No work sent
24/11/2010 03:36:38 Milkyway@home Message from server: Your app_info.xml file doesn't have a version of MilkyWay@Home N-Body Simulation.
24/11/2010 03:37:43 Milkyway@home Sending scheduler request: To fetch work.
24/11/2010 03:37:43 Milkyway@home Requesting new tasks
24/11/2010 03:37:45 Milkyway@home Scheduler request completed: got 0 new tasks
24/11/2010 03:37:45 Milkyway@home Message from server: No work sent
24/11/2010 03:37:45 Milkyway@home Message from server: Your app_info.xml file doesn't have a version of MilkyWay@Home N-Body Simulation.

It looks like you're using your own app_info.xml, and haven't accounted for the n-body simulation application.

---

Check here about what to add to your app_info.xml

Here's my xml:

<app_info>
<app>
<name>milkyway</name>
</app>
<file_info>
<name>astronomy_0.21_SSE3.exe</name>
<executable/>
</file_info>

<app_version>
<app_name>milkyway</app_name>
<version_num>21</version_num>
<file_ref>
<file_name>astronomy_0.21_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>

<app_version>
<app_name>milkyway</app_name>
<version_num>20</version_num>
<file_ref>
<file_name>astronomy_0.21_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
</app_info>

So I just add this:

<app>
<name>milkyway_nbody</name>
<user_friendly_name>MilkyWay@Home nbody Simulation</user_friendly_name>
</app>
<file_info>
<name>milkyway_nbody_0.21_windows_intelx86__sse2.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>milkyway_nbody</app_name>
<version_num>21</version_num>
<file_ref>
<file_name>milkyway_nbody_0.21_windows_intelx86__sse2.exe</file_name>
<main_program/>
</file_ref>
</app_version>

To it?

Nice hijacking of a thread.

But, to get back on topic:

Travis, is the splitter for the _17_3s_ workunits running? There is 3900+ WUs available for download and all I can get from the server is:

11/24/2010 1:57:28 PM Milkyway@home Message from server: No work sent
11/24/2010 1:57:28 PM Milkyway@home Message from server: Your app_info.xml file doesn't have a version of MilkyWay@Home N-Body Simulation.

The ratio of N-Body to other types of WUs for GPUs seems to be off a bit.

-Mike

---

Yes, I agree whole heartedly!
I got so tired of seeing that message(and the consequences)
I have reverted to the "stock" apps!
BTW, the validator seems to be on steroids now!
(no complaint there)

@ Zapped Sparky
Yes, insert those lines right before the "</app_info>"

@ mdhittle*
Would be nice to see 'Results ready to send' and 'Workunits waiting for validation' split into n-body and simulation numbers, right?

@ mdhittle*
Would be nice to see 'Results ready to send' and 'Workunits waiting for validation' split into n-body and simulation numbers, right?

Yes it would be great. DNETC@Home has a fantastic break out out the types of workunits available on their Server Status page. They even break it out to GPU type. It would be nice to see MW do something like that.

http://dnetc.net/server_status.php

-Mike

---