Stopped running 1.28, not worth it, switched to MilkyWay# home 1.01. Looks like no one else seems to care about the crazy long run times. No comparable projects out there that offer reasonable work value,, the result is I might just drop out of distributed computing all together.

What is this "value" of which you speak?

Knowledge, discovery, improvement in the human condition? Or just gollum-points you can't even exchange for a toaster?

Make your own decision, my friend - whether you contribute to distributed computing or not is entirely a personal choice. But there are other things to weigh in the balance, besides the credits.

Hi Edward,

I apologize for taking so long to get back to you. We are looking into the longer run times for the new app. It is possible we may need to adjust the credit allocation for completing MWSMF runs in the future. Another possibility is that there may be some optimizations to the code that need to be made. It will be at least another week until we are sure what the solution will be. Until then, we would appreciate you sticking with us, not necessarily crunching for MWSMF because it is a beta application, but definitely with our main stable version of Milky Way Separation. Please don't let the issues going on with MWSMF sully you opinion of the project or distributed computing in general.

Jake W.

So judgmental.
Mapping the Milky Way is wonderful and all and your idea of value is so grand and humane, blah blah blah.
Yes I do value my toaster in the morning, and coffee how delicious.

Jake,
Thank you.
I am currently running only MilkyWay@Home w/u's along with other projects.
It isn't all about the credits as I have been made out to be.
Ed

Just wondering if the Max # Errors could be increased?

Currently at 2, but with a Total # WUs of 9 and Total # Success at 6 it is not adding up.

I have successfully completed a WU only to find I was granted 0.00 as could not validate See Here.

It seems odd to me that some 'Modified Fit' work units need only a quorum of 1 but others need more, usually the slightly longer running ones it seems.

And quite often the 'Minimum Quorum' is 2 but 'Initial Replication' is 1 and credit is granted on the 1 work unit, again seems odd.

Conan

---

I agree with Conan. When there's a known fault with an app depending on execution source, the least you can do is adjust the max errors. I think I've mentioned it before but aborting by a user should not count toward errors either.

Hey guys,

Looks like the major problem was the large number of users aborting work units. I made a post asking for people to correct this. Hopefully, this will fix the invalid results and credit loss.

Jake W

I have had to stop doing these tasks as all they do is crash and burn on my system.

Not sure why they run so good on other systems and not mine, but in any case, modfit as it is currently written is not for me.

This application (like many before it) is accessing /home and being denied by SELinux. Please re-program your application to not access /home. Otherwise, it results in computation error.

FYI,

This has happened since version 1.24:
http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=3301&postid=59292

And previously with nBody:
http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=3171&postid=57607

Modfit 1.28 generates "computation error" immediately. 4 data sets downloaded this afternoon; all quit immediately. Also have had similar results in the past week or so. Running Win XP all updates, Core2 Duo. Also running Rosetta and Seti with few/no problems.

For now will remove Modfit from list of problem types accepted.

That is 2 of us with intel cpu's running Roesetta as well as this project.

All 3 task downloaded, crashed & burned almost right of way on my WIN XP SP3 (32 bit) PC 366384:
Tasks 594028263, 594028085 & 593781021.
All with same error message: Exit status -1073741795 (0xffffffffc000001d) Unknown error number

Stderr output
<core_client_version>6.12.34</core_client_version>
<![CDATA[
<message>
 - exit code -1073741795 (0xc000001d)
</message>
]]>

---

Hi Jake

I just came across this thread. Please see my thread here about an issue I am having with the current 1.28 OpenCL-nVidia app:

http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=3421&postid=60577#60577

Cheers

Mark

Thank you KIDH. I'm sorry this fix didn't help. Hopefully I will roll out another fix soon.

Thank you again,

Jake W

Hi Jake
Any news on a fix for the app for Windows 32 bit? (I'm assuming it's those versions as their not listed in the apps section, but are in the d/l folder).

---

Team AnandTech - SETI@H, DPAD, F@H, MW@H, A@H, LHC, POGS, R@H, Einstein@H, DHEP, WCG

Main rig - Ryzen 5 3600, MSI B450 G.Pro C. AC, RTX 3060Ti 8GB, 32GB DDR4 3200, Win 10 64bit
2nd rig - i7 4930k @4.1 GHz, HD 7870 XT 3GB(DS), 16GB DDR3 1866, Win7

Hello??

---

Team AnandTech - SETI@H, DPAD, F@H, MW@H, A@H, LHC, POGS, R@H, Einstein@H, DHEP, WCG

Main rig - Ryzen 5 3600, MSI B450 G.Pro C. AC, RTX 3060Ti 8GB, 32GB DDR4 3200, Win 10 64bit
2nd rig - i7 4930k @4.1 GHz, HD 7870 XT 3GB(DS), 16GB DDR3 1866, Win7