Richard Haselgrove wrote, On 01.12.11 21:59: > Would that work under the new v7 client data model, which separates upload > and download files? Since the files are intended to be both generated and > used locally, they would have neither a download nor an upload url. > > Also, since Raistmer is working as an independent developer outside a > project structure, he doesn't have access to the "job" file specifications: > the intention would be to define the files via anonymous platform and > app_info.xml > > The nearest analog would be the app_version of a project-delivered > application. I was wondering whether Oliver Bock had considered using > locally-compiled kernels in the Einstein OpenCL application,
No, not yet. > and if so what his solution to this issue would be? Don't know what Oliver thinks. But what about just putting the file into the project_directory (as available from init_data.xml), without letting the CC know about it at all? The CC won't delete it, would it? Best, Bernd > ----- Original Message ----- > From: "David Anderson"<[email protected]> > To:<[email protected]> > Sent: Wednesday, November 30, 2011 9:08 PM > Subject: Re: [boinc_dev] What is a proper way to have persistent file > written by project's app? > > >> You can do this by making them output files of the jobs, >> with the<sticky/> flag >> and without the<upload_when_present/> flag. >> >> In principle this should work, but I'm not sure it's been done before. >> If you encounter any problems, let me know. >> >> -- David >> >> On 30-Nov-2011 1:40 PM, Raistmer wrote: >>> For example, I want to use binary OpenCL kernels compiled for particular >>> user's GPU on first app run (app distributed with source CL file to make >>> it >>> compatible with all OpenCL devices). So, app needs to write some binary >>> file >>> that will be retrieved on next app run. And not recreated from scratch on >>> each and every app's run. There are persistent files distributed from >>> project >>> (einstein use them) but how to make something alike but directly on >>> client >>> side ? _______________________________________________ boinc_dev mailing >>> list [email protected] >>> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, >>> visit the above URL and (near bottom of page) enter your email address. >> _______________________________________________ >> boinc_dev mailing list >> [email protected] >> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev >> To unsubscribe, visit the above URL and >> (near bottom of page) enter your email address. >> > > _______________________________________________ > boinc_dev mailing list > [email protected] > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev > To unsubscribe, visit the above URL and > (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
