Opencl Help!


log in

Advanced search

Message boards : Number crunching : Opencl Help!

Author Message
Profile Cliff HardingProject donor
Volunteer tester
Avatar
Send message
Joined: 18 Aug 99
Posts: 974
Credit: 51,397,299
RAC: 37,816
United States
Message 1350163 - Posted: 24 Mar 2013, 15:18:45 UTC

It's been a while since I upgraded my NVidia Opencl app and have a question prior to upgrading to r1764, which is -- Why do we need 2 cmdline txt files when one is empty?. The following was introduced in the r1761 version

<file_name>ap_cmdline_win_x86_SSE2-OpenCL_NV.txt</file>
<open_name>ap_cmdline.txt</open_name>


All cmdline text is in the <file_name>, while the file named in <open_name> is empty. When I upgraded to r1761, I renamed what was then the cmdline text file to <file_name> and created a new empty cmdline.txt <open_name>.
____________


I don't buy computers, I build them!!

Profile jason_geeProject donor
Volunteer developer
Volunteer tester
Avatar
Send message
Joined: 24 Nov 06
Posts: 4978
Credit: 73,335,035
RAC: 16,194
Australia
Message 1350166 - Posted: 24 Mar 2013, 15:28:13 UTC - in response to Message 1350163.
Last modified: 24 Mar 2013, 15:31:24 UTC

That mechanism basically tells Boinc to use the full versioned name, by creating a boinc softlink in the slot with the generic open name expected by the app.

That allows the app to just use the generic name, but Boinc links it to & opens the appropriate file, usually in the project directory. The reasoning I believe is that firstly the Boinc server infrastructure doesn't like name clashes across app versions, while adjusting the name in every app build is not easy/practical.

A potentially positive side effect is that it allows you to use different apps with versioned files perhaps with differing settings.

[In the server distributed case] The settings files are distributed as 0 length files so that the client doesn't 'freak out' and try to redownload when you modify it.
____________
"It is not the strongest of the species that survives, nor the most intelligent that survives. It is the one that is the most adaptable to change."
Charles Darwin

Profile Cliff HardingProject donor
Volunteer tester
Avatar
Send message
Joined: 18 Aug 99
Posts: 974
Credit: 51,397,299
RAC: 37,816
United States
Message 1350170 - Posted: 24 Mar 2013, 15:35:32 UTC - in response to Message 1350166.

That mechanism basically tells Boinc to use the full versioned name, by creating a boinc softlink in the slot with the generic open name expected by the app.

That allows the app to just use the generic name, but Boinc links it to & opens the appropriate file, usually in the project directory. The reasoning I believe is that firstly the Boinc server infrastructure doesn't like name clashes across app versions, while adjusting the name in every app build is not easy/practical.

A potentially positive side effect is that it allows you to use different apps with versioned files perhaps with differing settings.

[In the server distributed case] The settings files are distributed as 0 length files so that the client doesn't 'freak out' and try to redownload when you modify it.



Thanks Jason, I will carry on with the upgrade.
____________


I don't buy computers, I build them!!

Message boards : Number crunching : Opencl Help!

Copyright © 2014 University of California