Forum > GPU crunching
CPU <-> GPU rebranding
Richard Haselgrove:
--- Quote from: Morten on 04 Jul 2009, 06:41:21 am ---Hi,
What about MB application 605? I only have 605 no 603s, so I receive "Error : There is no application defined for version 603".
Regards
Morten Ross
--- End quote ---
Look at the SETI applications page. There is no current MB application 605: there will, briefly, have been a CUDA app with that number, while they were ironing out the initial major bugs, but that app has long since passed into history.
If you are seeing v6.05 on your host, then at some point you must have installed an app_info.xml file with a 605 version number reference. I suggest you go and review the work you did then, and reassure yourself that whatever application you installed to handle that 605 reference is still an appropriate one that you want to use. Assuming that it is, duplicate your 605 section and change one of the copies to have a 603 version number: ReScheduled tasks should work then.
This is one reason why it's a good idea to stick with the project's version numbering, even when installing third party applications. It makes absolutely no difference at all to the validity of the results, but non-standard numbering can have unexpected side-effects later on, as here.
Raistmer:
If you simple dublicate your 605 field, new downloaded tasks will still be branded as 605 and still no 603 wtasks will be available. You need to get rid from 605 completely by drying your current cache and changing 605 to 603.
[603 version num reserved for CPU app and 608 - for GPU CUDA app for now]
Richard Haselgrove:
But if he uses Marius's "ReSchedule" tool to create 603 tasks, then a double-version app_info will run them. It would have the interesting, and possibly useful, side-effect of allowing him to distinguish between rebranded tasks (v6.03) and native MB/CPU downloads (v6.05). It would, however, destroy any chance of using Marius's tool to rebrand downloaded CPU tasks back to CUDA.
@ Morten,
One thing I didn't cover in my previous post: do make absolutely sure that your '605' reference doesn't point to a CUDA app! The whole point of rebranding is to point the tasks to a CPU handler. Your description "MB application" could refer to either CPU or CUDA.
@ Marius,
How are the CPU and CUDA versions defined in your application? Are they hard-coded version numbers, or are they data picked up from the .ini file? It would be better, in the long run, to use configuration data to establish the version numbers, to allow for future Berkeley releases and special cases like Morten's.
MarkJ:
I just downloaded it and installed on all my cuda machines, after first testing it on one of them. Seems I have VLAR/VHAR on all of them except one (it didn't have any MB work).
I did notice that the rebranded work units immediately went into "running, High Priority" mode. Seems their estimated time was 20+ hours. That estimate is dropping like a stone as it starts crunching them so it will work it out, but they will be finished by the time the TSI has come up (60 mins).
@ Marius, its a great little tool. Thank you. 8)
One question about the automatic mode and the default time of 4 hours. I assume it just sits there waiting for the 4 hours to be up and then does its scan/rebrand before going back to sleep. I don't need to get windows to schedule it?
Cheers,
MarkJ
Morten:
I was referring to CPU 605s, and based on app_info, some of which had both 603 and 605, and boinc started to pick up on the 605s recently. I thus assumed that 603s were about to expire and removed 603s from app_info. I have now reverted back to 603 and removed reference to 605s in my countless different app_infos, sigh.
Morten
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version