Upgrading to BOINC V7


log in

Advanced search

Message boards : Number crunching : Upgrading to BOINC V7

Author Message
Price Family - Brighton
Send message
Joined: 4 Nov 00
Posts: 29
Credit: 8,046,992
RAC: 12,502
United Kingdom
Message 1373435 - Posted: 30 May 2013, 10:51:50 UTC

I'm currently running BOINC V6.10.60 and since midnight I've been getting a message saying "A newer BOINC may be required for some tasks".

I think this means that if I want to keep running SETI (apart from resends) I must upgrade. Is this correct?

If so, I seem to remember that back in the early days of BOINC V7 there were issues with the upgrade from V6 and existing tasks. I think its was something to do with FLOPS being different causing the existing tasks to time out. Is this still a problem?

If it is still a problem, would the following steps overcome it:

Suspending my tasks.
Manually changing the current FLOP values (wherever they are stored).
Upgrading.
Restarting the tasks.

Are there other issues that I should be aware of?

Normally I would just let my tasks drain before upgrading but I'm away for the next 5 days so BOINC will be running on empty at some time. Not a major issue, so you can tell me to bite the bullet and drain!

Rick
____________

Grant (SSSF)
Send message
Joined: 19 Aug 99
Posts: 5566
Credit: 51,587,784
RAC: 44,229
Australia
Message 1373450 - Posted: 30 May 2013, 11:14:28 UTC - in response to Message 1373435.

If so, I seem to remember that back in the early days of BOINC V7 there were issues with the upgrade from V6 and existing tasks.

That relates to BOINC- the manager.

The present upgrage is about the applications that actualy do the processing.
If you run the stock applications, all you need to do is go to your account, Seti preferences & enable v7 processing, save the changes & it will take care of itself.
If you're running an optimised version, then things will be somewhat more complicated.


____________
Grant
Darwin NT.

Richard Haselgrove
Volunteer tester
Send message
Joined: 4 Jul 99
Posts: 8276
Credit: 45,013,706
RAC: 13,687
United Kingdom
Message 1373462 - Posted: 30 May 2013, 11:27:00 UTC

Some of the new applications released last night - those for AMD/ATI GPUs - rely on the OpenCL language. BOINC v6.10 can't process OpenCL properly, so you are being warned that you can't run those ATI apps currently.

One of your computers - ID 5744267 - has an ATI card, but because your old version of BOINC doesn't detect it properly, I can't tell if it's a model which can be used for SETI with the new applications.

If you want to experiment with GPU computing, you should probably upgrade directly to BOINC v7.0.64 - but there's no rush, your computers will continue to run as you normally do, using the CPUs only for Multibeam and doing Astropulse on the GPU. Wait until the rush and chaos of this launch have calmed down a bit.

Price Family - Brighton
Send message
Joined: 4 Nov 00
Posts: 29
Credit: 8,046,992
RAC: 12,502
United Kingdom
Message 1373559 - Posted: 30 May 2013, 16:21:09 UTC - in response to Message 1373450.

That relates to BOINC- the manager.


I thought the message "A newer BOINC may be required for some tasks" was telling me I had to upgrade BOINC to run SETI@home V7.

But if you're saying that I can run it from BOINC 6.10.60 that's grand. I've now enabled the new SETI version so we'll see what happens.

Thanks


____________

Price Family - Brighton
Send message
Joined: 4 Nov 00
Posts: 29
Credit: 8,046,992
RAC: 12,502
United Kingdom
Message 1373573 - Posted: 30 May 2013, 16:50:47 UTC - in response to Message 1373462.

Thanks for the reply. It is a bit confusing that the ATI card is not recognised by BOINC. In fact I've been running Astropulse v6 GUI apps under V6.10.60 for some time.

I decided to give the card a try when I spotted that SETI@home now provide this feature for ATI cards directly. I.e. without having to download and configure any of the special apps. So I knew that either the card would work or it wouldn't, without me thinking I'd set things up wrongly. How good is that!

Rick.

Some of the new applications released last night - those for AMD/ATI GPUs - rely on the OpenCL language. BOINC v6.10 can't process OpenCL properly, so you are being warned that you can't run those ATI apps currently.

One of your computers - ID 5744267 - has an ATI card, but because your old version of BOINC doesn't detect it properly, I can't tell if it's a model which can be used for SETI with the new applications.

If you want to experiment with GPU computing, you should probably upgrade directly to BOINC v7.0.64 - but there's no rush, your computers will continue to run as you normally do, using the CPUs only for Multibeam and doing Astropulse on the GPU. Wait until the rush and chaos of this launch have calmed down a bit.


____________

