shows the problem. I manually edit the xml files and set every instance of host_venue to "work". Fire up Boinc, and as the first highlighted line shows, all is well and good.

I then update LHC@home, where I've carefully set up preferences for all locations (including work), but lo-and-behold, Boinc decides that it hates being at work, and wants to go home - see the second highlighted section of text.

So, what do I have to do to explain to Boinc that it should not try to second guess me, and that it should stay with the work configuration?

Thanks.

---

I also have this problem - can there be a function in the manager of "set host venue"? (maybe it is there, but I can't find it, and editing the xml doesn't always seem to work, as described...)

---

I also have this problem - can there be a function in the manager of "set host venue"? (maybe it is there, but I can't find it, and editing the xml doesn't always seem to work, as described...)

Un-smeggin'-believable.

I will admit one thing about the Boinc team. They really have taken to the idea of setting stuff on the web with about the same tenacity as a pitbull.

That being said, go to any of the web sites you are registered with, view your account, hit the view computers link, select the computer by it's link on the left, scroll to the bottom, and there is where you set it.

Arthur Dent's quote from the Hitch-hiker's guide to the galaxy comes to mind:

"I finally found them in the bottom of a locked filing cabinet, in a basement, in a disused lavatory, with a sign on the door saying `Beware of the leopard'. You didn't exactly go out of your way to make them easy to find."

---

I have a related question. It appears that the venue of a computer does not travel between projects. Is there a way to get the venue to travel? (like the preferences do now), or do you just have to "remember" which project you last set the venue in? Or am I missing something altogether?

---

I have a related question. It appears that the venue of a computer does not travel between projects. Is there a way to get the venue to travel? (like the preferences do now), or do you just have to "remember" which project you last set the venue in? Or am I missing something altogether?

The General preference setting venues themselve propagates but you still need to go to the individual projects and identify the venue to use for the computers attached to that project.

---

Boinc V 7.4.36
Win7 i5 3.33G 4GB NVidia 470

This would imply that each project would set and use its own venue. However, within the client_state_prev.xml file, there is only one <host_venue> setting. I believe the computer is set a venue which it behaves across all projects as established by the General Preferences. My question is, why doesn't the computers venue travel between projects, and/or how can I really know which project is the correct one?

---

This would imply that each project would set and use its own venue. However, within the client_state_prev.xml file, there is only one <host_venue> setting.

There's now a separate <host_venue> setting for each project in the account_*.xml file.

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

This would imply that each project would set and use its own venue. However, within the client_state_prev.xml file, there is only one <host_venue> setting.

There's now a separate <host_venue> setting for each project in the account_*.xml file.

This is very interesting, and I did indeed find the venue within the account_*.xml file. The next obvious question is, what venue is the computer using? I guess I could see it using the venue from the project that the workunit is assigned to, but on multiprocessor systems where the computer might be running multiple projects, what venue is being used? Is it really being applied on a project basis?

So, using separate venues for each project I could use the "Do work only between the hours of" setting and do Seti work between the hours of 9-12, Einstein between 10-1, etc. and these settings would not conflict? If it wouldn't disrupt my farm to run this test I would.

---

Just tried to set one project for default and one for school and the new one propagated to the other project, so you can not do it as of now.......

---

BOINC Wiki

Just tried to set one project for default and one for school and the new one propagated to the other project, so you can not do it as of now.......

I have tried this many times, and I suspect that the venue does NOT travel between projects.

I set a computer up with Work venue across Seti, LHC, Rosetta, and Einstein. I let it run for several days. I then changed the Seti venue to be school, and LHC, Rosetta and Einstein all remained set to work.

I'm still confused.

---

Just tried to set one project for default and one for school and the new one propagated to the other project, so you can not do it as of now.......

I have tried this many times, and I suspect that the venue does NOT travel between projects.

I set a computer up with Work venue across Seti, LHC, Rosetta, and Einstein. I let it run for several days. I then changed the Seti venue to be school, and LHC, Rosetta and Einstein all remained set to work.

I'm still confused.

The venue is Computer specific not Project Specific. See Preference Venue. You can have many computer set to a venue, but an individual computer can only use one venue.

---

