I hadn't had a computer on as much recently and noticed I wasn't getting any credit. Ijust noticed the results were past the time. If I am not going to get credit for the time I volunteer for crunching it would be nice if the client would go ahead and throw out the results since they are useless.

---

I am confused, you do not run your computer and now you want BOINC to clean it up for you, jeeezzz just run the computer, one of your computers shows no WUs and the other shows one due the 12th and 21st.


Check out BoincView it has lots of bells and whistles.

http://boincview.amanheis.de/

---

Semper Eadem
So long Paul, it has been a hell of a ride.

Park your ego's, fire up the computers, Science YES, Credits No.

I see the point that one should configure their system only to download WU's if the machine will be on long enough to cruch them (in time for the deadline), but ksnash has a point that the client end could be tweaked to abort the number crunching if a unit passes it's deadline before completing. Might not be a bad idea for future versions. Of course one could argue that this would encourage downloading of WU's without regard to deadlines..... Ah, what a confusing world we live in....

> I am confused, you do not run your computer and now you want BOINC to clean it
> up for you, jeeezzz just run the computer, one of your computers shows no WUs
> and the other shows one due the 12th and 21st.
>
>
> Check out BoincView it has lots of bells and whistles.
>
> http://boincview.amanheis.de/
>

---

<br><br><img src='http://www.boincsynergy.com/images/stats/1185sah.png'> <br>
Thanks to Tim (Captain Avatar) for my groovy Red Foxx avatar!

Knash, You have been around a long time in classic and we are glad youre here,
But give us a break will you! You know you are crunching numbers and you can't do that with the computer in the off mode. If youre going to run BOINC set your'e preferences to 1 day and let it run see how long it takes to complete and adjust
but for gods sake Man turn on your machine!

Welcome again!




CA

---

> I see the point that one should configure their system only to download WU's
> if the machine will be on long enough to cruch them (in time for the
> deadline), but ksnash has a point that the client end could be tweaked to
> abort the number crunching if a unit passes it's deadline before completing.
> Might not be a bad idea for future versions.

Fred, the version of BOINC i'm using (4.25) appears to already have this feature. I've never used it, but if you go to the Work window and highlight a WU, over on the left is the option to 'Abort Result' which deletes the unit from your cache and prevents it from being crunched.

Dig

---

> but for gods sake Man turn on your machine!

LOL, like I tell the users at work that I support "You have to meet it half way!"

---

<br><br><img src='http://www.boincsynergy.com/images/stats/1185sah.png'> <br>
Thanks to Tim (Captain Avatar) for my groovy Red Foxx avatar!

> I am confused, you do not run your computer and now you want BOINC to clean it
> up for you, jeeezzz just run the computer, one of your computers shows no WUs
> and the other shows one due the 12th and 21st.
>
>
> Check out BoincView it has lots of bells and whistles.
>
> http://boincview.amanheis.de/
>

Boinc can't seem to know what it has. I haven't used two different computers. I started on laptop then the hard drive crashed. I used knoppix and ran boinc for a while. When I got the new hard drive I reinstalled everything. The boinc manager has all the fields closed evrytime you open it. If they won't give credit for the time spent working on a unit then don't make me spend the time on it. Well shoot I for some reason thought the reason for the distributed computing was to volunteer excess idle time to project, not force everyone to keep thier computers on all the time. Boinc can't even do a little comparison to help MANAGE some network comuting. Boinc setiathome has only doubled the time for a standard work unit. I could finish a workunit in 6hrs on this laptop now it takes 12. and the reason you don't see the other workunits on list is it looks like Boinc has no problem in deleting its records without notifying the clients.

---

