Make sure you've changed the right "preference set" (also known as venue or location). At the bottom of the details page for you computers you can see which location they are assigned to - Generic, Home, Work or School. Then when editing the preferences make sure the "preference set" matches that location.
I've checked it multiple times already - everything's correct.
BOINC Manager displays correct location for both machines. But client still uses preferences for Generic location. I've checked this by changing one option for Generic (unchecked using Beta versions) and both my machines - Work and Home - get this changed setting and stop getting Beta. This is strange.
BTW, I use local computing prefs. Can this be the reason for ignoring project prefs?
My host gets correct project prefs for Work venue (don't allow beta work) but for some unknown reason uses prefs for Generic venue (allow beta). Once again, if I disable 'allow beta work' in Generic prefs, all my hosts (work and home) stop getting beta. So only Generic prefs are used in my case.
I've made another change for Work venue - disabled Arecibo GPU apps for which I'm still getting betas. I'll see if I continue to get those apps. I'll report on that later.
I've made another change for Work venue - disabled Arecibo GPU apps for which I'm still getting betas. I'll see if I continue to get those apps. I'll report on that later.
That won't help since the Beta flag has precedence over the app selection. So you will still get the Arecibo GPU App. That is a nuisance that we maybe should get rid of, since it seems to cause more inconvenience than it is beneficial for testing.
I identified the problem. I'm about to deploy a fix on our server to circumvent the problem. This means venues will work on Einstein@Home again but not on other projects where our preferences are propagated to. In the meantime we are working on a solution that will fix the problem for other projects too. This is on high priority as it affects both project_specific preferences and computing preferences.
You can also fix this yourself if you de-select the presets in your computing preferences and select "custom" (far right option) then open the "Advanced Options". This will clear the preset="*" attribute that is causing problems.
Make sure you've changed the
)
Make sure you've changed the right "preference set" (also known as venue or location).
At the bottom of the details page for you computers you can see which location they are assigned to - Generic, Home, Work or School. Then when editing the preferences make sure the "preference set" matches that location.
Details page for the computer with a Nvidia card
Details page for the computer with an AMD card
I've checked it multiple
)
I've checked it multiple times already - everything's correct.
BOINC Manager displays correct location for both machines. But client still uses preferences for Generic location. I've checked this by changing one option for Generic (unchecked using Beta versions) and both my machines - Work and Home - get this changed setting and stop getting Beta. This is strange.
BTW, I use local computing prefs. Can this be the reason for ignoring project prefs?
Local computing prefs should
)
Local computing prefs should not interfere with the project specific preferences. This might be something for the admins to look at on Monday.
I wonder if this issue is
)
I wonder if this issue is related to this invalid global preferences thread
AgentB wrote:I wonder if this
)
It says in this thread that affected hosts get specific message. My hosts don't.
The following is the part of project prefs file my host gets from server:
<venue name="home" preset="standard">
<project_specific>
<graphics fps="20" width="800" height="600" quality="low"/>
<also_run_cpu>0</also_run_cpu>
<gpu_util_brp>1.00</gpu_util_brp>
<gpu_util_fgrp>1.00</gpu_util_fgrp>
<gpu_util_gw>1.00</gpu_util_gw>
</project_specific>
<resource_share>100</resource_share>
<no_cpu>0</no_cpu>
<no_cuda>0</no_cuda>
<no_ati>1</no_ati>
<no_intel_gpu>1</no_intel_gpu>
<allow_beta_work>1</allow_beta_work>
</venue>
<venue name="work" preset="standard">
<project_specific>
<graphics fps="20" width="800" height="600" quality="low"/>
<also_run_cpu>0</also_run_cpu>
<gpu_util_brp>1.00</gpu_util_brp>
<gpu_util_fgrp>1.00</gpu_util_fgrp>
<gpu_util_gw>1.00</gpu_util_gw>
</project_specific>
<resource_share>100</resource_share>
<no_cpu>0</no_cpu>
<no_cuda>1</no_cuda>
<no_ati>0</no_ati>
<no_intel_gpu>1</no_intel_gpu>
<allow_beta_work>0</allow_beta_work>
</venue>
<project_specific>
<graphics fps="20" width="800" height="600" quality="low"/>
<also_run_cpu>0</also_run_cpu>
<gpu_util_brp>1.00</gpu_util_brp>
<gpu_util_fgrp>1.00</gpu_util_fgrp>
<gpu_util_gw>1.00</gpu_util_gw>
</project_specific>
<resource_share>100</resource_share>
<no_cpu>0</no_cpu>
<no_ati>0</no_ati>
<no_cuda>0</no_cuda>
<no_intel_gpu>1</no_intel_gpu>
<allow_beta_work>1</allow_beta_work>
</project_preferences>
My host gets correct project prefs for Work venue (don't allow beta work) but for some unknown reason uses prefs for Generic venue (allow beta). Once again, if I disable 'allow beta work' in Generic prefs, all my hosts (work and home) stop getting beta. So only Generic prefs are used in my case.
I wonder if this is due to
)
I wonder if this is due to the extra preset="standard" attribute we add. Normally the client should ignore this. I'll look into this on Monday.
Thanks, Christian. I've made
)
Thanks, Christian.
I've made another change for Work venue - disabled Arecibo GPU apps for which I'm still getting betas. I'll see if I continue to get those apps. I'll report on that later.
Alexander Favorsky
)
That won't help since the Beta flag has precedence over the app selection. So you will still get the Arecibo GPU App. That is a nuisance that we maybe should get rid of, since it seems to cause more inconvenience than it is beneficial for testing.
Alright, undone this change.
)
Alright, undone this change.
I identified the problem. I'm
)
I identified the problem. I'm about to deploy a fix on our server to circumvent the problem. This means venues will work on Einstein@Home again but not on other projects where our preferences are propagated to. In the meantime we are working on a solution that will fix the problem for other projects too. This is on high priority as it affects both project_specific preferences and computing preferences.
You can also fix this yourself if you de-select the presets in your computing preferences and select "custom" (far right option) then open the "Advanced Options". This will clear the preset="*" attribute that is causing problems.