Many thanks to krgm, now I know they're beta's I've found them as well (just wasn't looking hard enough last time)

Been watching my claimed stats and Trux (of course) was right my claimed credit has been slowly climbing and is now claiming up not down:

29/01/2006 13:05:47|SETI@home|CC calibration: 26.73 >> 29.27 (time: 6054s >> 5120s / Gfpops: 1.93 >> 4.18)
29/01/2006 14:45:50|SETI@home|CC calibration: 26.08 >> 28.56 (time: 5905s >> 4994s / Gfpops: 1.93 >> 4.18)
29/01/2006 16:37:25|SETI@home|CC calibration: 26.64 >> 29.65 (time: 6033s >> 5150s / Gfpops: 1.93 >> 4.25)
29/01/2006 18:36:15|SETI@home|CC calibration: 26.25 >> 29.61 (time: 5944s >> 5114s / Gfpops: 1.93 >> 4.30)

Cheers guys,

Happy crunching!

---

[edit] I see mention of tx 37 but cannot find the download on Trux's site, is tx37 a linux distro?[/edit]

Actually I have found both tx37 & tx39 on Trux's site, but they are both beta versions

---

Many, if not most, girls know how to stuff their faces and have those babies but they're not good with keeping records straight, etc. They always mess up insurance billing numbers, etc. and I always have to call them to straighten them up.

---

You could take a look at my celeron D 2.8 GHz. There have been more than 25 results processed.

That does not look too bad. It looks like it is a fresh host installation or maybe you reset the project? There are actually only WU's calculated with the calibrating client, no older ones, and there are just aound two dozens of them, all completed during a short period. In such case, when the <duration_correction_factor> is not yet well in place (like it is at new hosts) the initial calibration will certainly take much longer. However, in your case it looks pretty fine, and the credit is still rather consistently growing, so there is no reason yet for any concerns :)

Reagarding the

It looks like it is a fresh host installation or maybe you reset the project?"