Profile Ageless
Avatar
Send message
Joined: 9 Jun 99
Posts: 12130
Credit: 2,525,019
RAC: 653
Netherlands
Message 1373579 - Posted: 30 May 2013, 17:02:26 UTC - in response to Message 1373573.

It is a bit confusing that the ATI card is not recognised by BOINC.

BOINC can only recognize GPUs that it has code for in its source code. With newer versions of BOINC this code gets added to, adapted, made better. Earlier versions of BOINC therefore cannot recognize the newest AMD GPUs, they'll call them ATI Unknown.

If you want your GPU to be fully recognized, the only way up is to update BOINC.

____________
Jord

Loving awareness is free.

Profile Gundolf Jahn
Send message
Joined: 19 Sep 00
Posts: 3184
Credit: 355,077
RAC: 24
Germany
Message 1373625 - Posted: 30 May 2013, 17:33:27 UTC - in response to Message 1373559.

But if you're saying that I can run it from BOINC 6.10.60 that's grand.

It's even running with BOINC 5.10.45 on my win XP laptop.

(No chance for 5.8.16 on win NT4 though ;-)

Gruß,
Gundolf

Ulrich Metzner
Volunteer tester
Avatar
Send message
Joined: 3 Jul 02
Posts: 956
Credit: 7,031,310
RAC: 12,215
Germany
Message 1373855 - Posted: 30 May 2013, 22:10:24 UTC

That's a very good question:
Where do i get a client for seti V7?
I use optimized clients all the time, but where to get a V7.0 one?
I don't have a clue, except to run a client plain, to get it from Seti server... :?
____________
Aloha, Uli

Profile bj
Send message
Joined: 11 Oct 00
Posts: 163
Credit: 50,429,449
RAC: 0
United States
Message 1373946 - Posted: 31 May 2013, 2:49:02 UTC

<app_info>
<app>
<name>setiathome_v7</name>
</app>
<file_info>
<name>setiathome_7.00_windows_intelx86.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>setiathome_7.00_windows_intelx86.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>setiathome_7.00_windows_intelx86.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>AK_v8b2_win_x64_SSE3.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>AK_v8b2_win_x64_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>603</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>AK_v8b2_win_x64_SSE3.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v6</name>
</app>
<file_info>
<name>AP6_win_x86_SSE_CPU_r555.exe</name>
<executable/>
</file_info>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>AP6_win_x86_SSE_CPU_r555.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v6</app_name>
<version_num>601</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>AP6_win_x86_SSE_CPU_r555.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>astropulse_v505</name>
</app>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<platform>windows_intelx86</platform>
<cmdline>-v505</cmdline>
<file_ref>
<file_name>AP6_win_x86_SSE_CPU_r555.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app_version>
<app_name>astropulse_v505</app_name>
<version_num>505</version_num>
<platform>windows_x86_64</platform>
<cmdline>-v505</cmdline>
<file_ref>
<file_name>AP6_win_x86_SSE_CPU_r555.exe</file_name>
<main_program/>
</file_ref>
</app_version>
<app>
<name>setiathome_enhanced</name>
</app>
<file_info>
<name>Lunatics_x41g_win32_cuda32.exe</name>
<executable/>
</file_info>
<file_info>
<name>cudart32_32_16.dll</name>
<executable/>
</file_info>
<file_info>
<name>cufft32_32_16.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_intelx86</platform>
<plan_class>cuda_fermi</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>609</version_num>
<platform>windows_intelx86</platform>
<plan_class>cuda23</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_intelx86</platform>
<plan_class>cuda</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>610</version_num>
<platform>windows_x86_64</platform>
<plan_class>cuda_fermi</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>609</version_num>
<platform>windows_x86_64</platform>
<plan_class>cuda23</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_enhanced</app_name>
<version_num>608</version_num>
<platform>windows_x86_64</platform>
<plan_class>cuda</plan_class>
<avg_ncpus>0.040000</avg_ncpus>
<max_ncpus>0.040000</max_ncpus>
<coproc>
<type>CUDA</type>
<count>1</count>
</coproc>
<file_ref>
<file_name>Lunatics_x41g_win32_cuda32.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>cudart32_32_16.dll</file_name>
</file_ref>
<file_ref>
<file_name>cufft32_32_16.dll</file_name>
</file_ref>
</app_version>
</app_info>

I added the above to the app_info.xml but now get this message in the event log:

