Opencl Help!

Message boards : Number crunching : Opencl Help!

To post messages, you must log in.

AuthorMessage
Profile Cliff Harding
Volunteer moderator
Volunteer tester
Avatar

Send message
Joined: 18 Aug 99
Posts: 1267
Credit: 74,307,784
RAC: 22,102
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!!
ID: 1350163 · Report as offensive
Profile jason_gee
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 24 Nov 06
Posts: 7291
Credit: 87,668,441
RAC: 11,732
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.
"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.
ID: 1350166 · Report as offensive
Profile Cliff Harding
Volunteer moderator
Volunteer tester
Avatar

Send message
Joined: 18 Aug 99
Posts: 1267
Credit: 74,307,784
RAC: 22,102
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!!
ID: 1350170 · Report as offensive

Message boards : Number crunching : Opencl Help!


 
©2017 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.