WU run and run but never show progress in Win7 - AMD 970BE. Any ideas!
Al
/ 
Reply
Quote
The progress meter doesn't work. Here they tasks run for 2 or 3 hours then complete. I see you've aborted all your tasks so far. I suggest you just let them run until they either crash or complete normally. They may take more than 2 or 3 hours on slower computers.
/ Reply
Quote
TJMProject administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,369,107
RAC: 63
Without sensor the progress bar doesn't work.
/ Reply
Quote
i was wondering how some people got credit yet, since the sensors aren't out yet and my sample wus all get validated with 0.00 credit.
/ Reply
Quote
TJMProject administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,369,107
RAC: 63
That's because at some point validator had a bug, it granted credit for CPU time (very little) when it should just put 0.
There are also prototype sensors running.
/ Reply
Quote
thanks for your answers. i like it when a project (even in early stage) is properly monitored.
/ Reply
Quote
How about at least some symbolic credit for testing tasks without the sensor?
/ Reply
Quote
How about at least some symbolic credit for testing tasks without the sensor?
I don't think granting credit for work that produces no useful scientific output is a good idea. The milestone hunters (yes, that includes me!) will just put every available host on the project for no useful result - apart from another 100k milestone ;)
One could argue that running WUs to stress test the server is worthy though. Maybe 0.01 credit per WU, capped at 1 credit per user per day?
Al.
p.s. Let the flame war begin :)
/ Reply
Quote
Al is a poopy face. There. Stress test the post hiding and user banning mechanism.
/ Reply
Quote
How about at least some symbolic credit for testing tasks without the sensor?
I'm agree with you.
We are testing the app. What about a small reward for this?
____________
/ Reply
Quote
how about 5 credits per day.
so lot of people will stick around when the sensors are available...
/ Reply
Quote
TJMProject administrator
Project developer
Project tester
Send message
Joined: 16 Apr 11
Posts: 291
Credit: 1,369,107
RAC: 63
I'm not sure if granting credit for tasks finished without sensor is a good idea.
The first version of validator granted a min credit based on CPU time (eventually credits from running the sensor [6 credits/hour] were added to this min value), which resulted in ~0.01credits/WU on average.
It didn't take long until a couple of crunchers attached a lot of hosts and after just a few days some of them had more credits than krzyszp who had the first sensor running (there was only one back then, it was before I reset all the credits to 0).
About the sensor - we would like to build another batch soon, but we need to solve a couple of problems first:
1. Development - the sensor software was upgraded during last week, latest version which we call "v3" added new functions (user can switch backlight/buzzer on/off via project prefs), which made v2 sensor incompatible with the current app.
At this time I don't know if there will be any other major change. Upgrading the software is a piece of cake for someone familiar with AVRs (the sensor has programming port), however it might be problematic for others.
2. The cost of components - everything is much cheaper when bought in larger quantities, especially the PCB, processor and transformer. The problem is that we currently don't have enough money to build more than 10-20.
/ Reply
Quote
I agree that tasks finished without a detector should not be granted credits. And there should be a warning on this project's front page to tell people they must have a detector to earn credits. If you don't have such a warning you will make a lot of people unhappy and get bad publicity. You don't need that. If you want people to buy a detector then you need to be honest and open about it from the very beginning. It should be one of the very first things they read about this project.
/ Reply
Quote
Let me heare from you when you are ready to make all right!
Since then I remove this Project from my Computers.............
Much work no creditds.... thats wrong!
I LIKE your Project!
Regards!
Arne
Oe3ALS
/ Reply
Quote
Let me heare from you when you are ready to make all right!
Since then I remove this Project from my Computers.............
Much work no creditds.... thats wrong!
I LIKE your Project!
Regards!
Arne
Oe3ALS
It's obvious you crunch for the credit and not the science.
Me, I crunch for the science, not the credit.
/ Reply
Quote
I see your point there fiend, and have to say I agree with it but. When it comes to the final result, and im talking about other projects too, whatever an individuals personal motivations are for crunching for that project, it's all work that is useful to the project. A 'science minded' person's computer works just as hard as a 'goal minded' person's computer does.
I also understand the other persons disappointment as well, using all those cpu cycles for null work when it could have been used for something else.
Aaron
/ Reply
Quote
There are several good points in this thread.
I'd like to say though, people should not attach to a project just beacuse it is there. They should read more than just the front page. If there is no more to read, i would not attach. Signing is ok as that is a different matter.
And speaking of the front page, it needs a minor corection, the word using is used twice in a row. "using using"
/ Reply
Quote