I got your client files, thanks.
Unfortunately I cannot reproduce the problem, nor your environment fully. The closest qd.exe I have to your version is the one released 21 December 2008 (fr 071), and it shows the points & PPH as expected:
Code: Select all
$ wine ./qd.exe -n ./qdinfo.dat -iaf ./gpu2-p5902/
qd released 21 December 2008 (fr 071); qd info 8 March 2009 (update-qd.pl)
** NOTICE: This version of "qd" is out of date (info file is fr 073). **
qd executed Tue Mar 10 19:52:08 CET 2009 (Tue Mar 10 18:52:08 UTC 2009)
Queue version 6.00
Current index: 9
[...]
Index 9: folding now 1680.00 pts (295.634 pt/hr) 16.9 X min speed; 78% complete
server: 171.64.122.70:8080; project: 5902
Folding: run 11, clone 271, generation 0; benchmark 0; misc: 500, 200
issue: Tue Mar 10 07:05:18 2009; begin: Tue Mar 10 07:05:07 2009
expect: Tue Mar 10 12:46:04 2009; due: Sat Mar 14 07:05:07 2009 (4 days)
preferred: Fri Mar 13 07:05:07 2009 (3 days)
core URL: http://www.stanford.edu/~pande/Win32/x86/NVIDIA/G80/Core_14.fah (V1.24)
CPU: 1,687 Pentium II/III; OS: 1,8 WinXP
tag: P5902R11C271G0
flops: 1064567259 (1064.567259 megaflops)
memory: 1024 MB; gpu memory: 258 MB
assignment info (le): Tue Mar 10 07:05:18 2009; BA118227
CS: 171.65.103.100; P limit: 524286976
user: Shadowtester; team: 10688; ID: 8B66702BF7251B4F; mach ID: 3
work/wudata_09.dat file size: 65280; WU type: Folding@Home
The only change to qd (fr 071) between December 21 and December 25 was an update to the project data:
Code: Select all
[2008-12-25 02:00:11] New project : 4447 new credit*100: 22500
[2008-12-25 02:00:11] New preferred deadline for project : 4447 new preferred deadline: 3715200
The
client experiencing the same problem on my FCI server uses the most recent functional revision of qd, so the changes to the code between the functional revision your using and the most recent can't be the issue:
Code: Select all
qd : 8 March 2009 (fr 073)
qdinfo.dat : 8 March 2009 (update-qd.pl)
I spent most of yesterday night casing ghosts in the qd source code, terribly on the wrong track of what was causing this unexpected behavior. Just now I realized that qd is not at fault here, it truly doesn't know about p5902 in its build in project data table. p5902 was released long after qd fr 071, so that data lives only in qdinfo.dat. The qdinfo.dat your FCI client is using was released 8 March 2009, so you'd think that it actually contains p5902 which was added that day.
It just so happens that on Sun Mar 8 03:27:01 2009 CET I released qd-tools v2.3.7 containing the new qd fr 073 and recent builds of xyz2pdb for all platforms (first time that FreeBSD, OpenBSD, Mac OS X/PPC, Mac OS X/x86 and Mac OS X/Universal binaries are available), only 33 minutes before p5902 was added to qdinfo.dat on 2009-03-08 04:00:13 CET.
So now there are two version of qdinfo.dat using the date (da) 8 March 2009. The only difference is the point table generation time (pg):
Code: Select all
# qdinfo.dat 8 March 2009 (2009-03-08 03:27:01)
$ grep ^pg qd-data/qdinfo.dat
pg 1145F13D
# qdinfo.dat 8 March 2009 (2009-03-08 04:00:13)
$ grep ^pg ~/.fci/qdinfo.dat
pg 1145E762
The pg value is an epoch, and the difference between the two is 289796413 - 289793890 = 2523 seconds, or 42.05000000 minutes. Sounds about right:
Code: Select all
perl -e 'print scalar localtime (hex("0x1145E762") + 946684800), "\n"; print scalar localtime (hex("0x1145F13D") + 946684800), "\n";'
Sun Mar 8 03:18:10 2009
Sun Mar 8 04:00:13 2009
The problem here is that FCI client is not smart enough to see that qdinfo.dat released 8 March 2009 (pg 1145F13D) on your FCI server is newer than its local copy of qdinfo.dat released 8 March 2009 (pg 1145E762):
Code: Select all
Upload URL: http://fci.fatalerrorgroup.com/index.pl
Verifying access to URL ... Success!
Updating qd files.
Retrieving URL: http://fci.fatalerrorgroup.com/qd-data/qdinfo.dat ... Success
Reading file from disc: /home/bas/.fci/qdinfo.dat ... Done.
Local version: 2009-03-08
Fetched version: 2009-03-08
Local functional revision: 071
Fetched functional revision: 073
Versions are the same, no update of qdinfo.dat necessary.
Not updating qd binary, use --update-qd to also update the binary.
The binary will only be updated if there is a more recent functional revision.
Finished updating qd files.
I'll build some more intelligence into fci-client.pl before I release fci-1.3, in the mean time you can work around this problem by downloading the most recent qd binary and/or qdinfo.dat manually.