BUT, we're expecting a new 'Version 7' of seti@home in the next few months - no release date even pencilled in yet. That one will definitely be a 'required upgrade', so keep watching this space.

Actually, Pond Grass Shrimp posted maybe a year off for Boinc ver.7....
Or is that not the same thing as Seti ver.7?

---

"Time is simply the mechanism that keeps everything from happening all at once."

Indeed, it's not the same. ;-)

Gruß,
Gundolf

Indeed, it's not the same. ;-)

Gruß,
Gundolf

OK....
The ol' kittyman gets confused sometimes.
Boinc=Boinc.
Seti=Seti.......
Boinc+Seti=crunching.

Got it.

---

"Time is simply the mechanism that keeps everything from happening all at once."

The 6.13.x builds of BOINC are the alpha's of what will become the 7.x.x builds.

SETI beta is running the beta test of v7.

---

Please add an option to the unified installer so I can select the number of GPU tasks and CPU cores that I want to run at a time. This would be much cleaner than editing the file after the fact.

example:
Number of CPU cores to leave idle: 1
Number of GPU work units to run: 3

---

It's not too many computers, it's a lack of circuit breakers for this room. But we can fix it :)

I dont think this will happen.

---

With each crime and every kindness we birth our future.

As Mike said, I don't think this will happen. The idea is to make the installers as easy to use as possible so most anyone can use them. Adding extra options like that would probably confuse the novice user.

---

PROUD MEMBER OF Team Starfire World BOINC

As Mike said, I don't think this will happen. The idea is to make the installers as easy to use as possible so most anyone can use them. Adding extra options like that would probably confuse the novice user.

For the installer, 'probably not' but that's out of my hands now.

Probably for application specific tweaks at some point a pretty little control console of some sort will be devised for optional install, with all manner of tweakables... It's pretty low on the priority list at this time, and ideas need to mature, but will probably happen eventually. As apps become more sophisticated there will be something better (i.e. safer) needed than manual editing of configuration files, even if only for intermediate level users.

The 560ti's situation comes down to a high potential for voltage, clockrate & temperature issues from novice users, so at the moment I'm brainstorming more in the the direction of sensing issues to offer some sortof limited guidance. nVidia's nvapi library seems promising so far for control, and research is indicating that some level of supervisory monitoring with evasive measures could be employed.

Jason

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

Oh boy!! With all kind of little bells and whistles and levers and sliders and switches so I can really mess things up?? :-)



oh,oh, dont forget knobs, me like knobs!!

---

PROUD MEMBER OF Team Starfire World BOINC

Please add an option to the unified installer so I can select the number of GPU tasks and CPU cores that I want to run at a time. This would be much cleaner than editing the file after the fact.

example:
Number of CPU cores to leave idle: 1
Number of GPU work units to run: 3

I might be able to put something together for this
Not sure about leaving a CPU core free, but the GPU workunits to run should be quite simple
I'll have a play tonight and get back to you, but as Jason says it would be a seperate install to the installer

Hi all,

I've installed the lunatic unified apps a couple of hours ago. I checked GPU-usage and found it very poor, so I started to experiment with different settings of <count> in the app_info.

atm I run that with a settting of 0.3 Seems to work, but display of the progress-bar acts strange. Sometimes two wu's show progress, sometimes none.
When I updated the drivers to 11.6 the system was unusable. Needed to complete uninstall all ati and nVidia-software. atm I have two ATI-cards installed and CCC 11.6b Seems to work, but can this be the cause of strange progress-bar behavior?

Another thing is the Lunatics installer. I have one 4850 and one 5830 in this system. What is the correct setting for the MultBeam App? It forces me to decide between HD5 and no-HD5 app.

The last thing is: is it possible to remove the auto-restart of the BM after the installation with help of the unified installer? Or at least place a message that BM will be restarted after pressing 'finish'. I had some Spinhendge wu's running; they checkpoint only after 95% and I lost a lot of crunching-hours.

Alexander

---

1)11.6 drivers known to have problems on some hosts. Try Cat 11.2.
2) progress bar updated when predefined part of calculation will be finished. Different parts may take different time so sometimes progress bar ticks not every second (it's a waste of resourses and your own time - to make and to watch progress bar tick every second, don't you think so? ;) )
3) installer should restart BOINC (at least it should stop it to make changes).
4) with mixed capabilities GPU setup like HD4xxx and HD5xxx one should use lower-capability application. There is no known way to tell BOINC to use HD5 only for HD5xxx GPU and not for HD4xxx GPU.

