Forum > GPU crunching
CPU <-> GPU rebranding
Marius:
--- Quote from: Josef W. Segur on 06 Aug 2009, 05:06:27 pm ---Marius, would you describe more fully what the 1.9 release note relating to SETI Beta means? Is it just avoiding messing with Beta work, or actually meant to allow rebranding of work at Beta? If the latter, it appears not to be working from Jason Keil's experience.
Joe
--- End quote ---
Sure, previous versions would simply mess up the client_state.xml as it was unable to distinguish units from seti beta and seti main. If you read a few pages back in this thread you problably can find the conversation about it.
1.9 is ONLY able to rebrands for seti main.
If i have time i would like to introduce seti-beta rebranding in a 2.0 version (its exactly the same, only app_name is different).
Greetings,
Marius
Josef W. Segur:
OK, I was too optimistic when I read the note, wishful thinking I guess :D I did remember the exchanges about the difficulty, I think I even commented therein.
In case it might encourage you to do the 2.0 version, I'll note that the file being split for Beta has a good mix, midrange and VHAR for the first part then VLAR for the end. I'm not sure how much of each, haven't investigated that closely. But there have been at least 6 channels split and the work that brought up the question was from the later part of the first of those. The others will of course have the same pattern, all feeds travel together. At the rate Beta participants get through work, there may be a week or two of non-VLAR work before the next problems. All in all, there's about 3 months of work already split (I think the mb_splitter there is using the same "Results ready to send" queue control values as Main).
Joe
MarkJ:
--- Quote from: msattler on 05 Aug 2009, 10:16:50 am ---Well........
I just had a scare with the rebranding tool.......
Got some new cuda work overnight, and ran the tool to move some VLAR over to the CPU. Tool ran, moved the work, and got the password error when restarting Boinc.
Manually shut Boinc down and restarted it, and when it came back up, the 'attach to project' window came up!!! No projects, no tasks!
Shut it down again and restarted it again, and, praise to the Gods of Seti....my tasks were back. The only ill effect was the loss of a bunch of crunch time on 4 AP wu's it had been crunching on....they exited with computation errors.
--- End quote ---
The core-client seems to start up, just the manager is unable to connect to it. I usually just click Advanced -> Select Computer and hit the Okay button (or enter) and it will reconnect.
k6xt:
--- Quote from: msattler on 05 Aug 2009, 10:16:50 am ---I just had a scare with the rebranding tool.......Got some new cuda work overnight, and ran the tool to move some VLAR over to the CPU. Tool ran, moved the work, and got the password error when restarting Boinc.
--- End quote ---
This happened to me as well when I ran the tool in manual mode. Running via a cmd batch file using the commands posted in this thread there was no error i.e. autorun 75.
Edit: [Snip] Sorry forget I asked!
In accordance with instructions I herewith post my thanks to Raistmer, Marius et al for a marvelous tool. No more killed VLAR's!
thanks
Art
Fredericx51:
Hi , I never had a problem , stopping BOINC, even when using the sleep mode ,availeble when right-clicking on the tasbar - icon.
Never had to use net stop boinc, so time to install this tool, too ::)
You've done a great job Raistmer!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version