> Boinc can't seem to know what it has. I haven't used two different computers.
> I started on laptop then the hard drive crashed. I used knoppix and ran
> boinc for a while. When I got the new hard drive I reinstalled everything.
> The boinc manager has all the fields closed evrytime you open it. If they
> won't give credit for the time spent working on a unit then don't make me
> spend the time on it. Well shoot I for some reason thought the reason for the
> distributed computing was to volunteer excess idle time to project, not force
> everyone to keep thier computers on all the time. Boinc can't even do a
> little comparison to help MANAGE some network comuting. Boinc setiathome has
> only doubled the time for a standard work unit. I could finish a workunit in
> 6hrs on this laptop now it takes 12. and the reason you don't see the other
> workunits on list is it looks like Boinc has no problem in deleting its
> records without notifying the clients.

Issues like this are being worked on. Changes to the way the the BOINC Daemon will manage the work queue are being worked on right now. But issues like this are of lower priority than the cross project GUI (for example).

Yes, you still do have to do some of the management of the work yourself. And yes, there are limitations to the current BOINC SOftware. But the changes and improvements occur with each new revision of the software.

---

> The boinc manager has all the fields closed evrytime you open it. If they
> won't give credit for the time spent working on a unit then don't make me
> spend the time on it. Well shoot I for some reason thought the reason for the
> distributed computing was to volunteer excess idle time to project, not force
> everyone to keep thier computers on all the time.

Yes, the goal is to use excess idle time.

If you have the default cache size (connect every "x" days) then you'll probably only get one work unit at a time, and since your average return time is just under 14 days, you really don't want more than one work unit at a time.

Given your 12 hours/WU number, it seems IOTTMCO that you'll need to run at least 36 hours in two weeks, or at least 2 1/2 hours per day to get through the tthree work units you currently have.

If you keep running with your current pattern, BOINC will realize that you aren't crunching a whole lot and throttle you back to one WU at a time -- or you can just set "connect every 'x' days" to something like 0.1 and your cache will still contain nearly 2 weeks of work.

---

> Yes, you still do have to do some of the management of the work yourself. And
> yes, there are limitations to the current BOINC SOftware. But the changes and
> improvements occur with each new revision of the software.

I think this is only a problem because his "connect every 'x' days" is higher than the default 0.1. Seems that he'd only have one work unit at a time, and given the idle time he has, he'd turn in one work unit just ahead of the deadline most of the time.

It is really only an issue because he's managed the "connect every" value.

I seem to remember a thread way back where someone kept raising this number to try and get more work -- and had it up to something like 100 days. This is the same problem.

---

> I am confused, you do not run your computer and now you want BOINC to clean it
> up for you, jeeezzz just run the computer....

SETI@home has always been billed to the public as a screensaver. Install it, forget it. Ordinary people don't want to be computer-process tinkerers any more than they want to be refrigerator tinkerers. They want their refrigerator to work by itself, as advertised.

This doesn't mean they're dumb or contemptible, it just means they've got other things to do on weekends.

We should cut the hardworking Berkeley folks some slack as they fix these problems. But the fact is, for nearly six years S@H has had far more than enough users to analyze all the available data 100% completely -- even with three- or four-times redundancy to catch every (rare) bad result. Beyond that, the excess users are just wasting electricity.

In fact, that's partly why BOINC was created -- to divert the (huge) wasted excess of people into other projects. So, we shouldn't be telling the guy he needs to run SETI@home 24/7.

Alan MacRobert

Alan I am confused by your post.

I think the days of set it and forget it are over, BOINC was created to include many projects and many different types of users...

To down load a WU and then shut tour computer down, and then complain that the WU expired, is a Dooh! type of problem. We should be telling the guy to turn on his computer and if he wants to run it once and awhile then he should not run any BOINC project...

Keep in mind The programs were created for unused CPU time and dont have that if
the CPU ISN't Running.....

---

>
> Alan I am confused by your post.
>
> I think the days of set it and forget it are over, BOINC was created to
> include many projects and many different types of users...
>
> To down load a WU and then shut tour computer down, and then complain that the
> WU expired, is a Dooh! type of problem. We should be telling the guy to turn
> on his computer and if he wants to run it once and awhile then he should not
> run any BOINC project...
>
> Keep in mind The programs were created for unused CPU time and dont have that
> if
> the CPU ISN't Running.....
>
>
I tend to agree. Seti was never really intended for laptop and their relatively short usage time. As I understand it the original concept, which I think still hold true, was to tap into the resource of the millions of desktop that were left ruining idle and doing nothing in offices around the world but displaying bouncing balls. It was intended as a install and forget screen saver.

