F@H: new core!

[GLeeM]

FahCore_96.exe

p19** WUs from server *.113, points = 125

You need -advmethods flag and BigWU = yes to get these. Also need 512MB ram, maybe more in future. Peak Mem Usage shows 294,804K on the unit I'm doing! They are revising the client to allow opt in to receive these.

Called QMD - Quantum MD. It uses SSE2, and in future may be limited to CPUs that have this.

Fast dual channel DDR ram gives 50% increase over single channel.

Gives better ppd than the other BigWUs on my P4 Northwood and Xeons.

4 minutes 57 seconds on P4 3.0@3.3 w/1GB = 360 ppd (with one instance)

Two on HT gives little to no increase in ppd.

Fold 'em if you got the equipment.

 

[BlackMountainCow]

Hehe! Now that's some good news. Even bigger WUs!! Hope I get one of these soon to raise my ppd!

:beer::beer:

 

[natethegreat]

I'll take one to go please

 

[ProviaFan]

I'm doing a 600 pt Gromacs on my BigWUs rig right now, and haven't seen any of the new ones yet (no Fahcore_96.exe in my F@H folder), but will keep an eye out for the new kind of WU.

 

[InlineFive]

How do I force -advmethods with GUI on an A64? I have Big WUs enabled but I can't wait to land me one of these!

 

[ProviaFan]

Originally posted by: PorBleemo
How do I force -advmethods with GUI on an A64? I have Big WUs enabled but I can't wait to land me one of these!

Append it to the end of the line that points to the executable in the shortcut properties dialog (add a space and then -advmethods after the quote so it looks something like this):

"x:\program files\folding@home\fah.exe" -advmethods

 

[kb3edk]

Originally posted by: PorBleemo
How do I force -advmethods with GUI on an A64? I have Big WUs enabled but I can't wait to land me one of these!

What I do usually is put the flag in the Windows Start Menu.

Start -> Programs -> Folding@Home -> Folding@Home 5.03 -> *right click* Properties
Then for Target, something like:
"C:\Program Files\Folding@Home\winfah.exe" -advmethods

I put the flag right outside the quotes.

Don't know if this is the most elegant way, but it seems to work for me-

-Adam in Philly

 

[Sniderhouse]

Originally posted by: GLeeM
You need -advmethods flag and BigWU = yes to get these.

I have bigpackets=yes in my client.cfg file. Is that the same as BigWu=yes?

 

[InlineFive]

Originally posted by: ProviaFan

Originally posted by: PorBleemo
How do I force -advmethods with GUI on an A64? I have Big WUs enabled but I can't wait to land me one of these!

Append it to the end of the line that points to the executable in the shortcut properties dialog (add a space and then -advmethods after the quote so it looks something like this):

"x:\program files\folding@home\fah.exe" -advmethods

Excellent, I just appended that to my Startup shortcut. Thanks!

 

[Insidious]

I just found this thread.....

Glad to see "new blood" comming out. :thumbsup:

-Sid

PS: Sorry to be such a noob, but does an AXP Barton have SSE2?

 

[kb3edk]

Originally posted by: Insidious
I just found this thread.....

Glad to see "new blood" comming out. :thumbsup:

-Sid

PS: Sorry to be such a noob, but does an AXP Barton have SSE2?

Unfortunately it doesn't...

 

[GLeeM]

Originally posted by: Sniderhouse

Originally posted by: GLeeM
You need -advmethods flag and BigWU = yes to get these.

I have bigpackets=yes in my client.cfg file. Is that the same as BigWu=yes?

Yes it is Sniderhouse.

Sorry about my FaH slang.

@everyone

Sorry I forgot to add that this core saves checkpoints funny. It writes a checkpoint however often you selected in the config even if it just finished a "frame" a few seconds before.

Also, FAH LogStats has problems. So does EM monitor.

unitinfo.txt file does not get written to until WU finishes

 

[InlineFive]

Originally posted by: kb3edk

Originally posted by: Insidious
I just found this thread.....

Glad to see "new blood" comming out. :thumbsup:

-Sid

PS: Sorry to be such a noob, but does an AXP Barton have SSE2?

Unfortunately it doesn't...

A64s and P4s

 

[GLeeM]

Originally posted by: GLeeM
Sorry I forgot to add that this core saves checkpoints funny. It writes a checkpoint however often you selected in the config even if it just finished a "frame" a few seconds before.

Also, FAH LogStats has problems. So does EM monitor.

unitinfo.txt file does not get written to until WU finishes

New version of new core - "Version 1.01 (Mar 10, 2005)" (LOL, the programmer is as good with a calendar as I am)
Fixes the funny checkpointing. Sort of.

[07:04:25] Performing initial WF calculations
[07:04:25] Verifying checksum
[07:04:30] Completed 5 out of 2500 steps (0)
[07:18:59] Writing checkpoint files
[07:22:43] Completed 25 out of 2500 steps (1)
[07:34:30] Writing checkpoint files
[07:45:29] Completed 50 out of 2500 steps (2)
[07:50:03] Writing checkpoint files
[07:54:41] Writing checkpoint files
[07:54:47] WF converged, jumping to MD
[07:54:47] Verifying checksum
[07:56:00] Completed 500 out of 2500 steps (20)
[08:09:50] Writing checkpoint files
[08:24:43] Completed 525 out of 2500 steps (21)

The first 20 frames are reserved for "Performing initial WF calculations", not all are needed.
Then jumps to the 80 MD frames.
FAH LogStats doesn't work yet.
You'd think this would have been worked out in alpha or beta testing :roll:

Points per day are sweet though