As soon as I installed the FAH program, I created a team (227616) for my company. I input the team number into both the web controller and FAH-control app. After 9 completed work units, both the web controller and client app show my team number correctly, but web control says that neither I nor my team are earning any points! When I go to my points page (username=JFisher@Lightfleet), it says that I am folding for team 0 and not earning any points for me or my company. My team page shows zero credit for zero work units.
How do I fix this so I start to earn points? My company has another 100 computers or so, but I won't even try to convince higher-ups and co-workers to dedicate their idle CPU cycles to FAH if I can't show them that our electrons would be acknowledged. In fact, I am sticking my neck out by starting FAH on my own desktop during the holiday without asking. I have until Monday to fix the team-credit bug or else I'm abandoning ship and uninstalling
Please post the information mentioned in my signature.
I was able to find one WU that was credited, but I need additional information from your log to figure out what happened to the others.
Hi JFisher (team 227616),
Your WU (P9011 R462 C0 G129) was added to the stats database on 2014-12-25 17:05:43 for 2085.71 points of credit.
Checking the official stats, your team does show up with 1 WU so far. Other WU's do show up as under just your username and without the team assigned. The search is complicated a bit by the fact that the jfisher name has also been used by a few others over the years, and by the use of an email address as part of the username.
Why some of the WU's you have turned in do not show up in the stats for Team 227616 is not clear. Please post the log file from the F@H client here including the beginning section which shows the system information, and enough of the rest to show the configuration and the most recently saved version of the configuration. You can clip out the repetitive sections reporting progress if needed to keep the size within the posting limits for the forum. Additional information on posting your log can be found under this topic - viewtopic.php?f=61&t=26036.
iMac 2.8 i7 12 GB smp8, Mac Pro 2.8 quad 12 GB smp6
MacBook Pro 2.9 i7 8 GB smp3
Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
In the past, you could change a team number at any time, and the points on an already running work unit would be credited to the new team when uploaded. However, security has been increased over the years to deter cheating attempts. It is possible that when a team number is added after the work units has started processing, the points may not report to the new team number, but to the team number setting when the work unit was downloaded. I have not personally tested this in a while.
It appears that the first 9 WU were teeny things all assigned in the first hour that took the default team 0 despite my best attempt to create and set a new team from the get go (within minutes of installation).
The work units that *started* after that first hour have been going to my team. What confused me was that units 2-9 started after I set my team but before the hour was up, and they were not respecting my team choice (so I thought something was not set correctly on the server side). Evidently, there's a one hour delay between choosing a team and having new units linked to it.
If there's an improvement to be made, it is to guide each new installation into setting team ID *before* assigning any work units. That way, new participants will have a *much* more positive UX coming out of the gate. In my case, I couldn't see how to configure my client without first starting folding, and that's what got me locked into the default group for the first 9 work-units.
BTW, I entered JFisher@Lightfleet (no .com) as my user name, but it displays as just 'JFisher' on the score page. If the '@' is a problem in a username, then perhaps the registration form needs to reject it. I apologize for the confusion, but I knew that JFisher alone would not be unique.
Anyway, I don't care about an hour's worth of credit. I am happy as long as my config ends upright so I have something to show co-workers and managers when I try to sell them on further installations. I'll be trying a few today on SW test machines in the lab that spend most of their lives just blowing warm air.
Unfortunately kakao is scheduled to shutdown after the end of this year so you may want to "save as" that browser page so you can later use it for display example purposes when it's no longer available online.
Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
I was prompted for those things, but I don't think it was by the Windows installer. What I recall is that I had to start running before I could start configuring. I tried to use the FAH control program to configure before running, but it told me to start a client. I think it was when I launched the client that the web control page opened and I was prompted to create username, team and a key. The client was already chewing on its first WU while I did that.
The installer does ask for the username, team, and passkey BEFORE it starts processing. You erroneously assumed you should ignore those questions and start the client and the control app first. If you fail to respond to the installer questions, it does start processing for team 0.
If you query the official stats using the exact name jfisher@lightfleet you'll see that the 9 WUs you're asking about had errors and received 0 points.
I think my workflow was a little less direct than that. Thinking that I would start the controller app and use its config first, I told the installer not to start the client, so I didn't get those questions at that time. When I got the controller app started, I discovered that it wouldn't work without connecting to a running client. That's how I found myself starting the client before doing config. The client was up and running its first WU while I was using both web control and the fah_control app to configure user ID, team and passkey.
In other words, I misunderstood a checkbox in the installer and made a wrong turn.
As I said above, I'm not worried about a small credit loss. What concerned me is that after I did create my user and team, that info was not visible on the server side (even after starting new work units and passing the first hourly update), so I was looking for a way to change it there. Apparently, the server's left hand does not always know what the right hand is doing.
What I'll suggest is to guard against that wrong turn I made. You could clarify the text in the installer. Instead of simply saying "start folding now", the installer could let me know that I'll be configuring and starting. Better yet, take me through the opportunity for username, team & passkey before even letting me opt out of starting the client. In the client itself, starting cold could invoke the config sequence one time (before folding starts).
I hope my suggestions make F@H an even friendlier app.
Hardware configuration: Intel i7-4770K @ 4.5 GHz, 16 GB DDR3-2133 Corsair Vengence (black/red), EVGA GTX 760 @ 1200 MHz, on an Asus Maximus VI Hero MB (black/red), in a blacked out Antec P280 Tower, with a Xigmatek Night Hawk (black) HSF, Seasonic 760w Platinum (black case, sleeves, wires), 4 SilenX 120mm Case fans with silicon fan gaskets and silicon mounts (all black), a 512GB Samsung SSD (black), and a 2TB Black Western Digital HD (silver/black).
