Forum > GPU crunching
CPU <-> GPU rebranding
Marius:
--- Quote from: samuel7 on 05 Jul 2009, 06:18:41 am ---Having managed to download a few more tasks, I suspended computation (I prefer doing this even if it's not necessary), hit Run and BOINC was stopped, 37 tasks moved and BOINC restarted. Great, I thought. Upon resuming computation however, two VLARs that had earlier been moved to the CPU (AK_v8_win_x64_SSE41) exited with 'SETI@home error -1 Can't create file -- disk full?' The CUDA task and two Einstein tasks restarted fine.
--- End quote ---
The tool only makes some minor changes in the client_state.xml and does nothing with the applications itself. I googled a bit, but this error "disk full" seems to occur only in combination with very old versions of boinc, but since you run a rather recent version i dont expect that to be the case.
The only thing that is kind of suspicious to me is that you suspend boinc while running the tool. In the basic configuration boinc leaves the applications in memory confronting those with unexpected changes in the client_state.xml. Advise is to stop boinc completely and not suspend it. But i don't think this will cause the disk-full errors though....
Greetings,
Marius
Marius:
--- Quote from: Raistmer on 05 Jul 2009, 06:31:46 am ---@Marius
BTW, how your tool will handle systems with SETI +SETI beta installations?
Can it be used in such situation? will it rebrand beta tasks?
--- End quote ---
1.8 and lower only do hardcoded 603 and 608 versions.
Richard mentioned about the same for future versions a few messages back. So i made changes to (not released) 1.9 to avoid using hardcoded versions. That one will parse all <app_version> filter those on app_name=setiathome_enhanced, split on plan_class=cuda and use the highest version_num as the default application for cpu and/or gpu. Would this approach work for the beta version as well?
I guess this will not work if you run the combination of seti + beta (not sure this combination is possible though)
Marius:
--- Quote from: Geek@Play on 05 Jul 2009, 01:03:49 am ---Could it be trying to reschedule an abandoned Boinc installation?
--- End quote ---
Unlikely unless he pointed the data directory to a location with an empty client_state. But since the host is running fine i dont think this is the case.
I need to install a vista version this week anywhay so i will use that to test (if i ever get some workunits though :o)
Raistmer:
--- Quote from: Marius on 05 Jul 2009, 08:59:21 am ---I guess this will not work if you run the combination of seti + beta (not sure this combination is possible though)
--- End quote ---
Such combination possible. SETI and SETI beta are different projects but both use SETI_enhanced tag for SETI MB. The problem is - their tasks reside in different directories (cause they belong to different projects).
So, from client_state workunit record point of view they are almost the same but fi you will need to parse WU itself you should look in another directory for that.
For now beta uses that same 603 and 608 app versions so its MB tasks almost indistinguishable from SETI main ones
Marius:
--- Quote from: Raistmer on 05 Jul 2009, 09:22:13 am ---Such combination possible. SETI and SETI beta are different projects but both use SETI_enhanced tag for SETI MB. The problem is - their tasks reside in different directories (cause they belong to different projects).
So, from client_state workunit record point of view they are almost the same but fi you will need to parse WU itself you should look in another directory for that.
For now beta uses that same 603 and 608 app versions so its MB tasks almost indistinguishable from SETI main ones
--- End quote ---
Then it sureley wont work because of three problems
1) The tool would need two running instances (because of different data directory), but because of a mutex it will not allow that (just to make sure people don't have 2 or more running instances).
2) It is currently hardcoded on the seti project ...\setiathome.berkeley.edu path. I need to configure project(s) and parse the projects as well to make this work.
3) It currently picks up al workunits for version 603 and 608 (without checking project, kind of a big bug on my side here). Running seti + beta in the same boinc setup would corrupt your client_state as it does not check projects.
But since seti beta is basicly the same i could make this work, but is it wurth the trouble? (its totally designed for a single project now)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version