I have quit answering for all of the Boinc projects because of the group above. There's no fun in answering to forums anymore with these people around. And don't expect you can go against them. For they know better than everyone above and beyond. And they will always know of a way to make you look bad. As they will in the posts beyond to make me look bad. :)
Jord,
I'm sorry I've just now noticed and read your post, I was a little busy trying to help with things for Gray here and JP, over in Bug Reports where Stick had asked me to take a stab.
Knowledge and experience are at a premium on these boards, especially with Gary MIA for this week, and we can ill afford to lose your help. I hope you'll reconsider your decision to quit. Hey, I just don the teflon suit, act the diplomat occasionally, and muddle through. I don't take offense where none is intended (that's the fool's game), nor even when offense IS intentional, if I can side-step it or ignore it - life's too short as it is.
Respects,
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
They weren't reported if they stayed in the queue. Might take some time until BOINC recognizes they were aborted, check again when the current Einstein@Home workunit completes and is uploaded and reported. If they're still in the queue afer that then its a problem.
Walt
Walt,
Thanks for checking over these boards. It's good to know that when some of us newer, less knowledgable helpers get in over our heads, there is a higher force to which we can appeal.
Respects,
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
Yes it's true. When some alcoholic (read Ageless) falls down in a drunken stupor and starts spouting off orders to you, do not pity him, instead kick-roll him into the gutter and move on. Nothing to see here. PLONK!
Yes it's true. When some alcoholic falls down in a drunken stupor and starts spouting off orders to you, do not pity him, instead kick-roll him into the gutter and move on. Nothing to see here.
Good sense of humor, Misfit, although I didn't hear him slur his speech :) I do, in my heart of hearts, believe that everyone has something worthwhile to contribute, so since your sense of humor may be better than a 'dour' one, perhaps you can convince your cohorts to strengthen their grievance by resuming the crunching (the thing that sort of brought us all together here, wasn't it?)...
Saying that someone's “part of the loony faction” is, speaking of history, the very kind of thing that kept Newton from expressing some deep revelations (for that time), and so I believe this proverb: 'Kindly spoken words can heal; cruel words can wound as deeply as any sword.'
As for my sense of humor, just the other day, I walked into a bar and a lady said to me, “Oh, you're a hunk.” I was so offended, I said, “Is that all I am to you – just a rock hard package of strength and power?”
Seriously, though, I started out with nothing, and I still have most of it! :)
No, really seriously, PlanetQuest is awesome – happy crunching, Misfit!
The WUs, aborted and processed, will be reported and cleared from manager in chronological order, earliest deadline first, so if you aborted the newer WUs, they will have to wait until older ones are processed - that's why I suggested dumping the older ones.
Respects,
Michael
Great ! Just for the record, I have aborted all WUs deadlined 30/10 apart from the one I am working on at present (well it's 60%, so seems a pity to abort at this point). From what you say, as all other functional WUs are deadlined 31/10, the aborted ones should be removed in the next couple of hours, Climate@home should have a chance and the pressure is off - I have 2 days off from work (Wed/Thurs) so can enjoy them !! I'll let you know if all goes as per spec around 8 hours hence.
Gray
Right done the work unit and, yes, you are quite correct - once that was done the aborted WUs became removeable, although this did require some "nudging" by hitting the update button under the project tab repeatedly and also the retry communications, under commands tab. Anyhow eventually the aborted WUs were removed from the manager list, which looks "tidier" but I do think that the process should have been somewhat smoother ie: as soon as the finished WU was uploaded, BOINC should have been able to figure that the aborted WUs must be mentioned to the website and then cleared from the list automatically - not that I mind doing the update fandango etc, but as a managerBOINC should have been able to do this itself as soon as I give it internet access once any WU before them were removed from the queue. Hmmmm, not sure how clear all this is...
Gray
PS: there is still an issue doing a project such as Climate alongside Einstein as BOINC doesn't go from one to the other every hour (50% resources each) - I assume that BOINC looks at the deadlines for each, and as Climate is October 2006, Einstein gets first option every time ?
I should add that I DID specify one hour per project in preferences.
The WUs, aborted and processed, will be reported and cleared from manager in chronological order, earliest deadline first, so if you aborted the newer WUs, they will have to wait until older ones are processed - that's why I suggested dumping the older ones.
Respects,
Michael
Great ! Just for the record, I have aborted all WUs deadlined 30/10 apart from the one I am working on at present (well it's 60%, so seems a pity to abort at this point). From what you say, as all other functional WUs are deadlined 31/10, the aborted ones should be removed in the next couple of hours, Climate@home should have a chance and the pressure is off - I have 2 days off from work (Wed/Thurs) so can enjoy them !! I'll let you know if all goes as per spec around 8 hours hence.
Gray
Right done the work unit and, yes, you are quite correct - once that was done the aborted WUs became removeable, although this did require some "nudging" by hitting the update button under the project tab repeatedly and also the retry communications, under commands tab. Anyhow eventually the aborted WUs were removed from the manager list, which looks "tidier" but I do think that the process should have been somewhat smoother ie: as soon as the finished WU was uploaded, BOINC should have been able to figure that the aborted WUs must be mentioned to the website and then cleared from the list automatically - not that I mind doing the update fandango etc, but as a managerBOINC should have been able to do this itself as soon as I give it internet access once any WU before them were removed from the queue. Hmmmm, not sure how clear all this is...
Gray
PS: there is still an issue doing a project such as Climate alongside Einstein as BOINC doesn't go from one to the other every hour (50% resources each) - I assume that BOINC looks at the deadlines for each, and as Climate is October 2006, Einstein gets first option every time ?
I should add that I DID specify one hour per project in preferences.
The next step is to try out Rosetta@home - the work units are smallish and so should see if the swopping between clients happens this time. Also I reckon the medicos could do with some support :)
The WUs, aborted and processed, will be reported and cleared from manager in chronological order, earliest deadline first, so if you aborted the newer WUs, they will have to wait until older ones are processed - that's why I suggested dumping the older ones.
Respects,
Michael
Great ! Just for the record, I have aborted all WUs deadlined 30/10 apart from the one I am working on at present (well it's 60%, so seems a pity to abort at this point). From what you say, as all other functional WUs are deadlined 31/10, the aborted ones should be removed in the next couple of hours, Climate@home should have a chance and the pressure is off - I have 2 days off from work (Wed/Thurs) so can enjoy them !! I'll let you know if all goes as per spec around 8 hours hence.
Gray
Right done the work unit and, yes, you are quite correct - once that was done the aborted WUs became removeable, although this did require some "nudging" by hitting the update button under the project tab repeatedly and also the retry communications, under commands tab. Anyhow eventually the aborted WUs were removed from the manager list, which looks "tidier" but I do think that the process should have been somewhat smoother ie: as soon as the finished WU was uploaded, BOINC should have been able to figure that the aborted WUs must be mentioned to the website and then cleared from the list automatically - not that I mind doing the update fandango etc, but as a managerBOINC should have been able to do this itself as soon as I give it internet access once any WU before them were removed from the queue. Hmmmm, not sure how clear all this is...
Gray
PS: there is still an issue doing a project such as Climate alongside Einstein as BOINC doesn't go from one to the other every hour (50% resources each) - I assume that BOINC looks at the deadlines for each, and as Climate is October 2006, Einstein gets first option every time ?
I should add that I DID specify one hour per project in preferences.
The next step is to try out Rosetta@home - the work units are smallish and so should see if the swopping between clients happens this time. Also I reckon the medicos could do with some support :)
One thing I did notice when hooking up with Rosetta via the BOINC wizard is that at the end of the process I was informed that the attempt to join Rosetta project had failed, but then a couple of seconds later Rosetta appeared in my list of projects anyway, and the downloads began - something a little strange there...
There seems to be a problem with 5.2.1 reporting completed WUs. I've only now noticed this behavior because I routinely "Update" shortly after a WU is processed. In the interest of testing, I deliberately left the most recently completed WU to report on Boinc's own terms, but it had been over 7 hours, well past my "connect every..." value, which is set to 0.27 days. I exited Boinc through the system tray, and upon starting it again a short time later, the WU was successfully reported. I have the manager set to "Run based on preferences" and "Network activity always available", cable internet.
I shall allow the next WU at least 10 hours to be reported before further interference, to verify what I suspect is a bug.
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
There seems to be a problem with 5.2.1 reporting completed WUs. I've only now noticed this behavior because I routinely "Update" shortly after a WU is processed. In the interest of testing, I deliberately left the most recently completed WU to report on Boinc's own terms, but it had been over 7 hours, well past my "connect every..." value, which is set to 0.27 days. I exited Boinc through the system tray, and upon starting it again a short time later, the WU was successfully reported. I have the manager set to "Run based on preferences" and "Network activity always available", cable internet.
I shall allow the next WU at least 10 hours to be reported before further interference, to verify what I suspect is a bug.
Michael
Hello Michael - just a reminder that I am using 5.2.2 - for the record as it were.
Other than what I have mentioned previously I have had no errors and am crunching away happily, while I read a new book (Science of the Discworld - the first in the series)
PS: there is still an issue doing a project such as Climate alongside Einstein as BOINC doesn't go from one to the other every hour (50% resources each) - I assume that BOINC looks at the deadlines for each, and as Climate is October 2006, Einstein gets first option every time ?
I should add that I DID specify one hour per project in preferences.
The next step is to try out Rosetta@home - the work units are smallish and so should see if the swopping between clients happens this time. Also I reckon the medicos could do with some support :)
One thing I did notice when hooking up with Rosetta via the BOINC wizard is that at the end of the process I was informed that the attempt to join Rosetta project had failed, but then a couple of seconds later Rosetta appeared in my list of projects anyway, and the downloads began - something a little strange there...
Gray
Gray,
Things are improving nicely for you!
As you can see from my open post (below), there may be an issue with 5.2.x not reporting completed WUs automatically. I recall reading something pertaining to this issue, but if I recall correctly, they concluded that Einstein was one project that was immune to that glitch. I'll have a better look at things with the currently processing WU, and should have an answer, one way or the other, by tomorrow morning, about 17 hours away. If you think or it, please check to see if it works on 5.2.2.
Re: Climate and/or Rosetta getting proper share time, it usually takes a few days for the manager to settle into it's routine, and forcing a project to crunch seems to confuse manager, and delay it's settling-in period. Since Climate has a year deadline, and Rosetta's is 28 days (I believe), you can comfortably allow manager time to sort things out without jeopardizing any deadlines.
Further note on swapping: Make sure that you set "Run based on preferences" instead of "Run always" in the "Commands" drop-down, or your carefully set up prefs may be overridden.
Regards,
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
RE: I have quit answering
)
Jord,
I'm sorry I've just now noticed and read your post, I was a little busy trying to help with things for Gray here and JP, over in Bug Reports where Stick had asked me to take a stab.
Knowledge and experience are at a premium on these boards, especially with Gary MIA for this week, and we can ill afford to lose your help. I hope you'll reconsider your decision to quit. Hey, I just don the teflon suit, act the diplomat occasionally, and muddle through. I don't take offense where none is intended (that's the fool's game), nor even when offense IS intentional, if I can side-step it or ignore it - life's too short as it is.
Respects,
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
RE: They weren't reported
)
Walt,
Thanks for checking over these boards. It's good to know that when some of us newer, less knowledgable helpers get in over our heads, there is a higher force to which we can appeal.
Respects,
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
Yes it's true. When some
)
Yes it's true. When some alcoholic (read Ageless) falls down in a drunken stupor and starts spouting off orders to you, do not pity him, instead kick-roll him into the gutter and move on. Nothing to see here. PLONK!
me-[at]-rescam.org
RE: Yes it's true. When
)
Good sense of humor, Misfit, although I didn't hear him slur his speech :) I do, in my heart of hearts, believe that everyone has something worthwhile to contribute, so since your sense of humor may be better than a 'dour' one, perhaps you can convince your cohorts to strengthen their grievance by resuming the crunching (the thing that sort of brought us all together here, wasn't it?)...
Saying that someone's “part of the loony faction” is, speaking of history, the very kind of thing that kept Newton from expressing some deep revelations (for that time), and so I believe this proverb: 'Kindly spoken words can heal; cruel words can wound as deeply as any sword.'
As for my sense of humor, just the other day, I walked into a bar and a lady said to me, “Oh, you're a hunk.” I was so offended, I said, “Is that all I am to you – just a rock hard package of strength and power?”
Seriously, though, I started out with nothing, and I still have most of it! :)
No, really seriously, PlanetQuest is awesome – happy crunching, Misfit!
RE: RE: Gray, The WUs,
)
Right done the work unit and, yes, you are quite correct - once that was done the aborted WUs became removeable, although this did require some "nudging" by hitting the update button under the project tab repeatedly and also the retry communications, under commands tab. Anyhow eventually the aborted WUs were removed from the manager list, which looks "tidier" but I do think that the process should have been somewhat smoother ie: as soon as the finished WU was uploaded, BOINC should have been able to figure that the aborted WUs must be mentioned to the website and then cleared from the list automatically - not that I mind doing the update fandango etc, but as a managerBOINC should have been able to do this itself as soon as I give it internet access once any WU before them were removed from the queue. Hmmmm, not sure how clear all this is...
Gray
PS: there is still an issue doing a project such as Climate alongside Einstein as BOINC doesn't go from one to the other every hour (50% resources each) - I assume that BOINC looks at the deadlines for each, and as Climate is October 2006, Einstein gets first option every time ?
I should add that I DID specify one hour per project in preferences.
RE: RE: RE: Gray, The
)
The next step is to try out Rosetta@home - the work units are smallish and so should see if the swopping between clients happens this time. Also I reckon the medicos could do with some support :)
Gray
RE: RE: RE: Gray, The
)
The next step is to try out Rosetta@home - the work units are smallish and so should see if the swopping between clients happens this time. Also I reckon the medicos could do with some support :)
One thing I did notice when hooking up with Rosetta via the BOINC wizard is that at the end of the process I was informed that the attempt to join Rosetta project had failed, but then a couple of seconds later Rosetta appeared in my list of projects anyway, and the downloads began - something a little strange there...
Gray
Gray
There seems to be a problem
)
There seems to be a problem with 5.2.1 reporting completed WUs. I've only now noticed this behavior because I routinely "Update" shortly after a WU is processed. In the interest of testing, I deliberately left the most recently completed WU to report on Boinc's own terms, but it had been over 7 hours, well past my "connect every..." value, which is set to 0.27 days. I exited Boinc through the system tray, and upon starting it again a short time later, the WU was successfully reported. I have the manager set to "Run based on preferences" and "Network activity always available", cable internet.
I shall allow the next WU at least 10 hours to be reported before further interference, to verify what I suspect is a bug.
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK
RE: There seems to be a
)
Hello Michael - just a reminder that I am using 5.2.2 - for the record as it were.
Other than what I have mentioned previously I have had no errors and am crunching away happily, while I read a new book (Science of the Discworld - the first in the series)
Gray
RE: PS: there is still an
)
Gray,
Things are improving nicely for you!
As you can see from my open post (below), there may be an issue with 5.2.x not reporting completed WUs automatically. I recall reading something pertaining to this issue, but if I recall correctly, they concluded that Einstein was one project that was immune to that glitch. I'll have a better look at things with the currently processing WU, and should have an answer, one way or the other, by tomorrow morning, about 17 hours away. If you think or it, please check to see if it works on 5.2.2.
Re: Climate and/or Rosetta getting proper share time, it usually takes a few days for the manager to settle into it's routine, and forcing a project to crunch seems to confuse manager, and delay it's settling-in period. Since Climate has a year deadline, and Rosetta's is 28 days (I believe), you can comfortably allow manager time to sort things out without jeopardizing any deadlines.
Further note on swapping: Make sure that you set "Run based on preferences" instead of "Run always" in the "Commands" drop-down, or your carefully set up prefs may be overridden.
Regards,
Michael
microcraft
"The arc of history is long, but it bends toward justice" - MLK