SMX Folding Production, new Thread.
Here is how the SMX Project is faring for the week. Stats taken from Statsman's site this morning.
SM1 - 554.90 points/week, 15,044.80 points total
SM2 - 83.40 points/week, 17,057.70 points total
SM3 - 229.80 points/week, 8,417.86 points total
SM4 - 284.00 points/week, 15,107.20 points total
SM5 - 250.99 points/week, 6,662.43 points total
SM6 - 39.75 points/week, 8,635.55 points total
SM7 - 250.47 points/week, 9,236.08 points total
SM8 - 51.40 points/week, 9,516.23 points total
SM9 - 226.57 points/week, 8,780.60 points total
SM10 - 32.00 points/week, 4,586.91 points total
SM11 - 395.30 points/week, 15,521.50 points total
SM12 - 0.00 points/week, 2,787.86 points total
SM13 - 266.19 points/week, 7,196.62 points total
SM14 - 102.80 points/week, 5,547.71 points total
SM15 - 138.58 points/week, 3,405.08 points total
SM16 - 428.39 points/week, 5,948.25 points total
SM17 - 173.70 points/week, 3,614.47 points total
SM18 - 401.64 points/week, 4,068.55 points total
SM19 - 183.67 points/week, 1,245.91 points total
SM20 - still getting parts sent to it to build.
Man, it seems like several of the SMX rigs have hit a decline in points production this week, with a few notable exceptions. We have SM1 leading production with over 550 points this week, followed by SM 16 and SM18 with over 400 points this week each. Also up for honorable mention is SM11 at 395 points this week. Also, we have SM3, SM4, SM5, SM7, SM9 and SM13 all in the 200-300 point/week range, WTG guys.:)
Now we get to the more disappointing side of the SMX rigs.:( We have SM14, SM15, SM17 and SM19 weighing in at the 100-200 point/week production rate. Of these, SM15, SM17 and SM19 all have XP processors in them, which should be giving at least 300-400 points/week. What's up with these rigs guys?
Finally, we have SM2, SM6, SM8, and SM10 all with less than 100 points for the week, most a lot less. What is the matter with these rigs? It wouldn't hurt to post a little message up here if you are having problems with the rig or you are going to be down for some reason for a while. Hotrodsun was nice enough to post up his problems with SM8 and now he has it back up and folding; all we want is to be informed of any problems.
We have 1 rig totally out of action; SM12 has 0 points for the week.:mad2: :thumbsdow WTF is the matter, Film. Stanford is showing that SM12 hasn't turned in any work since 10/25/03. If you can't or don't want to keep the rig up and folding, then PM me, mmonnin Leonardo or TBonZ and we will arrange to get another host assigned for it.
Total production for the SMX project for the week was 4,001.03 points.
The total amount of points the SMX project has accumulated for the team is 152,381.31 points.
SM1 - 554.90 points/week, 15,044.80 points total
SM2 - 83.40 points/week, 17,057.70 points total
SM3 - 229.80 points/week, 8,417.86 points total
SM4 - 284.00 points/week, 15,107.20 points total
SM5 - 250.99 points/week, 6,662.43 points total
SM6 - 39.75 points/week, 8,635.55 points total
SM7 - 250.47 points/week, 9,236.08 points total
SM8 - 51.40 points/week, 9,516.23 points total
SM9 - 226.57 points/week, 8,780.60 points total
SM10 - 32.00 points/week, 4,586.91 points total
SM11 - 395.30 points/week, 15,521.50 points total
SM12 - 0.00 points/week, 2,787.86 points total
SM13 - 266.19 points/week, 7,196.62 points total
SM14 - 102.80 points/week, 5,547.71 points total
SM15 - 138.58 points/week, 3,405.08 points total
SM16 - 428.39 points/week, 5,948.25 points total
SM17 - 173.70 points/week, 3,614.47 points total
SM18 - 401.64 points/week, 4,068.55 points total
SM19 - 183.67 points/week, 1,245.91 points total
SM20 - still getting parts sent to it to build.
Man, it seems like several of the SMX rigs have hit a decline in points production this week, with a few notable exceptions. We have SM1 leading production with over 550 points this week, followed by SM 16 and SM18 with over 400 points this week each. Also up for honorable mention is SM11 at 395 points this week. Also, we have SM3, SM4, SM5, SM7, SM9 and SM13 all in the 200-300 point/week range, WTG guys.:)
Now we get to the more disappointing side of the SMX rigs.:( We have SM14, SM15, SM17 and SM19 weighing in at the 100-200 point/week production rate. Of these, SM15, SM17 and SM19 all have XP processors in them, which should be giving at least 300-400 points/week. What's up with these rigs guys?
Finally, we have SM2, SM6, SM8, and SM10 all with less than 100 points for the week, most a lot less. What is the matter with these rigs? It wouldn't hurt to post a little message up here if you are having problems with the rig or you are going to be down for some reason for a while. Hotrodsun was nice enough to post up his problems with SM8 and now he has it back up and folding; all we want is to be informed of any problems.
We have 1 rig totally out of action; SM12 has 0 points for the week.:mad2: :thumbsdow WTF is the matter, Film. Stanford is showing that SM12 hasn't turned in any work since 10/25/03. If you can't or don't want to keep the rig up and folding, then PM me, mmonnin Leonardo or TBonZ and we will arrange to get another host assigned for it.
Total production for the SMX project for the week was 4,001.03 points.
The total amount of points the SMX project has accumulated for the team is 152,381.31 points.
0
Comments
Good thing you noticed SM4 was missing a connection b/c SM1 is right on her tail.
Everyone Do it NOW!! I am not ****ing around here. Keep them running here people. EM3 makes it SOOOOO easy its rediculous. It only takes up 2 icon spaces in the system tray.
Any improvement in speed? Also, for an AXP, what flags should be used?
The biggest change in flags that I've seen with 4.0 is that you need to use a new flag, -forceSSE, to enable SSE usage on your XP procs. The -forceasm flag only gets 3DNow! assembly loops with the 4.0 client now. Your other flags such as -verbosity 9 and -advmethods still work the same way as on 3.25 clients.
Not one problem yet.
So in a nutshell, with 4.0, I want -forceSSE -forceasm -advmethods?
-verbosity X where x is a number 1-9 (integer values) determines the level of information written to the log file. The higher the number the more written. I always use 9. Default is like 6 or something.
All you need is the -forceSSE flag; you no longer need the -forceasm flag with the 4.0 beta and an XP proc. Also, unless they've changed the beta a little more, you need to enter it with the "SSE" capitalized as in -forceSSE, not -forcesse like mmonnin just posted. It seems to be case-sensitive.
The proc refuses to overclock stably on that board and and I also get a lot more tinkers (see reason here here because of a bug with the folding core and SM17's last 3 units have been tinkers (this is why its droped from ~240-250 a week to 170, it might drop even further). Its currently on frame 230 of a 400 frame tinker WU. I will NOT delete tinker wu's to get gromacs as I believe the intention of the F@H project was to get
Like I said above, I'll switch it to windows first thing on December 8th after my last exam and see what happens. But until then with no overclocking and a rain of SSE-less tinkers its going to be pretty hard to bump SM17 up at all, I've heard some grumbling about 4.00 and I'd rather not have a hung machine daily so I'll stick with what's stable for now.
NS
:rolleyes2
NS
I prefer 2k myself for folding only rigs as it uses less resources, but you can strip all the bloatware and excess crap off from running on XP and get pretty close.
Just one question, what is a Windows license? jk