Advanced search

Message boards : News : [wildlife] v0.13 apps released!

Previous · 1 · 2 · 3 · Next
Author Message
Travis Desell
Volunteer moderator
Project administrator
Project developer
Project scientist
Send message
Joined: 16 Jan 12
Posts: 1813
Combined Credit: 23,514,257
DNA@Home: 293,563
SubsetSum@Home: 349,212
Wildlife@Home: 22,871,482
Wildlife@Home Watched: 212,926s
Wildlife@Home Events: 51
Climate Tweets: 21
Images Observed: 774

              
Message 6702 - Posted: 27 Jan 2017, 1:19:31 UTC - in response to Message 6700.

as I noted before:
The only machines I see failing for everyone are windoz xp using AMD cpu


Hm, I wonder if visual studio didn't include the libraries required for XP... will look into it.

MB Atlanos
Send message
Joined: 1 May 13
Posts: 1
Combined Credit: 718,759
DNA@Home: 0
SubsetSum@Home: 0
Wildlife@Home: 718,759
Wildlife@Home Watched: 3,328s
Wildlife@Home Events: 3
Climate Tweets: 0
Images Observed: 0

  
Message 6704 - Posted: 27 Jan 2017, 3:29:23 UTC - in response to Message 6702.
Last modified: 27 Jan 2017, 3:39:24 UTC

Not only AMD and Win XP are failing, an old Intel Atom N270 and Win XP also:
http://csgrid.org/csg/results.php?hostid=47240

Travis Desell
Volunteer moderator
Project administrator
Project developer
Project scientist
Send message
Joined: 16 Jan 12
Posts: 1813
Combined Credit: 23,514,257
DNA@Home: 293,563
SubsetSum@Home: 349,212
Wildlife@Home: 22,871,482
Wildlife@Home Watched: 212,926s
Wildlife@Home Events: 51
Climate Tweets: 21
Images Observed: 774

              
Message 6705 - Posted: 27 Jan 2017, 3:44:21 UTC - in response to Message 6704.

Not only AMD and Win XP are failing, an old Intel Atom N270 and Win XP also:
http://csgrid.org/csg/results.php?hostid=47240


So then it may be some kind of win xp issue.

Profile [B@P] Daniel
Send message
Joined: 23 Sep 16
Posts: 28
Combined Credit: 8,537,989
DNA@Home: 0
SubsetSum@Home: 3,381
Wildlife@Home: 8,534,608
Wildlife@Home Watched: 0s
Wildlife@Home Events: 0
Climate Tweets: 163
Images Observed: 18

      
Message 6706 - Posted: 27 Jan 2017, 6:44:07 UTC - in response to Message 6705.
Last modified: 27 Jan 2017, 7:01:55 UTC

Not only AMD and Win XP are failing, an old Intel Atom N270 and Win XP also:
http://csgrid.org/csg/results.php?hostid=47240


So then it may be some kind of win xp issue.

There are no stderr logged for these tasks, what is weird. I tried to google for this error code and found some similar reports from other projects. Fortunately they had stderr log present, and there were messages like this:

Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Out Of Memory (C++ Exception) (0xe06d7363) at address 0x7C812A5B

Edit: I checked reports from other hosts here and they had stderr with the same error. Only that one PC does not stderr logged.

Edit2: this is probably caused by memory fragmentation: https://stackoverflow.com/questions/1617897/out-of-memory-problem-on-win32-vs-linux
____________

Chris Skull
Avatar
Send message
Joined: 11 Apr 15
Posts: 20
Combined Credit: 4,766,966
DNA@Home: 55,861
SubsetSum@Home: 1,272,523
Wildlife@Home: 3,438,582
Wildlife@Home Watched: 1,312,789s
Wildlife@Home Events: 475
Climate Tweets: 0
Images Observed: 46

            
Message 6707 - Posted: 27 Jan 2017, 8:33:42 UTC - in response to Message 6692.

isn't the granded credit a litle bit high ? :)

I also noticed that the v0.13 are about 80 percent faster than the previous versions but paying about the same credits.


EDIT: Should have said EIGHT TIMES faster.
Yes, very high granted credit for CPU work.


Okay I'll get the credit dropped down a bit. I did do quite a few performance enhancements while I was debugging.


still very high credit...
____________
Greetz
Chris

Travis Desell
Volunteer moderator
Project administrator
Project developer
Project scientist
Send message
Joined: 16 Jan 12
Posts: 1813
Combined Credit: 23,514,257
DNA@Home: 293,563
SubsetSum@Home: 349,212
Wildlife@Home: 22,871,482
Wildlife@Home Watched: 212,926s
Wildlife@Home Events: 51
Climate Tweets: 21
Images Observed: 774

              
Message 6708 - Posted: 27 Jan 2017, 17:15:25 UTC - in response to Message 6707.

