We started some new runs today.

The runs are:

de_separation_82_3s_dr8_2
se_separation_82_3s_dr8_2

These will involve new star files.
Please be patient as the new star files are distributed.

Thank you,

Jeff Thompson

---

Are these WUs much longer than the previous ones?

I'm asking because my BOINC client decided to switch to panic mode immediately after it got one of them.

Here's the WU's XML definition:

<workunit>
    <name>ps_separation_82_3s_dr8_2_1358941502_29559263</name>
    <app_name>milkyway</app_name>
    <version_num>100</version_num>
    <rsc_fpops_est>89643799999999993000000000000000.000000</rsc_fpops_est>
    <rsc_fpops_bound>89643799999999998000000000000000000.000000</rsc_fpops_bound>
    <rsc_memory_bound>50000000.000000</rsc_memory_bound>
    <rsc_disk_bound>15000000.000000</rsc_disk_bound>
    <command_line>
-np 20 -p 0.943595320917666 23.0867525425274 -17.2245569434017 30.1253113951534 27.7632766885683 1.17406084491819 4.12454840047643 13.0079187392257 -11.5395608730614 39.1341196808498 22.0797624444123 0.980515889188198 1.62739609185373 12.7507249950431 13.1226277071983 41.4128890240099 30.2472704153508 6.16794836081251 3.20157651974716 5.24611199158244
    </command_line>
    <file_ref>
        <file_name>p-82-3s-dr8-2.txt</file_name>
        <open_name>astronomy_parameters.txt</open_name>
    </file_ref>
    <file_ref>
        <file_name>stars-82-dr8.txt</file_name>
        <open_name>stars.txt</open_name>
    </file_ref>
</workunit>

<rsc_fpops_est> is much higher than it's used to be. BOINC deducted an estimated execution time of more then 24 hours...

I have got some of them and the estimate run time is 87600 hours !!!! even CPDN tasks dont take that long.
All tasks are now running in high priority and BM will not download any new work because of the crazy high estimate run times,
The estimate 89643799999999998000000 GFLOPs for that task :()
And that is on a ATI 7970 that usualy takes about one minuet to crunch a `sep` task,
Me thinks something is wrong :)

EDIT - one of them just finished is 62 seconds as normal,
The rest sufer a Computation Error as soon as they start. Too many errors (may have bug)

Yep, there definitely is something wrong with these tasks. Mine was crashing after a split second. Here's the stderr output:

<core_client_version>7.0.28</core_client_version>
<![CDATA[
<message>
Unzul�ssige Funktion. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
<search_application> milkyway_separation 1.00 Windows x86 double </search_application>
Unrecognized XML in project preferences: max_gfx_cpu_pct
Skipping: 0
Skipping: /max_gfx_cpu_pct
Unrecognized XML in project preferences: apps_selected
Skipping: app_id
Skipping: /apps_selected
Unrecognized XML in project preferences: nbody_graphics_poll_period
Skipping: 30
Skipping: /nbody_graphics_poll_period
Unrecognized XML in project preferences: nbody_graphics_float_speed
Skipping: 5
Skipping: /nbody_graphics_float_speed
Unrecognized XML in project preferences: nbody_graphics_textured_point_size
Skipping: 250
Skipping: /nbody_graphics_textured_point_size
Unrecognized XML in project preferences: nbody_graphics_point_point_size
Skipping: 40
Skipping: /nbody_graphics_point_point_size
Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4' 
Error reading astronomy parameters from file 'astronomy_parameters.txt'
  Trying old parameters file
Integral area { 1819239215, 1769234796, 1008738314 } will overflow progress calculation
Error reading parameters file
Failed to read parameters file
19:51:28 (4132): called boinc_finish

</stderr_txt>
]]>

I also have only task which errored out after a one second or less.

---

Yep, there's something wrong with those. Estimated runtime 87600 hours and error out instantly.

Interesting thing: one of my wingmen was doing such WU on ARM and could complete it in 20 seconds. The std_err output however does not look healthy.

---

Hi, has 3 incorrect tasks with the same error.
http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=429446376
http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=429449911
http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=429450303
stderr output

<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)
</message>
<stderr_txt>
<search_application> milkyway_separation 1.00 Linux x86_64 double </search_application>
Unrecognized XML in project preferences: max_gfx_cpu_pct
Skipping: 20
Skipping: /max_gfx_cpu_pct
Unrecognized XML in project preferences: apps_selected
Skipping: app_id
Skipping: app_id
Skipping: /apps_selected
Unrecognized XML in project preferences: nbody_graphics_poll_period
Skipping: 30
Skipping: /nbody_graphics_poll_period
Unrecognized XML in project preferences: nbody_graphics_float_speed
Skipping: 5
Skipping: /nbody_graphics_float_speed
Unrecognized XML in project preferences: nbody_graphics_textured_point_size
Skipping: 250
Skipping: /nbody_graphics_textured_point_size
Unrecognized XML in project preferences: nbody_graphics_point_point_size
Skipping: 40
Skipping: /nbody_graphics_point_point_size
Error loading Lua script 'astronomy_parameters.txt': [string "number_parameters: 4..."]:1: '<name>' expected near '4' 
Error reading astronomy parameters from file 'astronomy_parameters.txt'
  Trying old parameters file
Integral area { 1819239215, 1769234796, 1008738314 } will overflow progress calculation
Error reading parameters file
Failed to read parameters file
19:17:36 (31649): called boinc_finish

</stderr_txt>
]]>

I pulled these runs down. I think I know what the issue is - the step sizes in the volume integral were set too small, which ironically causes the server to freak out because of a fix that was implemented due to some big step sizes that made the server freak out.

We should have them repaired and back up later tonight.

I have started new runs with larger step counts I am creating a new thread for these runs.


Thank you

Jeff Thompson

I'm getting the error that they were getting back in March now in June.

I get the following:

<search_application> milkyway_separation 1.00 Windows x86_64 double </seach_application> Unrecognized XML in project preferences: max_gfx_cpu_pct Skipping: 40 Skipping: /max_gfx_cpu_pct Unrecognized XML in project preferences: allow_non_preferred_apps S

its cut off after the S on that one.

Then another one is

<search application> milkyway_nobody 1.18 Windows x86_64 double OpenMP, Crlibm </search application> Using Open MP 1 max threads on a system with 8 processors Could not load Ktm32.dll(126): The specified module could not be found <search likelihood> -942

its cut off after that. I searched my system and I do not have a file called Ktm32.dll.

Finally I get the following:

<search application> milkyway_separaton 1.22 Windowx x86_64 double </search application> Reading preferences ended prematurely Error loading Lua script 'astronomy_parameters.txt': [strong number_parameters: 4...]:1 '<name>' expected near '4' Error rea

and it cuts off after that. I searched and I dont have a file called astronomy_parameters.txt.

I've gotten several of each type error recently. Should I be fixing something?

Thanks...

James

---

Joined MilkyWay@Home in 2012
Online since ArpNET days
First activity on Honeywell 1648
Series Mainframe in 1975 at age 12.

I've gotten several of each type error recently. Should I be fixing something?

Since you have no errors or invalids in your results, I'd say no. Missing astronomy_parameters.txt is completely normal, the others does not look "dangerous".

I mean, it runs, that's good enough.

---

ok thanks

---

Joined MilkyWay@Home in 2012
Online since ArpNET days
First activity on Honeywell 1648
Series Mainframe in 1975 at age 12.