Hey all,

I just released a new version of Separation Modified Fit. Version 1.24 fixes some Mac compatability for users attempting to use GPUs and library issues for older versions of Linux.

In addition I put up some new runs:

de_modfit_09_3s_test_1
ps_modfit_09_3s_test_1
de_modfit_09_3s_testwrap_2
ps_modfit_09_3s_testwrap_1

If anyone runs into any problems please let me know.


Thank you,

Jake W

Were there any changes to the Windows apps, other than a version number change?

There was a code change that was implemented across the board but it should only effect Mac users.

OK, I'll have to make some updates to my app_info files for the hosts I have on the anonymous platform.

<edit>BTW, is there a reason why there isn't a 32 bit version of MWSMF for Winboxes?

We are working on it, but these bugs were on the top of the priority list for now. There seems to be one other small issue I need to look into before I start working on that.

Jake W.

OK, I got a chance to update my anonymous hosts and the 1.24 app seems to be working fine on all my Winboxes.

I run Milkyway on a Mac and I continue to receive the "GPU lacks necessary double precision extension" message. Is there anything I can do about this.

OK, I'll have to make some updates to my app_info files for the hosts I have on the anonymous platform.

<edit>BTW, is there a reason why there isn't a 32 bit version of MWSMF for Winboxes?

So use app_config instead of app_info.
It will download new versions of app itself.

Unfortunately, to workaround BOINC limitations in the way it handles multi-threaded CPU applications (nBody) you have to use the anonymous platform currently. Once you do that the app_config file is ignored.

So it's all or nothing in the app_info file.

Unfortunately, to workaround BOINC limitations in the way it handles multi-threaded CPU applications (nBody) you have to use the anonymous platform currently. Once you do that the app_config file is ignored.

So it's all or nothing in the app_info file.

Actually, not so.

Both app_info and app_config can be used at the same time: if both are present, and both contain values for what is fundamentally the same parameter (e.g. <coproc><count> in app_info is the same value as <gpu_versions><gpu_usage> in app_config), then the value in app_config takes precedence. (source: Josef W. Segur)

The thing you can't do is to run one Milkyway app (say, N-Body) under app_info, but use stock settings and automatic updating for other apps from the same project. If you wanted to run both N-Body and a GPU app here, you would have to write an app_info.xml file which defines the files and parameters for both applications.

Agreed. So in that case (which is what I'm doing) you may as well get rid of app_config since there isn't anything in it you can't do with app_info, and it's one less thing to worry about getting and keeping right. ;-)

<edit> IMHO, they got the precedence backwards simply because app_info is the more 'powerful' tool. But then what do I know? :-D

Agreed. So in that case (which is what I'm doing) you may as well get rid of app_config since there isn't anything in it you can't do with app_info, and it's one less thing to worry about getting and keeping right. ;-)

<edit> IMHO, they got the precedence backwards simply because app_info is the more 'powerful' tool. But then what do I know? :-D

One thing you can do with app_config that you can't do with app_info is to make changes 'on the fly', and apply them without stopping/restarting BOINC. That makes it a useful prototyping tool, especially on a system which also runs projects which don't checkpoint well.

There's also no equivalent of <max_concurrent> available in app_info.

LOL...

DOHHHH.... I stand corrected! That's what I get for not staying fully up to date over on the BOINC boards. :-)

I guess it would be too much to ask if Dr. Anderson could add the <max_concurrent> element to the anonymous platform, or at least add the ability to reread all app_info files on the fly, like you can do for the local prefs. ;-)

<edit> Is the rereading of app_config automatic, or do you have to use the Read Config File command or something like that?

You have to use the Read Config File command. When you issue that command it will adopt the new behavior of the app_config file.

In Boinc Manager, on the Tasks tab, the status column may continue to show the previous setting, but it should run the new settings. For example, if you previously had it set for each task to use 1 cpu and 1 nvidia gpu, and the revised setting is for each task to use 1 cpu and .5 nvidia gpu; the status column may continue to show 1 cpu and 1 nvidia gpu but it should actually operate with 1 cpu and .5 nvidia gpu. The wording will straighten out later.

Roger that. Thanks.

This binary is accessing my /home folder again, and it's being denied by SELinux. This causes the task to crash.

This was a problem before with the regular separation binaries, but you had fixed it there. Guess you should compare source code or something.

System:
Linux localhost 2.6.35.14-106.fc14.x86_64 #1 SMP Wed Nov 23 13:07:52 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

Getting these errors with modified fit:
../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_separation__modified_fit_1.24_x86_64-pc-linux-gnu: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ../../projects/milkyway.cs.rpi.edu_milkyway/milkyway_separation__modified_fit_1.24_x86_64-pc-linux-gnu)

Any word on this at all?

I cannot run any modified fit tasks until this is fixed. I think statically linking the glibc version GLIBC_2.14 will fix it.

I have a new version of the modified fit tested, I am just waiting for my current runs to finish. Once they are done, I will release it which should fix the problem.

Jake W.

Errors are still occurring, with following in stdout

Failed to calculate integral 0
Failed to calculate likelihood
<background_integral> nan </background_integral>
<stream_integral> nan nan nan </stream_integral>
<background_likelihood> nan </background_likelihood>
<stream_only_likelihood> nan nan nan </stream_only_likelihood>
<search_likelihood> nan </search_likelihood>
16:59:27 (9512): called boinc_finish

(http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=548714650)
Running on an XUbuntu 13.04, AMD7950 (factory-OCed), and nothing out of ordinary.

In the past few days I've seen 11 errors (out of 200+ WUs), all exactly identical.