isn't the granded credit a litle bit high ? :)

I also noticed that the v0.13 are about 80 percent faster than the previous versions but paying about the same credits.


EDIT: Should have said EIGHT TIMES faster.
Yes, very high granted credit for CPU work.


Okay I'll get the credit dropped down a bit. I did do quite a few performance enhancements while I was debugging.


still very high credit...


So credit for a workunit is determined at the time when it's generated, not when reported to the server -- so workunits generated before my previous credit adjustment are still going to be high.

If newly generated workunits are still too high I can make another adjustment, but I want to make sure that any adjustment is based off the new ones and not ones generated before I dropped the credit rate.

Travis Desell
Volunteer moderator
Project administrator
Project developer
Project scientist
Send message
Joined: 16 Jan 12
Posts: 1813
Combined Credit: 23,514,257
DNA@Home: 293,563
SubsetSum@Home: 349,212
Wildlife@Home: 22,871,482
Wildlife@Home Watched: 212,926s
Wildlife@Home Events: 51
Climate Tweets: 21
Images Observed: 774

              
Message 6709 - Posted: 27 Jan 2017, 17:18:28 UTC - in response to Message 6706.
Last modified: 27 Jan 2017, 17:19:00 UTC

Not only AMD and Win XP are failing, an old Intel Atom N270 and Win XP also:
http://csgrid.org/csg/results.php?hostid=47240


So then it may be some kind of win xp issue.

There are no stderr logged for these tasks, what is weird. I tried to google for this error code and found some similar reports from other projects. Fortunately they had stderr log present, and there were messages like this:

Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Out Of Memory (C++ Exception) (0xe06d7363) at address 0x7C812A5B

Edit: I checked reports from other hosts here and they had stderr with the same error. Only that one PC does not stderr logged.

Edit2: this is probably caused by memory fragmentation: https://stackoverflow.com/questions/1617897/out-of-memory-problem-on-win32-vs-linux


What I think is happening is if you look at the stderr that it's not finding the BOINC client:

03:46:10 (5440): Can't open init data file - running in standalone mode

This means that the directories for the input files isn't being set -- so it's actually not finding them. I need better error checking for that in my code. Then what happens is when it opens the samples file, which isn't there it gets some ridiculous numbers:

parsed arguments, loading images
number_classes: 1718580028
rowscols: 1768710004
vals_per_pixel: 775842670

What this should look like is:

parsed arguments, loading images
number_classes: 10
rowscols: 28
vals_per_pixel: 1

So when it allocates the data structure to hold the sample images, it thinks each image is 1768710004x1768710004x775842670 instead of 28x28x1. So it's pretty easy to see where the out of memory error is coming from...

But the real culprit is that the BOINC app isn't connecting to the BOINC client for some reason.

Profile Conan
Avatar
Send message
Joined: 13 Apr 12
Posts: 151
Combined Credit: 47,672,899
DNA@Home: 399,792
SubsetSum@Home: 1,448,876
Wildlife@Home: 45,824,231
Wildlife@Home Watched: 70,910s
Wildlife@Home Events: 0
Climate Tweets: 412
Images Observed: 0

          
Message 6710 - Posted: 28 Jan 2017, 22:25:34 UTC
Last modified: 28 Jan 2017, 22:26:45 UTC

This Work Unit has not validated due to 3 other computers not being able to run work units.
I believe the work unit is fine and does not have a bug (I ran it to completion).

The other three computers have not returned any successful work due to 3 different issues, one gets constant "signal 11" errors (Darwin), one has the Win XP problem and the last I think has Anti-virus issues).

So can the work unit be looked at being reissued so it can be validated please?

Thanks Travis

Conan
____________

Profile Bryan
Send message
Joined: 25 Aug 14
Posts: 4
Combined Credit: 113,102,344
DNA@Home: 608,637
SubsetSum@Home: 4,003,422
Wildlife@Home: 108,490,286
Wildlife@Home Watched: 0s
Wildlife@Home Events: 0
Climate Tweets: 0
Images Observed: 0

      
Message 6711 - Posted: 29 Jan 2017, 14:21:53 UTC
Last modified: 29 Jan 2017, 14:22:47 UTC

I had 3 show up this morning as "invalid". In each case the WU had been tried by XP machines that have not had a single valid WU out of 200 tried.

It is frustrating to spend 7 hours on WUs that probably have no problem only to have it discarded because machines with problems are pulling WU.

