I have been installing and uninstalling a number of different clients (about 4 different ones) to see if the benchmark results change (which they don't). Trux has been on for at least 2 days but I am not sure how many work units it has processed.
How do I do that? I thought that is was turned on by default when downloaded, so i have not tried to do anything else with the client.
That is correct, calibration is set to ON for all by default. When did you install truxoft? It may take more than 20 WU to settle into a "normal" calibrating mode.
Well actually for the linux client, it's NOT on by default. You need to add a truxoft_prefs.xml file to your boinc directory. The windows zip file on truxofts website has this xml file in it, but the linux version only contains the boinc executable.
Create a file truxoft_prefs.xml with the following contents:
all
You will then after 30 results see your credits calibrated.
How do I do that? I thought that is was turned on by default when downloaded, so i have not tried to do anything else with the client.
That is correct, calibration is set to ON for all by default. When did you install truxoft? It may take more than 20 WU to settle into a "normal" calibrating mode.
Well actually for the linux client, it's NOT on by default. You need to add a truxoft_prefs.xml file to your boinc directory. The windows zip file on truxofts website has this xml file in it, but the linux version only contains the boinc executable.
Create a file truxoft_prefs.xml with the following contents:
all
You will then after 30 results see your credits calibrated.
Thanks a heap for that. I am very new to Linux, still expect it to do things Windows does. Your help is very much appreciated.
Thanks a heap for that. I am very new to Linux, still expect it to do things Windows does. Your help is very much appreciated.
Your welcome. It's not actually a linux thing that's the problem. It's how the zip files on trux's site were prepared. The linux gzip just doesn't include the required XML file, while the windows zip does. Not including it in the linux gzip is just an oversight by the person preparing it, IMO, and it makes the statement on the website "calibration is turned on by default . . ." confusing.
MarkF, I would love my Opterons to be performing as well as yours. The difference must be Linux as you have Windows. I wish they would sort out the credit disparity between the two systems.
Thanks again.
I have to thank Akos for that, maybe he can work his magic on all the platforms eventually. (fingers crossed)
Boinc Studio provides the credit correction such that the 'Result duration correction factor' is normalized to 1.
Your welcome. It's not actually a linux thing that's the problem. It's how the zip files on trux's site were prepared. The linux gzip just doesn't include the required XML file, while the windows zip does. Not including it in the linux gzip is just an oversight by the person preparing it, IMO, and it makes the statement on the website "calibration is turned on by default . . ." confusing.
My thoughts exactly, sorry about the confusion folks...
differnet machine this time.
I also have been credited for the previous 3 that gave no credit.
P.S. the calibration file is working fine, thanks for that.
Yes it is sucessful, but click on Result ID and look at validate state. Invalid. It's sucessful because the quorum was fulfilled, yet your result was determined invalid. This is expected behaviour once in a while with the linux beta app. Notice: BETA app. They are trying to fix the intermittant invalids for the official linux app to come.
I have been installing and
)
I have been installing and uninstalling a number of different clients (about 4 different ones) to see if the benchmark results change (which they don't). Trux has been on for at least 2 days but I am not sure how many work units it has processed.
RE: RE: How do I do
)
Well actually for the linux client, it's NOT on by default. You need to add a truxoft_prefs.xml file to your boinc directory. The windows zip file on truxofts website has this xml file in it, but the linux version only contains the boinc executable.
Create a file truxoft_prefs.xml with the following contents:
all
You will then after 30 results see your credits calibrated.
RE: RE: RE: RE: How
)
Thanks a heap for that. I am very new to Linux, still expect it to do things Windows does. Your help is very much appreciated.
RE: Thanks a heap for
)
Your welcome. It's not actually a linux thing that's the problem. It's how the zip files on trux's site were prepared. The linux gzip just doesn't include the required XML file, while the windows zip does. Not including it in the linux gzip is just an oversight by the person preparing it, IMO, and it makes the statement on the website "calibration is turned on by default . . ." confusing.
RE: MarkF, I would love my
)
I have to thank Akos for that, maybe he can work his magic on all the platforms eventually. (fingers crossed)
Boinc Studio provides the credit correction such that the 'Result duration correction factor' is normalized to 1.
RE: Your welcome. It's not
)
My thoughts exactly, sorry about the confusion folks...
Tim
Got another one with no
)
Got another one with no credit but says successful:-
http://einsteinathome.org/workunit/8428107
differnet machine this time.
I also have been credited for the previous 3 that gave no credit.
P.S. the calibration file is working fine, thanks for that.
RE: Got another one with no
)
Yes it is sucessful, but click on Result ID and look at validate state. Invalid. It's sucessful because the quorum was fulfilled, yet your result was determined invalid. This is expected behaviour once in a while with the linux beta app. Notice: BETA app. They are trying to fix the intermittant invalids for the official linux app to come.
Ok, thanks. I will see what
)
Ok, thanks. I will see what happens over time.
Success means it was
)
Success means it was downloaded, crunched, returned and reported correctly. Nothing more. It does not determine validity.