I had some Spinhendge wu's running; they checkpoint only after 95% and I lost a lot of crunching-hours.

Alexander

Is this something you can change in your preferences for the project? I know you can change the checkpoint interval on Seti.

---

"Time is simply the mechanism that keeps everything from happening all at once."

The last thing is: is it possible to remove the auto-restart of the BM after the installation with help of the unified installer? Or at least place a message that BM will be restarted after pressing 'finish'. I had some Spinhendge wu's running; they checkpoint only after 95% and I lost a lot of crunching-hours.

Alexander

And second note....
Changing the restart of Boinc to manual will not change the situation. If they were not checkpointed, the work done was lost when Boinc shut down to do the install, not upon restart.

---

"Time is simply the mechanism that keeps everything from happening all at once."

Good point Mark.

While running those projects you should always finnish your running tasks before using the installer.

---

With each crime and every kindness we birth our future.

Wow, what a response!

Is this something you can change in your preferences for the project?

Project admins say no, it's a very complicated structure and cannot be done earlier. I need to accept that.

While running those projects you should always finnish your running tasks before using the installer.

Well, I think I've learned that lesson ... LOL

Try Cat 11.2.

Will be done tomorrow before restarting BM.

2) progress bar updated when predefined part of calculation will be finished. Different parts may take different time so sometimes progress bar ticks not every second (it's a waste of resourses and your own time - to make and to watch progress bar tick every second, don't you think so? ;) )

To give you an example: elapsed time shows 1h15min, progress bar shows 0%, remaining time counts down. So, how can I be shure, that the wu's progress?
One GPU crunches two AP-wu's and Afterburner reports 24% GPU usage; my intention is to increase that. The other GPU crunches one AP and one Seti Enhanced @ 96% GPU usage.
Anyway, they finish and validate. So, Let it be.

Alexander

---

Good point Mark.

And point taken. My only plea in mitigation - so many of the people who post here are "SETI first, the rest nowhere" crunchers that the specific needs of other projects can get overlooked. And the vast majority of backup projects do follow standard BOINC practice with regard to checkpointing.

For the next installer version, I'll try and find a balance between v0.37 (which stopped BOINC, or required the user to stop BOINC, right at the very beginning after launch, losing valuable crunching time while you read the setup screens and chose the right set of options), and v0.38 (which delayed stopping BOINC until the last possible moment, to minimise wasted time). I can split the detection phase ('BOINC is running, this is what will happen, back out now if you don't like it') from the action phase ('closing BOINC at the last moment before modifying files'). Something like that?

Will be done tomorrow before restarting BM.

Alexander

Alexander, you do understand that Boinc Manager only monitors and displays what Boinc.exe is doing, don't you?

Opening and closing BM does not stop the crunching processes from running, unless you specify that in the closing popup window.

It's just your window on what is going on in the background.

It's starting and stopping Boinc in the background that affects the running processes.

---

"Time is simply the mechanism that keeps everything from happening all at once."

It's starting and stopping Boinc in the background that affects the running processes.

And it's the background boinc.exe process which has to be stopped and restarted for an application change to take effect.

Maybe Alexander - you're one of the people who closes down their computer overnight and starts it up again in the morning? Then yes - starting the computer first, making the changes, and only then starting BOINC (Manager) should work.

Well,
yes, my mainsys is a 6/16 running system, my integrator is a machine running on demand with different configurations; I have a GTX260 and a GTX460 as replacement GPU's here. Runs sometimes with mixed GPU's.
The only 7/24 is my Flash-PC, which acts as fileserver (running @18W power consumption!!!), crunching Seti and Spinhendge.

Opening and closing BM does not stop the crunching processes from running, unless you specify that in the closing popup window.

THX for that hint; yes, the two boxes are checked. I prefer to have control over my system.

For the next installer version, I'll try ...

I like projects where Admins take care about needs of volunteers! Talking for me, a short notice that crunching must be stopped in order to update would be OK.

CHEERS,

Alexander

---