Travis Desell
Volunteer moderator
Project administrator
Project developer
Project scientist
Send message
Joined: 16 Jan 12
Posts: 1813
Combined Credit: 23,514,257
DNA@Home: 293,563
SubsetSum@Home: 349,212
Wildlife@Home: 22,871,482
Wildlife@Home Watched: 212,926s
Wildlife@Home Events: 51
Climate Tweets: 21
Images Observed: 774

              
Message 6712 - Posted: 29 Jan 2017, 20:55:29 UTC - in response to Message 6711.

I had 3 show up this morning as "invalid". In each case the WU had been tried by XP machines that have not had a single valid WU out of 200 tried.

It is frustrating to spend 7 hours on WUs that probably have no problem only to have it discarded because machines with problems are pulling WU.


Completely understandable. I've been trying to shake down a solution for this, so far just crickets from the BOINC mailing lists though.

Profile Beyond
Avatar
Send message
Joined: 4 Feb 15
Posts: 12
Combined Credit: 16,990,008
DNA@Home: 66,428
SubsetSum@Home: 195,743
Wildlife@Home: 16,727,837
Wildlife@Home Watched: 0s
Wildlife@Home Events: 0
Climate Tweets: 0
Images Observed: 0

      
Message 6723 - Posted: 30 Jan 2017, 17:46:35 UTC - in response to Message 6712.

I had 3 show up this morning as "invalid". In each case the WU had been tried by XP machines that have not had a single valid WU out of 200 tried.

It is frustrating to spend 7 hours on WUs that probably have no problem only to have it discarded because machines with problems are pulling WU.

Completely understandable. I've been trying to shake down a solution for this, so far just crickets from the BOINC mailing lists though.

These xp machines are spewing out thousands of failed WUs. Why not ban them until this gets sorted out or at least set a WU limit/day to mitigate the damage?

Travis Desell
Volunteer moderator
Project administrator
Project developer
Project scientist
Send message
Joined: 16 Jan 12
Posts: 1813
Combined Credit: 23,514,257
DNA@Home: 293,563
SubsetSum@Home: 349,212
Wildlife@Home: 22,871,482
Wildlife@Home Watched: 212,926s
Wildlife@Home Events: 51
Climate Tweets: 21
Images Observed: 774

              
Message 6724 - Posted: 30 Jan 2017, 18:18:29 UTC - in response to Message 6723.

I had 3 show up this morning as "invalid". In each case the WU had been tried by XP machines that have not had a single valid WU out of 200 tried.

It is frustrating to spend 7 hours on WUs that probably have no problem only to have it discarded because machines with problems are pulling WU.

Completely understandable. I've been trying to shake down a solution for this, so far just crickets from the BOINC mailing lists though.

These xp machines are spewing out thousands of failed WUs. Why not ban them until this gets sorted out or at least set a WU limit/day to mitigate the damage?


This is fixed now. I updated the plan class for windows workunits so that XP machines should not be downloading any more WUs.

Profile Beyond
Avatar
Send message
Joined: 4 Feb 15
Posts: 12
Combined Credit: 16,990,008
DNA@Home: 66,428
SubsetSum@Home: 195,743
Wildlife@Home: 16,727,837
Wildlife@Home Watched: 0s
Wildlife@Home Events: 0
Climate Tweets: 0
Images Observed: 0

      
Message 6725 - Posted: 30 Jan 2017, 18:43:19 UTC - in response to Message 6724.

These xp machines are spewing out thousands of failed WUs. Why not ban them until this gets sorted out or at least set a WU limit/day to mitigate the damage?

This is fixed now. I updated the plan class for windows workunits so that XP machines should not be downloading any more WUs.

Three thumbs up.

Profile Beyond
Avatar
Send message
Joined: 4 Feb 15
Posts: 12
Combined Credit: 16,990,008
DNA@Home: 66,428
SubsetSum@Home: 195,743
Wildlife@Home: 16,727,837
Wildlife@Home Watched: 0s
Wildlife@Home Events: 0
Climate Tweets: 0
Images Observed: 0

      
Message 6727 - Posted: 1 Feb 2017, 17:54:18 UTC - in response to Message 6699.

Dropped the credit awarded by a factor of 5. Probably still too high but I'll leave it at there for awhile given our alpha status and hopefully it will help attract some more crunchers. :)

The credits were high but now they seem low. Don't think you'll be attracting many users at this rate, in fact I see that some are leaving. The WU length has increased many fold and doesn't seem to be very well coordinated with the credits awarded. While the WU length is greatly increasing, credit doesn't seem to be increasing at all. Longer WUs are often credited less than shorter ones.

