| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 3
|
|
| Author |
|
|
WilhelmGGW
Advanced Cruncher Joined: Nov 12, 2005 Post Count: 52 Status: Offline Project Badges:
|
My computer sometimes goes for a few days unattended -- turned on and connected to the Internet, crunching away on work units as fast as it can. I am thinking of signing up to do beta testing, but I'm reluctant to do that if faulty beta test units might occasionally seize up my crunching, awaiting my user input.
Can someone tell me how this works? Do I have reason for pause, or not? Thanks. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Things can go wrong. If they do, it is useful to WCG to get reports about them, as well as the question of interruption to your crunching.
Only sign up for beta testing if you want to actively help. Also, you can set up a separate device profile with beta testing enabled - this way, if you have multiple computers you can restrict beta testing to the one computer that you use primarily. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I'll toss in my own 2 cents. Beta Testers should be unflappable with a phlegmatic tolerant attitude toward errors. If the test program makes your computer go wonky, just shrug and send in a report about what you saw.
There are a number of people who ENJOY ( ) spending their time demonstrating their superiority to poor fallible computers, so don't feel pressured to become a Beta Tester. The idea is to have fun and feel good about yourself.Lawrence |
||
|
|
|