Brief Overview Of F@h Beta Team Membership

[bruce]

• Purpose Of F@h Beta Team

The purpose of the beta team is to test projects and software that has undergone initial testing but isn't ready to be released. That means that your PRIMARY purpose will be to find and report problems, gathering enough information that Development can reproduce and fix those problems. If you primary purpose is to earn points for advancing science, then you're in the wrong place. although certainly you'll be doing that, too. It must be a secondary purpose for you.

Beta Team Members are commonly called Beta Testers (via their Avatar and/or Signature). They are a group of F@h Donors that help the Pande Group test out new Projects and new FahCores. There isn't any limit to the size of the Beta Team hence any active forum member with an appropriate background (details below) can apply for membership.

Note: Information learned through Beta Testing will be available to the public as a read-only Forum that they can browse and link to. However, Non-Beta Members will not be able to post in the Beta Forum.

Moreover, we cannot support you if you post elsewhere and you post is likely to be deleted.

[bruce]

• Relationship Between F@h Points & Beta Tester

YOU WILL NOT GET MORE POINTS WHILE WORKING ON A WU AS A BETA TESTER. It just won't happen because the points will be inline with the standard benchmarking policy. If Project A is in Beta Testing and is worth X points, if it goes public, it will continue to be worth X points. If you are wondering why Beta Testers have such high PPD or total points, it is most likely that they fold 24/7 on dedicated powerful system(s) for many year(s). Please note that as a Beta Tester, your probability of loosing F@h points increases since you will be dealing with new Servers, Projects, FahCores, etc. If you're interested in getting more F@h points, your best bet is to stay with public WUs.

Note 1: In case you're wondering how the WU flow is, below is a brief summary (it assumes that there are no problems anywhere).
Internal Testing (PG Members) -> Beta Project (Beta Testers) -> Limited Public Project (F@h Donors using -advmethods/advanced configuration) -> Completely Public (F@h Donors without any flags)

Note 2: Please note that when a new Beta Project is released for Beta Testing, only a limited quantity of WUs will be assigned. This is because if an issue arises, only a few machines will be effected by it. It also makes it easy to do the changes and roll out the solution so that other machines can verify it.

[bruce]

• Beta Forum's Visibility

Please note that as a registered forum member, you can only view the Beta Forum and can't make any posts in that Forum. You can track any Beta Project's progress since it entered Beta Stage until it reaches public. If you see an issue and want to offer any help/advice, please PM an Administrator/Moderator rather than making a new thread in the Public Forum since it might so unnoticed. Do note that while you are free to join the Beta Team, we prefer Donors who are regular. If you are a seasonal or an occasional tester, we prefer that you observe the Forum and offer help/advice via PM with an Administrator/Moderator.

[bruce]

• Applying For Beta Testing

The best candidates are those who have been folding for a while and have experience with this forum, F@h clients, FahCores, WUs, Servers, etc. Thus we will check your user history. Those who participate regularly in this forum either by asking questions or helping others tend to get priority over those who rarely post, simply because it shows your willingness to be an active member within the F@h Community. If you just joined this forum and/or have very few posts, your request post should distinguish you as to why you would be a good addition to the Beta Team. Please note that if you don't plan to stick with it, we would prefer that you do not join. If this is your first visit to our forum, you are not eligible for membership to the Beta Team.

Note: If the forum username here is different than the F@h username used by you to fold, please include your F@h username in your request post. Posting your team affiliation is not required and will be ignored.

[bruce]

• Role Of Beta Testers

Beta Testers are expected to report back any unusual behaviors, glitches, errors, FAHlog messages, performance issues, etc. in the Beta Forum. A true Beta Tester actually tries to break the software (but not violate the EULA), use it in many scenarios, system configurations, and tries all combinations of settings, switches, clients, etc. They then have to try and figure out exactly what they did to break it, and report their findings in a detailed manner. Thus providing detailed feedback is very important during Beta Testing. Moreover, Beta Testers must have a fairly good understanding of computers and their inner workings so they know how to fix something when/if it breaks during Beta Testing. They accept the risk of running into an occasional problem, and will be tolerant of those problems. By posting your request to join, you have indicated that you have accepted these conditions of membership. (In your request, please state that you understand and accept them.) This is a brief overview but can learn more as you read the posts in the Beta Forum starting with Beta Team - Rules Of Engagement, provided you have been accepted.

Note: A quick recap of what Beta Testers do:
A) They test work units from new Beta Projects
B) They test new beta versions of FahCores
They don't test new F@h Clients. That is handled separately and generally done as an Open Public Beta: Forum

[bruce]

• Methodology Of Beta Testing