Travis Desell
Volunteer moderator
Project administrator
Project developer
Project scientist
Send message
Joined: 16 Jan 12
Posts: 1813
Combined Credit: 23,514,257
DNA@Home: 293,563
SubsetSum@Home: 349,212
Wildlife@Home: 22,871,482
Wildlife@Home Watched: 212,926s
Wildlife@Home Events: 51
Climate Tweets: 21
Images Observed: 774

              
Message 6728 - Posted: 1 Feb 2017, 18:30:49 UTC - in response to Message 6727.

Dropped the credit awarded by a factor of 5. Probably still too high but I'll leave it at there for awhile given our alpha status and hopefully it will help attract some more crunchers. :)

The credits were high but now they seem low. Don't think you'll be attracting many users at this rate, in fact I see that some are leaving. The WU length has increased many fold and doesn't seem to be very well coordinated with the credits awarded. While the WU length is greatly increasing, credit doesn't seem to be increasing at all. Longer WUs are often credited less than shorter ones.


Okay, I need to look into how I'm calculating credit. I'll bump it up a notch for the time being. How far off do you think it is right now?

Profile Beyond
Avatar
Send message
Joined: 4 Feb 15
Posts: 12
Combined Credit: 16,990,008
DNA@Home: 66,428
SubsetSum@Home: 195,743
Wildlife@Home: 16,727,837
Wildlife@Home Watched: 0s
Wildlife@Home Events: 0
Climate Tweets: 0
Images Observed: 0

      
Message 6731 - Posted: 1 Feb 2017, 19:21:40 UTC - in response to Message 6728.
Last modified: 1 Feb 2017, 19:25:08 UTC

Dropped the credit awarded by a factor of 5. Probably still too high but I'll leave it at there for awhile given our alpha status and hopefully it will help attract some more crunchers. :)

The credits were high but now they seem low. Don't think you'll be attracting many users at this rate, in fact I see that some are leaving. The WU length has increased many fold and doesn't seem to be very well coordinated with the credits awarded. While the WU length is greatly increasing, credit doesn't seem to be increasing at all. Longer WUs are often credited less than shorter ones.

Okay, I need to look into how I'm calculating credit. I'll bump it up a notch for the time being. How far off do you think it is right now?

The truth is that there's a large difference in credits awarded by various projects. No matter what you set it at some will be unhappy. The self appointed SETI credit cops will say it's too high no matter what it is. I don't think that most of us crunch primarily for credit but it definitely seems to be a consideration. Look at it this way, if a user likes a few projects equally which do you think that they'll go with primarily? If you want to increase participation, higher credit will definitely help achieve that. It's proven to be a fact of life in BOINC-land. I don't want to suggest a specific figure but I feel that it's too low presently.

Profile Gibson Praise
Avatar
Send message
Joined: 5 Aug 16
Posts: 56
Combined Credit: 50,846,655
DNA@Home: 0
SubsetSum@Home: 73,256
Wildlife@Home: 50,773,399
Wildlife@Home Watched: 0s
Wildlife@Home Events: 0
Climate Tweets: 769
Images Observed: 25,024

        
Message 7144 - Posted: 19 Jun 2017, 2:51:31 UTC - in response to Message 7141.

I also have this errors on my pc ??

..
26/01/2017 09:32:03 Citizen Science Grid Starting task exact_genome_1485416402_21_6679_0 using exact version 13
..

Why are you posting about errors from 5 months ago? ( since you just joined today?). The current version of exact is 30.

Remove the project and re-add.
____________

Profile PDW
Send message
Joined: 10 Aug 14
Posts: 26
Combined Credit: 125,270,288
DNA@Home: 2,517,852
SubsetSum@Home: 5,000,796
Wildlife@Home: 117,751,640
Wildlife@Home Watched: 0s
Wildlife@Home Events: 0
Climate Tweets: 31
Images Observed: 14

          
Message 7145 - Posted: 19 Jun 2017, 7:07:14 UTC - in response to Message 7144.

It is just a spam account posting to get you to click on the 'free vps' link embedded in the event log listing.

Profile Gibson Praise
Avatar
Send message
Joined: 5 Aug 16
Posts: 56
Combined Credit: 50,846,655
DNA@Home: 0
SubsetSum@Home: 73,256
Wildlife@Home: 50,773,399
Wildlife@Home Watched: 0s
Wildlife@Home Events: 0
Climate Tweets: 769
Images Observed: 25,024

        
Message 7146 - Posted: 19 Jun 2017, 14:29:50 UTC

Well crap! @!&%$ spammers ..

Previous · 1 · 2 · 3 · Next
Post to thread

Message boards : News : [wildlife] v0.13 apps released!