5/30/2013 9:32:44 PM | | No config file found - using defaults
5/30/2013 9:32:44 PM | | Starting BOINC client version 7.0.64 for windows_x86_64
5/30/2013 9:32:44 PM | | log flags: file_xfer, sched_ops, task
5/30/2013 9:32:44 PM | | Libraries: libcurl/7.25.0 OpenSSL/1.0.1 zlib/1.2.6
5/30/2013 9:32:44 PM | | Data directory: C:\ProgramData\BOINC
5/30/2013 9:32:44 PM | | Running under account bj2
5/30/2013 9:32:44 PM | | Processor: 8 GenuineIntel Intel(R) Core(TM) i7 CPU 920 @ 2.67GHz [Family 6 Model 26 Stepping 4]
5/30/2013 9:32:44 PM | | Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss htt tm pni ssse3 cx16 sse4_1 sse4_2 popcnt syscall nx lm vmx tm2 pbe
5/30/2013 9:32:44 PM | | OS: Microsoft Windows 7: Ultimate x64 Edition, Service Pack 1, (06.01.7601.00)
5/30/2013 9:32:44 PM | | Memory: 5.99 GB physical, 11.98 GB virtual
5/30/2013 9:32:44 PM | | Disk: 111.79 GB total, 93.01 GB free
5/30/2013 9:32:44 PM | | Local time is UTC -5 hours
5/30/2013 9:32:44 PM | | CUDA: NVIDIA GPU 0: GeForce GTX 460 SE (driver version 320.18, CUDA version 5.50, compute capability 2.1, 1024MB, 948MB available, 746 GFLOPS peak)
5/30/2013 9:32:44 PM | | OpenCL: NVIDIA GPU 0: GeForce GTX 460 SE (driver version 320.18, device version OpenCL 1.1 CUDA, 1024MB, 948MB available, 746 GFLOPS peak)
5/30/2013 9:32:44 PM | SETI@home | Found app_info.xml; using anonymous platform
5/30/2013 9:32:44 PM | SETI@home | File referenced in app_info.xml does not exist: setiathome_7.00_windows_intelx86.exe
5/30/2013 9:32:44 PM | SETI@home | [error] State file error: missing application file setiathome_7.00_windows_intelx86.exe
5/30/2013 9:32:44 PM | SETI@home | [error] State file error: missing application file setiathome_7.00_windows_intelx86.exe
5/30/2013 9:32:44 PM | SETI@home | URL http://setiathome.berkeley.edu/; Computer ID 6619276; resource share 100
5/30/2013 9:32:44 PM | SETI@home | General prefs: from SETI@home (last modified 24-Aug-2012 06:33:45)
5/30/2013 9:32:44 PM | SETI@home | Computer location: home
5/30/2013 9:32:44 PM | SETI@home | General prefs: no separate prefs for home; using your defaults
5/30/2013 9:32:44 PM | | Preferences:
5/30/2013 9:32:44 PM | | max memory usage when active: 3067.56MB
5/30/2013 9:32:44 PM | | max memory usage when idle: 5521.61MB
5/30/2013 9:32:44 PM | | max disk usage: 55.89GB
5/30/2013 9:32:44 PM | | (to change preferences, visit a project web site or select Preferences in the Manager)
5/30/2013 9:32:44 PM | | Using proxy info from GUI
5/30/2013 9:32:44 PM | | Not using a proxy
5/30/2013 9:32:44 PM | SETI@home | Restarting task ap_29ja10aa_B0_P0_00011_20130530_22560.wu_1 using astropulse_v6 version 601 in slot 6
5/30/2013 9:32:44 PM | SETI@home | Restarting task ap_29ja10aa_B2_P1_00081_20130530_12462.wu_0 using astropulse_v6 version 601 in slot 2
5/30/2013 9:32:44 PM | SETI@home | Restarting task ap_13ap11aa_B2_P1_00227_20130505_12598.wu_2 using astropulse_v6 version 601 in slot 4
5/30/2013 9:32:44 PM | SETI@home | Restarting task ap_29ja10aa_B1_P1_00118_20130530_12362.wu_1 using astropulse_v6 version 601 in slot 5
5/30/2013 9:32:44 PM | SETI@home | Restarting task ap_29ja10aa_B2_P1_00118_20130530_12462.wu_0 using astropulse_v6 version 601 in slot 8
5/30/2013 9:35:47 PM | SETI@home | Sending scheduler request: To fetch work.
5/30/2013 9:35:47 PM | SETI@home | Requesting new tasks for CPU and NVIDIA
5/30/2013 9:35:49 PM | SETI@home | Scheduler request completed: got 0 new tasks
5/30/2013 9:35:49 PM | SETI@home | No tasks sent
5/30/2013 9:35:49 PM | SETI@home | No tasks are available for SETI@home Enhanced
5/30/2013 9:35:49 PM | SETI@home | No tasks are available for Astropulse v505
5/30/2013 9:35:49 PM | SETI@home | No tasks are available for SETI@home v7
5/30/2013 9:35:49 PM | SETI@home | No tasks are available for AstroPulse v6
5/30/2013 9:35:49 PM | SETI@home | [b]Message from server: Your app_info.xml file doesn't have a usable version of SETI@home v7.[/b]