When F@h is running on an overclocked system, you may find that the settings you thought were stable, may need to be tweaked further. The reason is that F@h uses optimizations which pushes the system a bit harder than most other burn-in tests. Unfortunately, some WUs give errors that look similar to an unstable overclock. Hence we expect you to distinguish between the two possibilities by switching back to stock settings, and retesting the WU to eliminate overclocking as the possible cause (The Pande Group only tests on stock systems, so they cannot find or fix problems associated with overclocking).

As a Beta Tester, please do not run Beta WUs on any computer that can't tolerate even the slightest instability or problem. You can use any computer for which you have permission to fold on, as stated in the EULA. We do ask that you monitor its progress closely and report any strange event(s) that might need fixing. You can select which computers get Beta WUs and which will continue to be assigned Public WUs. Do not fold Beta WUs on system(s) with which you do not have frequent access to or cannot monitor carefully.

[bruce]

• A Word Of Advice

If you don't understand anything you read in this thread, please ask. There are some very important statements here, and if you miss them, you may not be accepted as a Beta Tester. If you want to test future clients, posting here will not help because that is not covered in Beta Team Testing. If you want to test newly minted, possibly less-stable WUs with any of the F@h Clients on the download pages, then do post here. Please include a comment in your request stating that you have read and agreed to the above mentioned guidelines. Request posts without this comment will not be eligible for the Beta Team Membership.
Credits: Thanks to PantherX and 7im who were very helpful in reorganizing the information that had been developed over the years.
========================================================================================================================================
f=70&t=20755

[aetch]

A true Beta Tester actually tries to break the software (but not violate the EULA), use it in many scenarios, system configurations, and tries all combinations of settings, switches, clients, etc.

I've been thinking about applying to become a beta tester for some time so I've been reading the "manuals" on what's required for it and whether I "have" what it takes.

The above quote confuses me me a bit. Can anyone shed light on exactly what this means in relation to work units.
My limited understanding of the work units is that once assigned to a gpu or cpu they cannot be freely moved to another system and are rather fragile to changes or interruptions you make in your current system.

I think it's more likely to refer to the testing of cores.

[toTOW]

It means that you must not start to install or to use the client on machines you don't have the written permission ... and also that beta testing doesn't allow you to modify how the client and core works ...

Basically, you don't have to worry about this unless you have some weird ideas in mind ... you don't have to change much your habits when you become a beta tester, but you have to pay more attention about what happens while you're running something in beta ...

[aetch]

Okay? I guess that answers the bit about the eula, but that wasn't what I was asking about.

A true Beta Tester actually tries to break the software, use it in many scenarios, system configurations, and tries all combinations of settings, switches, clients, etc.

What was meant by "breaking the software"?
How am I being expected to test work units "in many scenarios, system configurations, and tries all combinations of settings, switches, clients"?
Am I being expected to chop and change my system mid test?
Am I being expected to move test work units between different systems?
Am I being expected stop and start work units with different settings/switches/options?

Or do I have this all wrong and this text merely applies to the cores?

[toTOW]

Just use it as you would usually ... to test a client or a core : start the client, stop it, pause/resume, reboot, launch a game without pausing the client ...

When testing WUs, it's basically checking that PPD is in your expected range and that you don't see an abnormal error rate (it might be easier to use HFM to track WUs) ...

[PaulTV]

Beta tester application:

Names:
Forum / Discord: PaulTV
Folding: Fahnatic (before that as PaulTV and ChopChop)

Main system:
CPU: AMD Ryzen 7 5800X
GPU: GA104 [GeForce RTX 3070] (ASUS Strix RTX 3070 OC, standard nVidia drivers)
OS: Windows 10
No stability or heat issues, nothing overclocked on default settings

Since I started folding as Fahnatic, I'm keeping track of all jobs being processed and their results, and store most logs. So if a job fails, I'll know pretty quickly, and I'll be able to analyse if something goes haywire.
I've read and agree to the guidelines in this thread, and the Rules of Engagement posted in the beta channel.

[aetch]

A true Beta Tester actually tries to break the software, use it in many scenarios, system configurations, and tries all combinations of settings, switches, clients, etc.

I think I've figured this, it relates to the testing of the cores alone, not the work units. It just doesn't say this explicitly.

There is a bit later, under "Methodology Of Beta Testing" on that makes it explicit that the systems that work units are run on should be pretty rock solid.


Anyway, I would like to apply to become a beta tester.

My folding name is the same as my forum name.
If anything will sink this application it might be my slight lack of forum participation but that's for you to decide.

Rig - see signature, just need to find a post which actually has my signature. Underclocked and power limited for reduced heat output and quieter running, steady as a rock.

To the best of my ability I have read and agreed the above guidelines.

It's in your hands now

[aetch]

Would someone mind giving us an update on this.
At the very least clean up the thread ready to capture the next poor unsuspecting beta applicant.

[toTOW]

It's usually bruce who handles the requests, be we haven't seen hi for while ...