BOINC Manager seems to handle it natively fine for me.
BT is 3rd party after all. I personally don't use it. just using BOINC manager seems to work better. BT JS is broken half the time I'm trying to use it anyway. randomly wont connect and the interface and UX is terrible IMO with non-intuitive interface and configurations
I think you are still trying to avoid running with an app_info.xml file?
Yes, I "prefer" sticking with just the app_config and not going the app_info route as that "breaks" the automatic version upgrades, etc.
...EXTRA! EXTRA! ... As of 9 a.m. today (just 90 minutes ago) the servers downloaded the O3AS 1.15 (cuda) app and two work units. This is very encouraging. My hopes are raised that the v1.14 (cuda recalc stage) will eventually be downloaded, and boinc will discover 1.14 is slightly faster than 1.15 and bias the work units in that direction.
I'm going to keep the <no_opencl> setting as it, at least, contributed to moving to the cuda app(s). For the time being I will keep the "run test application" enabled as that setting may be necessary(?) for getting the cuda apps. Actually, I'm o.k. with a permanent "run test apps" to help out in future Beta trials.
i think if you turn off beta, you should get 1.14 now that you've inhibited OpenCL work.
pretty sure 1.14 is not in the beta chain. with beta enabled, and the project's preference to always send beta work first, not sure if you will be sent the 1.14 otherwise.
Hm. Or maybe not. I followed up on my own suggestion and used this host to test. It initially had opencl installed and ran using a host venue with beta testing enabled, O3AS only. Just as it had been doing all winter, it downloaded and ran 1.15 (CUDA/recalcCPU). I then switched off beta testing, and it got and ran 1.07 (opencl) only. I didn't bother to wait for a day or so but deinstalled the nvidia-opencl-icd through Synaptic, restarted the system and let BOINC request work. The log message (or what I think is relevant of it) looked like this:
2024-06-25 19:44:30.2791 [PID=1851455] [version] Checking plan class 'GW-opencl-nvidia-2'
2024-06-25 19:44:30.2791 [PID=1851455] [version] parsed project prefs setting 'gpu_util_gw': 0.500000
2024-06-25 19:44:30.2791 [PID=1851455] [version] NVidia device (or driver) doesn't support OpenCL
2024-06-25 19:44:30.2791 [PID=1851455] [version] Checking plan class 'GW-cuda'
2024-06-25 19:44:30.2791 [PID=1851455] [version] parsed project prefs setting 'gpu_util_gw': 0.500000
2024-06-25 19:44:30.2791 [PID=1851455] [version] Peak flops supplied: 1.03056e+12
2024-06-25 19:44:30.2791 [PID=1851455] [version] GPU RAM calculated: min: 2500 MB, use: 2000 MB, WU#813563294 CPU: 300 MB
2024-06-25 19:44:30.2791 [PID=1851455] [version] plan class ok
2024-06-25 19:44:30.2792 [PID=1851455] [version] beta test app versions not allowed in project prefs.
2024-06-25 19:44:30.2793 [PID=1851455] [version] no app version available: APP#56 (einstein_O3AS) PLATFORM#7 (x86_64-pc-linux-gnu) min_version 0
and the host was not getting any work.
Switching beta-testing on again, everything is back to normal in that it downloads work for 1.15 an runs it.
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
in the app_info file, you don't even need the version number line at all. omit it completely and it's easier to switch back and forth between app versions just by changing the filename called.
if you leave the app version in, and later change which app you want to use without exhausting the cache, BOINC will delete all of them when you make the switch since all the old tasks in the queue are marked for the 'old' app but BOINC doesnt see (app_info) that you have the 'old' app anyway and abandons them. without the parameter at all, they all get marked with v0.00 regardless of which one is actually in use and BOINC wont abandon them.
Does this make it easier to switch from say v1.14 and v1.08?
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
2024-06-25 19:44:30.2791 [PID=1851455] [version] plan class ok
2024-06-25 19:44:30.2792 [PID=1851455] [version] beta test app versions not allowed in project prefs.
2024-06-25 19:44:30.2793 [PID=1851455] [version] no app version available: APP#56 (einstein_O3AS) PLATFORM#7 (x86_64-pc-linux-gnu) min_version 0
and the host was not getting any work.
Switching beta-testing on again, everything is back to normal in that it downloads work for 1.15 an runs it.
That's odd.
Walton
Thank you so much Walton748; reassuring to know that my situation is not a total outlier case.
That is the same result I am getting. Beta=off and <no_opencl> the servers send nothing;// Beta=on and <no_opencl> the servers send 1.15. With opencl enabled the servers send only 1.07 whether Beta is on or off. Maybe I didn't wait long enough, but my first setup (opencl=yes + Beta=no) ran for over 30 days and never got any cuda apps of any kind, either v1.14 or v1.15. Setup now for <no_opencl> and Beta=YES and I'll let it run forever. v1.14 is only 30 seconds faster than v1.15 anyway. But it's the "principle of the thing..." in that v1.14 is a production app and should go automatically to a cuda-capable host.
With opencl enabled the servers send only 1.07 whether Beta is on or off.
...
That's not the case for me. With opencl installed and not disabled (i never did that) I could change between 1.07 and 1.15 (and only these) using the beta switch in my host venue. Just to be precise.
It looks like Pioneers has switched from brp7/meerKat to All-Sky GW and is coming on strong!
The system is running stock 1.07 version. Looks like it maybe 1x.
Free-DC said the system ran 7M+ yesterday. Since it is showing 4.9M now, lots of room for growth.
There goes my 5th place ranking (probably).
;)
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
BOINC Manager seems to handle
)
BOINC Manager seems to handle it natively fine for me.
BT is 3rd party after all. I personally don't use it. just using BOINC manager seems to work better. BT JS is broken half the time I'm trying to use it anyway. randomly wont connect and the interface and UX is terrible IMO with non-intuitive interface and configurations
_________________________________________________________________________
Tom M wrote: ...snip... I
)
Yes, I "prefer" sticking with just the app_config and not going the app_info route as that "breaks" the automatic version upgrades, etc.
...EXTRA! EXTRA! ... As of 9 a.m. today (just 90 minutes ago) the servers downloaded the O3AS 1.15 (cuda) app and two work units. This is very encouraging. My hopes are raised that the v1.14 (cuda recalc stage) will eventually be downloaded, and boinc will discover 1.14 is slightly faster than 1.15 and bias the work units in that direction.
I'm going to keep the <no_opencl> setting as it, at least, contributed to moving to the cuda app(s). For the time being I will keep the "run test application" enabled as that setting may be necessary(?) for getting the cuda apps. Actually, I'm o.k. with a permanent "run test apps" to help out in future Beta trials.
i think if you turn off beta,
)
i think if you turn off beta, you should get 1.14 now that you've inhibited OpenCL work.
pretty sure 1.14 is not in the beta chain. with beta enabled, and the project's preference to always send beta work first, not sure if you will be sent the 1.14 otherwise.
_________________________________________________________________________
Hm. Or maybe not. I followed
)
Hm. Or maybe not. I followed up on my own suggestion and used this host to test. It initially had opencl installed and ran using a host venue with beta testing enabled, O3AS only. Just as it had been doing all winter, it downloaded and ran 1.15 (CUDA/recalcCPU). I then switched off beta testing, and it got and ran 1.07 (opencl) only. I didn't bother to wait for a day or so but deinstalled the nvidia-opencl-icd through Synaptic, restarted the system and let BOINC request work. The log message (or what I think is relevant of it) looked like this:
2024-06-25 19:44:30.2791 [PID=1851455] [version] Checking plan class 'GW-opencl-nvidia-2'
2024-06-25 19:44:30.2791 [PID=1851455] [version] parsed project prefs setting 'gpu_util_gw': 0.500000
2024-06-25 19:44:30.2791 [PID=1851455] [version] NVidia device (or driver) doesn't support OpenCL
2024-06-25 19:44:30.2791 [PID=1851455] [version] Checking plan class 'GW-cuda'
2024-06-25 19:44:30.2791 [PID=1851455] [version] parsed project prefs setting 'gpu_util_gw': 0.500000
2024-06-25 19:44:30.2791 [PID=1851455] [version] Peak flops supplied: 1.03056e+12
2024-06-25 19:44:30.2791 [PID=1851455] [version] GPU RAM calculated: min: 2500 MB, use: 2000 MB, WU#813563294 CPU: 300 MB
2024-06-25 19:44:30.2791 [PID=1851455] [version] plan class ok
2024-06-25 19:44:30.2792 [PID=1851455] [version] beta test app versions not allowed in project prefs.
2024-06-25 19:44:30.2793 [PID=1851455] [version] no app version available: APP#56 (einstein_O3AS) PLATFORM#7 (x86_64-pc-linux-gnu) min_version 0
and the host was not getting any work.
Switching beta-testing on again, everything is back to normal in that it downloads work for 1.15 an runs it.
That's odd.
Walton
Ah.
)
Deleted
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
Ian&Steve C. wrote: in the
)
Does this make it easier to switch from say v1.14 and v1.08?
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!
in my opinion, yes.
)
in my opinion, yes.
_________________________________________________________________________
walton748 wrote: Hm. Or
)
Thank you so much Walton748; reassuring to know that my situation is not a total outlier case.
That is the same result I am getting. Beta=off and <no_opencl> the servers send nothing;// Beta=on and <no_opencl> the servers send 1.15. With opencl enabled the servers send only 1.07 whether Beta is on or off. Maybe I didn't wait long enough, but my first setup (opencl=yes + Beta=no) ran for over 30 days and never got any cuda apps of any kind, either v1.14 or v1.15. Setup now for <no_opencl> and Beta=YES and I'll let it run forever. v1.14 is only 30 seconds faster than v1.15 anyway. But it's the "principle of the thing..." in that v1.14 is a production app and should go automatically to a cuda-capable host.
Eugene Stemple
)
That's not the case for me. With opencl installed and not disabled (i never did that) I could change between 1.07 and 1.15 (and only these) using the beta switch in my host venue. Just to be precise.
Cheers,
Walton
It looks like Pioneers has
)
It looks like Pioneers has switched from brp7/meerKat to All-Sky GW and is coming on strong!
The system is running stock 1.07 version. Looks like it maybe 1x.
Free-DC said the system ran 7M+ yesterday. Since it is showing 4.9M now, lots of room for growth.
There goes my 5th place ranking (probably).
;)
A Proud member of the O.F.A. (Old Farts Association). Be well, do good work, and keep in touch.® (Garrison Keillor) I want some more patience. RIGHT NOW!