This computer has only five tasks left. not getting new work. What do I need to do to get the V7 tasks?

Have three others but seem to be getting work yet.

Got to get to bed now so will be able to get back in the morning.

bj
WØBJH

____________

Wedge009
Volunteer tester
Avatar
Send message
Joined: 3 Apr 99
Posts: 237
Credit: 108,604,071
RAC: 201,697
Australia
Message 1373953 - Posted: 31 May 2013, 3:13:04 UTC

You'll need to copy setiathome_7.00_windows_intelx86.exe into your setiathome.berkeley.edu projects folder, where the app_info.xml is.
____________
Soli Deo Gloria

Profile bj
Send message
Joined: 11 Oct 00
Posts: 163
Credit: 50,429,449
RAC: 0
United States
Message 1373960 - Posted: 31 May 2013, 3:33:43 UTC - in response to Message 1373953.

[quote]You'll need to copy setiathome_7.00_windows_intelx86.exe into your setiathome.berkeley.edu projects folder, where the app_info.xml is.[/q

OK> Where would I get this .exe at?

Would this be applicable to the XP computers?

Been trying to keep up with all the news but seems like there are alot of conflicting info.

Thanks
____________

zoom314
Avatar
Send message
Joined: 30 Nov 03
Posts: 44596
Credit: 35,456,417
RAC: 9,013
Message 1373977 - Posted: 31 May 2013, 4:14:17 UTC - in response to Message 1373960.

[quote]You'll need to copy setiathome_7.00_windows_intelx86.exe into your setiathome.berkeley.edu projects folder, where the app_info.xml is.[/q

OK> Where would I get this .exe at?

Would this be applicable to the XP computers?

Been trying to keep up with all the news but seems like there are alot of conflicting info.

Thanks

If you have no app_info.xml file where your data is stored at, then boinc should download what you need for you.
____________

Wedge009
Volunteer tester
Avatar
Send message
Joined: 3 Apr 99
Posts: 237
Credit: 108,604,071
RAC: 201,697
Australia
Message 1374040 - Posted: 31 May 2013, 6:51:12 UTC

That's right - BOINC will download all the necessary files for you under normal circumstances. If you're configuring an app_info.xml, then you have to do everything manually.
____________
Soli Deo Gloria

msattler
Volunteer tester
Avatar
Send message
Joined: 9 Jul 00
Posts: 37453
Credit: 502,443,324
RAC: 569,882
United States
Message 1374043 - Posted: 31 May 2013, 6:54:50 UTC

I simply renamed my app_info.xml to app_info.sav in case I would ever want to refer to it in the future. Then I restarted Boinc, which ditched all tasks left in cache due to the app references not being there.
The did the 'reset project', and things took off OK from there.
Except for the problem downloading the new app files.
Which I think, are mostly out of the way now.
____________
******************
Just a kittyman kinda guy.

Crunching Seti, loving all of God's kitties.

I have met a few friends in my life.
Most were cats.

Mark Lybeck
Send message
Joined: 9 Aug 99
Posts: 209
Credit: 84,624,869
RAC: 112,813
Finland
Message 1374858 - Posted: 1 Jun 2013, 16:56:20 UTC

Hello,

For all those who actually like to configure the anonymous platform there is an alternative way to downloading the applications than removing temporarily the app_info.xml file.

Just use your browser to download the needed files to your setiathome.berkeley.edu project folder:

http://boinc2.ssl.berkeley.edu/sah/download_fanout/setiathome_7.00_windows_intelx86.exe
http://boinc2.ssl.berkeley.edu/sah/download_fanout/libfftw3f-3-3_upx.dll

The app_info should be amended as follows:
<app>
<name>setiathome_v7</name>
</app>
<file_info>
<name>setiathome_7.00_windows_intelx86.exe</name>
<executable/>
</file_info>
<file_info>
<name>libfftw3f-3-3_upx.dll</name>
<executable/>
</file_info>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_intelx86</platform>
<file_ref>
<file_name>setiathome_7.00_windows_intelx86.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-3_upx.dll</file_name>
</file_ref>
</app_version>
<app_version>
<app_name>setiathome_v7</app_name>
<version_num>700</version_num>
<platform>windows_x86_64</platform>
<file_ref>
<file_name>setiathome_7.00_windows_intelx86.exe</file_name>
<main_program/>
</file_ref>
<file_ref>
<file_name>libfftw3f-3-3_upx.dll</file_name>
</file_ref>
</app_version>

____________

Message boards : Number crunching : Upgrading to BOINC V7

Copyright © 2014 University of California