The easiest way is to not tell BOINC about the file - just create it in the project directory, and look for it there in subsequent jobs.
The app can get the project dir from the APP_INIT_DATA: http://boinc.berkeley.edu/trac/wiki/StatusApi -- David On 25-Jun-2015 2:10 AM, Marius Millea wrote:
Suppose the result of a computation yields a large file which I would like 1) to remain on host 2) to be used in subsequent computations 3) to not be uploaded I think I know how to do 1), if I have the file in the output template I can add the <copy_file> flag. Is there actually any way to do 2 or 3 though? Thanks, Marius _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu 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 boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
