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.
If anyone runs into any problems please let me know.
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.
OK, I got a chance to update my anonymous hosts and the 1.24 app seems to be working fine on all my Winboxes.
Message 59263 - Posted: 7 Jul 2013, 16:45:39 UTC - in response to Message 59189.
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.
Message 59270 - Posted: 8 Jul 2013, 7:11:45 UTC - in response to Message 59193.
So use app_config instead of app_info.
It will download new versions of app itself.
Message 59272 - Posted: 8 Jul 2013, 11:21:46 UTC - in response to Message 59270.
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.
Message 59273 - Posted: 8 Jul 2013, 11:49:20 UTC - in response to Message 59272.
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.
Message 59275 - Posted: 8 Jul 2013, 12:46:12 UTC - in response to Message 59273.
Message 59276 - Posted: 8 Jul 2013, 13:47:04 UTC - in response to Message 59275.
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.
Message 59277 - Posted: 8 Jul 2013, 14:17:55 UTC - in response to Message 59276.
<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.
Message 59280 - Posted: 8 Jul 2013, 17:15:30 UTC - in response to Message 59279.
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.
Message 59376 - Posted: 16 Jul 2013, 4:11:43 UTC - in response to Message 59293.
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.
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.