No credits granted |
| log in |
Message boards : SETI@home Enhanced : No credits granted
1 · 2 · Next
| Author | Message |
|---|---|
|
Hi, | |
| ID: 32557 · | |
|
Hello Hi, ____________ Thanks to Paul and Friends Please consider a Donation to the Seti Project | |
| ID: 32570 · | |
|
Hi all: Just finished task id: 3810119 work unit id: 1108615 This result took over 5.4 hours to complete: | |
| ID: 32984 · | |
Hi all: Just finished task id: 3810119 work unit id: 1108615 This result took over 5.4 hours to complete: Just looked at the server status page. The waiting to send has dropped by about 100,000 work unts. So my guess they did a forced cancel off all the SETI Multi-beam work units, so the astorpulse would start to run. | |
| ID: 33019 · | |
Just looked at the server status page. The waiting to send has dropped by about 100,000 work unts. So my guess they did a forced cancel off all the SETI Multi-beam work units, so the astorpulse would start to run. Thereby giving the proverbial finger to all the Mac users out there … ____________ | |
| ID: 33038 · | |
|
When I was speaking with Eric on the phone the number of WU's was about 117000 and had been for days...
____________ Thanks to Paul and Friends Please consider a Donation to the Seti Project | |
| ID: 33079 · | |
|
Odysseus Just looked at the server status page. The waiting to send has dropped by about 100,000 work unts. So my guess they did a forced cancel off all the SETI Multi-beam work units, so the astorpulse would start to run. ____________ Thanks to Paul and Friends Please consider a Donation to the Seti Project | |
| ID: 33100 · | |
I will bang on the desk Monday, again for the Mac Users... Dotsch has some test apps for AP... In the AP forum. Thanks—and sorry if I seem intemperate but the lack of warning had me irritated; my G4 at work, for example, will have needlessly wasted about a day of CPU time. How much trouble could it have been to issue an advisory to set the project to NNT, and stop issuing new work, a week or two in advance of cancelling the outstanding WUs outright? As for Dotsch’s Astropulse app, this G5 is running the PPC build as I write: it’s about 60% through its first task, which I estimate will run a little over 150 hours. | |
| ID: 33121 · | |
|
Thanks to the developers for granting credit on the cancelled WUs; that has greatly improved my poor old G4’s morale. ;) | |
| ID: 33244 · | |
|
I’ve just started crunching for this project again after a few months absence, but I don’t seem to be getting any credits. This message is typical of what happens: | |
| ID: 34019 · | |
|
Welcome Back I’ve just started crunching for this project again after a few months absence, but I don’t seem to be getting any credits. This message is typical of what happens: ____________ Thanks to Paul and Friends Please consider a Donation to the Seti Project | |
| ID: 34020 · | |
|
Thanks for the info! I haven’t received any credits for any workunits since rejoining though. The five returned so far are all redundant results, which seems unlucky: Welcome Back | |
| ID: 34021 · | |
|
I will tickle Eric to Kick the Validator Thanks for the info! I haven’t received any credits for any workunits since rejoining though. The five returned so far are all redundant results, which seems unlucky: ____________ Thanks to Paul and Friends Please consider a Donation to the Seti Project | |
| ID: 34025 · | |
Thanks for the info! I haven’t received any credits for any workunits since rejoining though. The five returned so far are all redundant results That difference in the status shown has been noted before, it just seems to be a cosmetic flaw. I note you have received credit for one since posting: 3940223 1147818 21 Jun 2008 16:01:46 UTC 26 Jun 2008 17:08:05 UTC Over Success Done 15,443.35 63.99 63.98 With over 5 days between the "Sent" and "Reported" times, I think Pappa's original analysis is right on target. The queue of over 70 WUs you have will probably make many more redundant before the host starts them, particularly since I judge you have a fairly small share of its time allocated to this project. That's not a criticism, you're contributing some CPU time and the project asks no more. If we've missed something and the host had actually spent some time working on any of those which the server aborted, that would indicate a server misconfiguration which should be corrected ASAP. Joe | |
| ID: 34029 · | |
|
Thanks for all the helpful messages! You’re right; only 9.09% of my CPU time is dedicated to this project. Interestingly, that doesn't seem to have the same effect on all the other projects I crunch for. Presumably this one has some very dedicated hosts which gobble up workunits as fast as they come out! Perhaps I should consider either increasing the allocation of time to this project or just concentrating on other projects. I shall ponder...
| |
| ID: 34031 · | |
Thanks for all the helpful messages! You’re right; only 9.09% of my CPU time is dedicated to this project. Interestingly, that doesn't seem to have the same effect on all the other projects I crunch for. Presumably this one has some very dedicated hosts which gobble up workunits as fast as they come out! Perhaps I should consider either increasing the allocation of time to this project or just concentrating on other projects. I shall ponder... Graham, Your machine seems to be communicating with SETI Beta servers at least once a day, and you are using BOINC 5.10.45 I would suggest that you set your connect interval in BOINC to 1 day or less. 0.25 would probably be as low as I would go, as a very low setting may cause other problems. Then set the "Maintain enough work for an additional:" setting to something like 2 or 3 days max. I see that you are (or have been) attached to about 20 projects. I also run > 10 projects on 2 single core PC's, although several of them are currently set to "No New Tasks", and others e.g. LHC, RALPH, SIMAP, rarely or infrequently have work. Keith. ____________ | |
| ID: 34032 · | |
I would suggest that you set your connect interval in BOINC to 1 day or less. 0.25 would probably be as low as I would go, as a very low setting may cause other problems. Then set the "Maintain enough work for an additional:" setting to something like 2 or 3 days max. Thanks; I’ve gone for 0.25 and 3 respectively. Will watch and see! I see that you are (or have been) attached to about 20 projects. I also run > 10 projects on 2 single core PC's, although several of them are currently set to "No New Tasks", and others e.g. LHC, RALPH, SIMAP, rarely or infrequently have work. Yes, I used to do work for about twenty projects. Nowadays I only have Macs (a dual core Intel that does most of the work, and a couple of G3s that occasionally manage to finish a workunit or two), so I just crunch for whichever projects support Macs. Thanks for your help. Graham | |
| ID: 34041 · | |
|
Hi, | |
| ID: 34580 · | |
|
Had a power outage this morning all well over here, After reading this post I reset Seti main on both hosts only received half of the WU back so it saved crunching to nothing. Still no AP4.35 though. I have not posted a list of completed WU as there has been so much discusion on AP4.35 for main. | |
| ID: 34581 · | |
|
application AstroPulse | |
| ID: 34631 · | |
Message boards :
SETI@home Enhanced :
No credits granted