Boinc V 7.4.36
Win7 i5 3.33G 4GB NVidia 470

Just tried to set one project for default and one for school and the new one propagated to the other project, so you can not do it as of now.......

I have tried this many times, and I suspect that the venue does NOT travel between projects.

I set a computer up with Work venue across Seti, LHC, Rosetta, and Einstein. I let it run for several days. I then changed the Seti venue to be school, and LHC, Rosetta and Einstein all remained set to work.

I'm still confused.

The venue is Computer specific not Project Specific. See Preference Venue. You can have many computer set to a venue, but an individual computer can only use one venue.

I understand that. However, I would expect a single computer to have the same venue across all projects. If I change the venue for computer A on project Seti from Work to School, I would expect the venue on LHC to also change to School after computer A first updated from Seti and then later contacted LHC. Is this not correct? However, this is not what I am seeing.

---

Boinc uses the General preference from the last project where there was a change, once that project has been contacted. I've noticed some latency on all the projects syncing up (sometime days), some projects are very slow at getting the newest updated General preferences. I presume this will get worse as more new projects come on line. I haven't personally checked specifically what is happening as far as venues are concerned.

---

Boinc V 7.4.36
Win7 i5 3.33G 4GB NVidia 470

Boinc uses the General preference from the last project where there was a change, once that project has been contacted. I've noticed some latency on all the projects syncing up (sometime days), some projects are very slow at getting the newest updated General preferences. I presume this will get worse as more new projects come on line. I haven't personally checked specifically what is happening as far as venues are concerned.

I understand that general preferences get update from project to project through the users computer. What I am asking about is how does a specific computers venue travel? I believe it leads to undesireable results if it does not.

---

Boinc uses the General preference from the last project where there was a change, once that project has been contacted.

I understand that general preferences get update from project to project through the users computer. What I am asking about is how does a specific computers venue travel? I believe it leads to undesireable results if it does not.

When Boinc on your computer contacts any project server (do do some uploads or downloads etc.), it asks the server for any changes in the preferences and tells recent changes, obtained from other projects. This way the recent changes traverse the way Project1 -> ComputerA -> Project2..n, possibly slowly (if some projects have rather small resource share and your computer(s) contact them rarely), but predictively.

The same is true for computers venue, if you change your ComputerA's venue on Project1, as far as CompA contacts Proj1, it will begin to behave according to this venue and tell all other projects, which it will later contact, that it is now under such venue.

Peter

Actually I think I have it figured out now.

There is a concept of "Source Project". This happens to be the last project you ever made a change to within the General Preferences section. For instance, if you have 3 projects Seti, Rosetta, LHC. And open LHC and change the number of “multiprocessors, use at most” from say, 30 to 31, then LHC will become the feed point (Source Project) for the venues for ALL computers that are attached to LHC.

A detailed example: If I have 2 computers (A, B), and 2 projects Seti, LHC;

If the venues for each project are set as follows
Comp A - Seti - Home, LHC - Work.
Comp A - Seti - Home, LHC - Work.

Let's say that Seti was the last project that had made a General Preferences change to, so both computers are using Home as the venue, and I am happy with this. Both, Seti and LHC would indeed be using Home to derive its General Preferences from, and indeed since Seti was the last to have a change, the Seti General Preferences will show up in LHC General Preferences and the General Preferences will all match.

Now let's say I want to make a change to the Home General Preferences to leave the applications in memory. But let's say I forgot which project was the "driver". If I open LHC, and make a change to the Home General Preferences and close it, I have started a chain reaction with some very undesirable results.

When A and B eventually contact LHC, their venue will switch from Home to Work. (NOT WHAT I WANTED) because the venues in LHC was Work for each computer and now LHC is the "Source Project".

So the result is that both computers are now using Work as their venue, which I may or may not have properly set up. What I wanted was the change I made to Home to propagate across all projects (which it will), but I did NOT want the venues for the computers to switch to Work.

---

Actually I think I have it figured out now.

There is a concept of "Source Project". This happens to be the last project you ever made a change to within the General Preferences section. For instance, if you have 3 projects Seti, Rosetta, LHC. And open LHC and change the number of “multiprocessors, use at most” from say, 30 to 31, then LHC will become the feed point (Source Project) for the venues for ALL computers that are attached to LHC.