Boinc as now outgrown this original concept, and does require a little more maintenance. But, those millions of computers are still out there and a dedicated IT person can still relatively easily donate all those wasted CPU cycle to science.

With todays OS, the average person, can run it in background, while surfing the net, without having a noticeable effect on computer performance. Being one of the crazy people, with my P2P constantly downloading something, I use 'run always' mode, since the computer itself rarely, if ever, gets turned off.

---

Boinc V7.2.42
Win7 i5 3.33G 4GB, GTX470

> I hadn't had a computer on as much recently and noticed I wasn't getting any
> credit. Ijust noticed the results were past the time. If I am not going to
> get credit for the time I volunteer for crunching it would be nice if the
> client would go ahead and throw out the results since they are useless.

Geez there was a lot of crap in the responses to your comment.

I was under the impression that BOINC would remove wu's that would not be completed before the deadline. That WAS/IS one of the goals of BOINC - to manage the WU's for you and to not waste cpu cycles. Why on earth it has not yet been implemeted I do not know. With various projects having different deadline periods (1 to 7 to 14 days) it can be quite easy to have more work in you cache than can be completed in time, especially if you turn off your computer for any period of time. Maybe it's there and is not working correctly. A bug report or feature request is required.

Live long and crunch!

---

Paul
(S@H1 8888)
And proud of it!

No Bug Paul...

---

> I was under the impression that BOINC would remove wu's that would not be
> completed before the deadline. That WAS/IS one of the goals of BOINC - to
> manage the WU's for you and to not waste cpu cycles. Why on earth it has not
> yet been implemeted I do not know. With various projects having different
> deadline periods (1 to 7 to 14 days) it can be quite easy to have more work in
> you cache than can be completed in time, especially if you turn off your
> computer for any period of time. Maybe it's there and is not working
> correctly. A bug report or feature request is required.

I don't think it's as much a bug as just a question of some folks being overzealous.

The default connection interval is 0.1 days -- basically, this will give you one work unit.

On my workstation, running 16 hours/day, and processing SETI/LHC/Einstein 50/25/25, at 0.1 it picks up new work just a little before the current WU finishes.

I have to raise it to something over 1 before it grabs more than a couple of WUs.

... but the scheduler knows the ratio between projects and that I'm up 16 hours/day.

If a new user sets "connect every..." to 10 and hasn't crunched work, the scheduler will assume 24 hours -- and let the user have too much work.

BOINC assumes 24/7 to start, and if someone really works 10 hour days and 5 day weeks, it'll figure that out.

Note that late work units can contribute to a quorum and get credit, it's just not the best idea to plan on that.

... and the limit on "connect every 'x' days" should probably be closer to 3 than 10.

---

> ... and the limit on "connect every 'x' days" should probably be closer to 3
> than 10.

No thanks.
4 days worth of work is just right for me.

---

Grant
Darwin NT

> I was under the impression that BOINC would remove wu's that would not be
> completed before the deadline.

That has never been an option mentioned for development AFAIK.

BOINC will adjust the amount of work it downloads based on your systems up time & the time it receives to crunch work. But it does take time to do that.
Making it impossbile for people to initially download more work than they might be able to handle would hugely inconvenience 1,000s more that are able to manage their workload effectively.

---

Grant
Darwin NT

>
> > ... and the limit on "connect every 'x' days" should probably be closer
> to 3
> > than 10.
>
> No thanks.
> 4 days worth of work is just right for me.

4 is 1 away from 3, 4 is 6 away from 10. 4 is closer to 3 than it is to 10.

---

> 4 is 1 away from 3, 4 is 6 away from 10. 4 is closer to 3 than it is to 10.
>
There is logic in your words