New Separation Modfit Version 1.36
log in

Advanced search

Message boards : News : New Separation Modfit Version 1.36

Previous · 1 · 2
Author Message
Stick
Send message
Joined: 8 Oct 07
Posts: 31
Credit: 281,487
RAC: 120

Message 62583 - Posted: 16 Oct 2014, 19:24:23 UTC - in response to Message 62582.

Your Win32 machines will no longer be receiving Modfit work units so that won't be a problem any more.

I was aware of the ongoing Win32 problems and that you had subsequently blocked Modfit from Win32 machines. I was just trying to add some specifics to the discussion - that my Win32 errors were immediate computation errors [-1073741515 (0xffffffffc0000135) Unknown error number]. Other posts on this thread seemed to indicate that some Win32 units were failing after processing for significant amounts of time.

As for your 64 bit computer that is completely normal. We require ~3 computers to return the same result for every work unit we send out. Validation inconclusive just means we are waiting for others to return their results for the work unit before we award credit. This ensure people aren't trying to game the system just for credits and it ensures we are getting reliable results for our optimizations.

It may be Milkyway "completely normal" but it's not BOINC "completely normal". ;-)

Richard Haselgrove
Send message
Joined: 4 Sep 12
Posts: 218
Credit: 448,778
RAC: 0

Message 62585 - Posted: 16 Oct 2014, 23:50:01 UTC - in response to Message 62583.

Your Win32 machines will no longer be receiving Modfit work units so that won't be a problem any more.

I was aware of the ongoing Win32 problems and that you had subsequently blocked Modfit from Win32 machines. I was just trying to add some specifics to the discussion - that my Win32 errors were immediate computation errors [-1073741515 (0xffffffffc0000135) Unknown error number]. Other posts on this thread seemed to indicate that some Win32 units were failing after processing for significant amounts of time.

Isn't 0xc0000135 (expressing it in 32 bits) the very old and very well known 'The application failed to initialize properly' STATUS_DLL_NOT_FOUND?

Shouldn't somebody be checking to see what DLLs are required by the application (http://www.dependencywalker.com/ is your friend), what DLLs are being sent out, and why there's a difference between the two?

Jake Weiss
Volunteer moderator
Project developer
Project tester
Project scientist
Send message
Joined: 25 Feb 13
Posts: 440
Credit: 10,663,140
RAC: 219,013

Message 62586 - Posted: 17 Oct 2014, 16:44:02 UTC

Thank you Richard. I will look into it when I get a chance. Might not be for a few days though. Things have gotten very busy here.

Jake W.

Tom*
Send message
Joined: 4 Oct 11
Posts: 33
Credit: 268,994,839
RAC: 397,513

Message 62588 - Posted: 18 Oct 2014, 0:20:33 UTC
Last modified: 18 Oct 2014, 0:45:20 UTC

Several people running ati? were experiencing 6% validate errors on modfit runs.

I just started with my HD7950 with same drivers I have been using for several years. These drivers produced no invalids back in April for a team challenge.

SETI recently noticed that an API bug in BOINC truncates the STDERR sent to the server. ALL of my Invalids have this example
Stderr output

<core_client_version>7.2.42</core_client_version>
<![CDATA[
<stderr_txt>

</stderr_txt>
]]>

http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=573186&offset=0&show_names=0&state=5&appid=

Windows 7 64 bit boinc 64 bit. FX-8350

My i5-3570 with GTX660 does not show any invalids

Thanks

Will test my A8-5800 in a couple of days it also has an HD7950

Michael Bennett
Send message
Joined: 10 Mar 09
Posts: 13
Credit: 4,300,514
RAC: 3,766

Message 62589 - Posted: 18 Oct 2014, 3:31:13 UTC - in response to Message 62565.

Thank you for the reply. I'll allow another load of work units to be off loaded onto my computer and see how it goes. As I recall, some Modfit 1.36 wu's were still coming through and gumming up the works, lol. Hope you have a good weekend. Mike

Profile Cosmin Stanescu
Send message
Joined: 8 Aug 13
Posts: 1
Credit: 14,635
RAC: 0

Message 62590 - Posted: 18 Oct 2014, 5:45:38 UTC
Last modified: 18 Oct 2014, 5:50:11 UTC

I've been running this N-body simulation wu (one core, not modfit) since oct 6. The estimated remaining time always says 16 hours, but it already has had 77 CPU hours and it's only at 30% and today's the deadline. Any idea why it takes so much time? It's the first wu that takes this long. Usually the estimates are optimistic.

Jake Weiss
Volunteer moderator
Project developer
Project tester
Project scientist
Send message
Joined: 25 Feb 13
Posts: 440
Credit: 10,663,140
RAC: 219,013

Message 62594 - Posted: 18 Oct 2014, 23:27:18 UTC

Hey all,

Tom*, we did some updates to the BOINC libraries we compile against so maybe the issue lies there. I will look to see if there are any newer versions for us to use. Thank you for the reply.

Cosmin, I don't work much on the nbody application but 77 hours seems pretty long, probably okay just to abort that. If you post in one of the nbody posts on the news section, someone who works more closely with nbody might be better able to answer your question.

Jake W.

cyrusNGC_224@P3D
Send message
Joined: 2 Apr 13
Posts: 10
Credit: 753,496,489
RAC: 1,215,801

Message 62603 - Posted: 20 Oct 2014, 18:37:01 UTC
Last modified: 20 Oct 2014, 18:37:09 UTC

Tentatively i have activated modified-fit yesterday.
To date, over one day no error occurred.
It seems ok.

http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=510433

Jake Weiss
Volunteer moderator
Project developer
Project tester
Project scientist
Send message
Joined: 25 Feb 13
Posts: 440
Credit: 10,663,140
RAC: 219,013

Message 62604 - Posted: 21 Oct 2014, 3:28:20 UTC

Thanks! Glad everything is working well on your end. I appreciate the extra help.

Jake W.

Profile Mumak
Avatar
Send message
Joined: 8 Apr 13
Posts: 89
Credit: 515,960,170
RAC: 3,220

Message 62605 - Posted: 21 Oct 2014, 6:22:18 UTC

I'm too seeing a higher error rate of the Modfit since a few weeks (several dozen invalids per day). Had to opt-out...

Jake Weiss
Volunteer moderator
Project developer
Project tester
Project scientist
Send message
Joined: 25 Feb 13
Posts: 440
Credit: 10,663,140
RAC: 219,013

Message 62606 - Posted: 21 Oct 2014, 12:43:42 UTC

Hi Mumak,

Looks like you are also running into the AMD issue. I will try to look into the issue a bit more and see if it needs to be a fix on our end or BOINC.

Jake W.

greg_be
Send message
Joined: 18 Aug 09
Posts: 83
Credit: 3,773,703
RAC: 4,338

Message 62613 - Posted: 22 Oct 2014, 23:02:49 UTC

switched back to 64 bit boinc last week. things are running smooth now.
open cl problems solved as well
so back to letting this project churn in the background and turn back some smooth results now.

Previous · 1 · 2
Post to thread

Message boards : News : New Separation Modfit Version 1.36


Main page · Your account · Message boards


Copyright © 2017 AstroInformatics Group