A detailed example: If I have 2 computers (A, B), and 2 projects Seti, LHC;

If the venues for each project are set as follows
Comp A - Seti - Home, LHC - Work.
Comp A - Seti - Home, LHC - Work.

Let's say that Seti was the last project that had made a General Preferences change to, so both computers are using Home as the venue, and I am happy with this. Both, Seti and LHC would indeed be using Home to derive its General Preferences from, and indeed since Seti was the last to have a change, the Seti General Preferences will show up in LHC General Preferences and the General Preferences will all match.

According to this, ATM, the venues will be set as follows, to really match:
Comp A - Seti - Home, LHC - Home.
Comp B - Seti - Home, LHC - Home.

Now let's say I want to make a change to the Home General Preferences to leave the applications in memory. But let's say I forgot which project was the "driver".

This does not matter, as they already do match.

If I open LHC, and make a change to the Home General Preferences and close it, I have started a chain reaction with some very undesirable results.

When A and B eventually contact LHC, their venue will switch from Home to Work. (NOT WHAT I WANTED) because the venues in LHC was Work for each computer and now LHC is the "Source Project".

So the result is that both computers are now using Work as their venue

This might happen if no one of the A or B computers, which already contacted Seti after the 'Home' modification, had passed the 'change' news to LHC yet. So if LHC would still think that A and B belong to Work and you would modify (Work? or Home? you did not tell in your scenario) from 30 to 31 processors, the next time A or B would contact LHC, they would notice the preferences at LHC are more recent than at Seti.

(To be exact, I don't know wherher ALL preferences are propagated en block or single venues are propagated and timely-compared as single units. I suppose all together.)

So, Mike, it's not that much difficult and dangerous like the way you figured out. You have only to take care or confirm that any of the computers, which already contacted the "Source" project, also 'talked' to one of the "Target" projects afterwards, which you'd like to modify. Which mostly happens after few days automatically.

Peter

Peter

Actually I think I have it figured out now.

If the venues for each project are set as follows
Comp A - Seti - Home, LHC - Work.
Comp A - Seti - Home, LHC - Work.

According to this, ATM, the venues will be set as follows, to really match:
Comp A - Seti - Home, LHC - Home.
Comp B - Seti - Home, LHC - Home.

This is exactly what I am trying to point out. The fact that Seti and LHC differ in what a specific computer venue is, is allowed and NOT updated from the source project. Only the venue settings (General Preferences) are update from project to project.

Now let's say I want to make a change to the Home General Preferences to leave the applications in memory. But let's say I forgot which project was the "driver".

This does not matter, as they already do match.

No they wont.

(To be exact, I don't know wherher ALL preferences are propagated en block or single venues are propagated and timely-compared as single units. I suppose all together.)

They go in a block with a single date to figure out which is the source project.

Mike

---

Actually I think I have it figured out now.

If the venues for each project are set as follows
Comp A - Seti - Home, LHC - Work.
Comp A - Seti - Home, LHC - Work.

According to this, ATM, the venues will be set as follows, to really match:
Comp A - Seti - Home, LHC - Home.
Comp B - Seti - Home, LHC - Home.

This is exactly what I am trying to point out. The fact that Seti and LHC differ in what a specific computer venue is, is allowed and NOT updated from the source project. Only the venue settings (General Preferences) are update from project to project.

Hmmmmm... Probably some of the LHC folks should comment on this. I'm out of ideas :-(

Peter

Actually I think I have it figured out now.

If the venues for each project are set as follows
Comp A - Seti - Home, LHC - Work.
Comp A - Seti - Home, LHC - Work.

According to this, ATM, the venues will be set as follows, to really match:
Comp A - Seti - Home, LHC - Home.
Comp B - Seti - Home, LHC - Home.

This is exactly what I am trying to point out. The fact that Seti and LHC differ in what a specific computer venue is, is allowed and NOT updated from the source project. Only the venue settings (General Preferences) are update from project to project.

Hmmmmm... Probably some of the LHC folks should comment on this. I'm out of ideas :-(

Peter

It's not LHC specific, its ANY BOINC projects

---