Messages

They are testing sub-second throttling in the alpha test versions of BOINC at the moment.

Dr A finally realised that the wrapper app they provide only updates once a second, so they've given up on the sub-second throttling.

I have my computers setup into 3 groups. I have Nvidia GPU's, Intel GPU's and Raspberry Pi's. In the left hand pane it shows each group and I can expand or collapse the tree showing the individual computers. I can't however see the whole lot in one go on the tasks tab or project tabs. I have to select each group. It defaults at startup to the first one (Intel GPU's).

Would it be possible to show all, or to be able to have groups within groups?

Another alternative could be an overview tab that shows stats for the farm as a whole, but doesn't go into detail, perhaps a total of tasks by state (uploading, running, etc)

Related to the old SETI programs there is a proposal for SuperHost which would have similar functionality to the SetiGate and SetiQueue programs. The proposed design ideas can be found at http://boinc.berkeley.edu/trac/wiki/SuperHost

Maybe if Fred wants a new project to look at 

They are testing sub-second throttling in the alpha test versions of BOINC at the moment. I don't know if Fred would mind offering code to the BOINC developers so they could integrate temperature based throttling into the BOINC client. Dr A keeps saying its difficult to find code to obtain the temperature of the CPU and GPU.

There was SETIqueue as well which was quite popular. Unfortunately there is nothing similar for BOINC.

It seems (after a bit of experimenting) that you can skip step 2 and leave gui_rpc_auth.cfg blank. That way you don't need a password.

[Setting up BoincTasks talking to a Raspberry Pi]

Setting up BoincTasks talking to a Raspberry Pi

BoincTasks is designed to monitor a number of machines. Unfortunately its a Windows app and so getting it talking to the Raspberry Pi's is not the simplest of things to do. I assume that you've managed to get BOINC running on the Pi and BoincTasks (BT) is also running on your Windows PC. I also assume they are on the same router.

1. On the Pi you'll need to put the IP address and host name of the BT machine into /etc/hosts

2. On the Pi you'll need to put a password into /var/lib/boinc-client/gui_rpc_auth.cfg

3. On the Pi you'll need to put the host name of the BT machine into /var/lib/boinc-client/remote_hosts.cfg

4. Restart the Pi to pick up the above changes

5. In BT (on your PC) you need to add the Pi. Click on the Computers tab and then on the Menu Bar Computers -> Add Computer. You need to use the IP address (not the host name) of the Pi and the password from point 2.


Points to note:
• If you installed the boinc-manager on the Pi it will no longer be able to connect to the boinc-client. This is because it doesn't know the password. You can execute it manually and supply the password from a command prompt if you still want to use it, but you now have BT working so why would you need it?

• The Pi is invisible to the windows PC's on the network. The router will usually be able to see all of them but the windows machines only show other windows machines. The Pi's don't seem to have visibility of anything else on the network.

• Due to the 2nd point the Pi needs to have the IP address and host name of the BT machine in the hosts file. This is not good practice as IP addresses can and do frequently change.

Hi Fred,

It seem Dr A has removed the <zero_debts> <std_debug> and <debt_debug> flags from the cc_config file from client versions 7.0.27 onwards.    He has also added <suspend_debug> again from 7.0.27 onwards.

Is it possible to include these changes in the BT 1.31 that you are working on, or some later version please.

The message thread discussing these over at Seti is Here

Cheers,
MarkJ

I notice the project properties don't match the manager, specifically the Nvidia and CPU back off times don't seem to show in BT.

If the client doesn't get work for a specific resource (ie ATI, CPU or Nvidia) it will back off in 10 minute increments for that resource type. This is seperate to the normal project requested "comms deferred" time and any file transfer back offs. The only place I recall seeing it is on the project properties.

It probably something thats been changed in the 7.x clients. Client is a Win7 x64 machine running 7.0.25. I'll email the screen shots as I don't seem able to attach them to this message.

Using BT 1.30 with BOINC 7.0.25 clients. When the client machine makes a scheduler request it doesn't show in BT. The status column remains blank, but in the BOINC manager it shows as "Schedule request in progress, etc". I noticed because the SETI ones were taking a long time to complete yesterday and in a few cases even timing out.

All machines are running Win7 x64

Yes I have had a smililar issue.

Also running BT (1.16) on a laptop without BOINC. Clients are all 6.12.34 (and one 7.0.6). All running Win7 x64. Usually happens if a machines is off/not running BOINC and then I bring it back online. The computers tab shows it as connected, but nothing in other tabs for it. A restart of BT seems to fix it.

As for upgrading BT to 1.25 that had another problem. I will start a separate thread about that.

This may also be fixed in 1.30.

It certainly seems to be fixed in 1.30. I still have the occasional drop out (where a connected computer seems to drop off), but it seems to come back on the next refresh.

I have upgraded to 1.30 and that seems to have resolved it.

I did try uninstalling 1.16 so that I only had a computers.xml file and then installing 1.25 so there shouldn't have been anything to convert. Also it repeatedly took 20+ seconds start up, not just the first time. Anyway no point worrying about it now as 1.30 seems to fix it. Perhaps its time to make 1.30 the recommended version?

So here's the scenerio... Happily running BT 1.16 on a laptop with win7 x64. I do the upgrade to BT 1.25. No problems until I click on the icon to start it. It takes 22 seconds to come up. Now 1.16 was there within 1 second, but 22 seconds to start up? And no its not in power saving mode. I can exit BT and restart it and its still around the 22 seconds startup time.

Checked www and webserver options and both are unchecked. Same for History logging (unchecked).

Yes I have had a smililar issue.

Also running BT (1.16) on a laptop without BOINC. Clients are all 6.12.34 (and one 7.0.6). All running Win7 x64. Usually happens if a machines is off/not running BOINC and then I bring it back online. The computers tab shows it as connected, but nothing in other tabs for it. A restart of BT seems to fix it.

As for upgrading BT to 1.25 that had another problem. I will start a separate thread about that.

Yep, i'd like to run an iPad version of it 
Fred and I have discussed this via email and he is thinking of using the html files to be able to do this.

My take on that is it would be too slow as you'd have to get the html file onto a sever to display the page every 6 or so seconds, which would be a lot of overhead. You would also need to have a web server running to do it.

I was thinking along the lines of a stripped-down BT as the iPad isn't the fastest piece of hardware around.  It would need to get ported so it could run as an iPad app. While I am not an iPad developer I might be able to find one to do the work.