well that what happens if you tell a (please really don't get me wrong here !!!) secretary to leave the computer on and ..well get ill for 2 weeks and guess what happens ....

Same goes for 3 other hosts crunching for my account ... told them to leave them on but ... guess what ... there off for about 1 1/2 weeks now and i dropped in RAC.

But no further comment on that :-(

---

Join BOINC United now!

You could take a look at my celeron D 2.8 GHz. There have been more than 25 results processed.

That does not look too bad. It looks like it is a fresh host installation or maybe you reset the project? There are actually only WU's calculated with the calibrating client, no older ones, and there are just around two dozens of them, all completed during a short period. In such case, when the <duration_correction_factor> is not yet well in place (as it is usual at new hosts) the initial calibration will certainly take much longer. However, in your case it looks pretty fine, and the credit is still rather consistently growing, so there is no reason yet for any concerns :)

---

trux
BOINC software
Freediving Team
Czech Republic

The program need to go through about 12 WUs before it will lock in on the correct calibration.

Give it time.

You could take a look at my celeron D 2.8 GHz. There have been more than 25 results processed.

http://setiathome.berkeley.edu/results.php?hostid=1904408&offset=60
http://setiathome.berkeley.edu/results.php?hostid=1904408&offset=80

It seems to increase after 20+ WUs processed but still is way of from 32 credits claimed.

Hope this helps.

---

Join BOINC United now!

The program need to go through about 12 WUs before it will lock in on the correct calibration.

Give it time.

---

Maybe someone (more intelligent than I) can explain this on the tx36 calibrating client, It appears to be adjusting my claimed credit downwards....can this be correct? Only noticed it happening last night. My other box running tx36 is fine....and correcting upwards per design (I believe)

You show only a single WU, so it is hard to tell. It is quite well possible that some units require the calibration downwards. Or it can also happen in the initial stage, after project reset, after manipulating the state xml file manually, or after running benchmarks. However, although in some cases it may take a dozen or two units before starting to calibrate correctly (what is well explained in the documentation), I did not yet see any machine where it would consistently underclaim. I cannot, though, exclude that such cases may happen. For example if the standard WU time estimation does not work on your machine, then it is likely the calibration won't work correctly either. Hard to tell what the reason could be - I would need to have such system for testing to tell you more.

One possible reason could be, if it accidentally happens that the machine crunches some units extremely slowly. There are some buggy units that can take up to many tens of hours to complete. Or the machine can stay looping during the night in some buggy program and therefor crunching much slower than usually. That will throw the calibration off its shoes, and it may take considerable time before it settles back to the right level (there is strong assimilarity in the calibrating algorithm). In such case, modifying the calibrating coeeficient <credit_correction_factor> in the client_state.xml may help. You can change it to whatever you want (and restart the client) - in the moment you edit it, the checksum will not match and the client will reset it to the initial value. However, if the <duration_correction_factor> is far off the base, you may need to correct it too (or reset the project).

---

trux
BOINC software
Freediving Team
Czech Republic

I'm not sure if this helps, but I noticed similar behavior when I started using the tx36 client. After a day and a half of use it started creeping back up. If you look at one of my hosts you'll see that at first it claimed credit in the teens but now it's claiming credits in the 31 range.

---

Double post. Sorry.

---

Join BOINC United now!

Maybe someone (more intelligent than I) can explain this on the tx36 calibrating client, It appears to be adjusting my claimed credit downwards....can this be correct? Only noticed it happening last night. My other box running tx36 is fine....and correcting upwards per design (I believe)


26/01/2006 20:16:15|SETI@home|Started upload of 25se04aa.16928.7953.854828.1.93_0_0
26/01/2006 20:16:19|SETI@home|CC calibration: 14.49 >> 8.91 (time: 3281s >> 1913s / Gfpops: 1.93 >> 2.35)
26/01/2006 20:16:19|SETI@home|CC calibration: 14.60 >> 8.98 (time: 3306s >> 1928s / Gfpops: 1.93 >> 2.35)
26/01/2006 20:16:19|SETI@home|CC calibration: 23.82 >> 14.65 (time: 5394s >> 3145s / Gfpops: 1.93 >> 2.35)
26/01/2006 20:16:19|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
26/01/2006 20:16:23|SETI@home|CC calibration: 14.41 >> 8.86 (time: 3262s >> 1902s / Gfpops: 1.93 >> 2.35)
26/01/2006 20:16:23|SETI@home|CC calibration: 14.45 >> 8.89 (time: 3273s >> 1909s / Gfpops: 1.93 >> 2.35)

It's probably something which can easily be explained and will probably turn out to be my fault anyway, but I am curious!!!

Second posting, posted on another thread with no comments.

[edit] I see mention of tx 37 but cannot find the download on Trux's site, is tx37 a linux distro?[/edit]

Hi Andy,

i can comfirm this behavior. Seen it on 2 systems i've tested it on first one was my A64 3200+ and second was a Celeron D 2.8 GHz.

So someone (more intelligent tahn "US") can explain it to us ? :D

---

Join BOINC United now!

Maybe someone (more intelligent than I) can explain this on the tx36 calibrating client, It appears to be adjusting my claimed credit downwards....can this be correct? Only noticed it happening last night. My other box running tx36 is fine....and correcting upwards per design (I believe)


26/01/2006 20:16:15|SETI@home|Started upload of 25se04aa.16928.7953.854828.1.93_0_0
26/01/2006 20:16:19|SETI@home|CC calibration: 14.49 >> 8.91 (time: 3281s >> 1913s / Gfpops: 1.93 >> 2.35)
26/01/2006 20:16:19|SETI@home|CC calibration: 14.60 >> 8.98 (time: 3306s >> 1928s / Gfpops: 1.93 >> 2.35)
26/01/2006 20:16:19|SETI@home|CC calibration: 23.82 >> 14.65 (time: 5394s >> 3145s / Gfpops: 1.93 >> 2.35)
26/01/2006 20:16:19|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
26/01/2006 20:16:23|SETI@home|CC calibration: 14.41 >> 8.86 (time: 3262s >> 1902s / Gfpops: 1.93 >> 2.35)
26/01/2006 20:16:23|SETI@home|CC calibration: 14.45 >> 8.89 (time: 3273s >> 1909s / Gfpops: 1.93 >> 2.35)

It's probably something which can easily be explained and will probably turn out to be my fault anyway, but I am curious!!!

Second posting, posted on another thread with no comments.

[edit] I see mention of tx 37 but cannot find the download on Trux's site, is tx37 a linux distro?[/edit]

---