Welcome to the MacNN Forums.

Mr Zippy · Sep 15, 2004, 07:15 PM

I have downloaded the optimised BOINC + SETI worker package for G4 7450 and the BOINC benchmark is excellent.

But when I run BOINC and setup my SETI account it just downloads and uses SETI 4.02 worker from the SETI servers.

How do I get BOINC to use the optimized SETI worker.

Thanks

Neil

Benchmarks
=======

Actual Processor G4 7455x2
==========================

BOINC 4.05

Number of CPUs: 2
570 double precision MIPS (Whetstone) per CPU
1340 integer MIPS (Dhrystone) per CPU

**********************************************

BOINC 4.06 G4 7450 optimized

Number of CPUs: 2
1757 double precision MIPS (Whetstone) per CPU
1973 integer MIPS (Dhrystone) per CPU

mikkyo · Sep 15, 2004, 08:47 PM

You need the app_info.xml file in your projects/setiathome.berkeley.edu/ directory with the optimized worker.
The app_info.xml must also have the correct name of the worker inside it.
This is why those files are provided with the workers.

Mr Zippy · Sep 15, 2004, 09:08 PM

Ah it works now, must have deleted it when I tried to transfer my current work unit to the new version.

I take it it's normal to fail any work unit you try and transfer?

It has downloaded a new unit and is processing with SETI worker 4.30 now

2004-09-16 03:05:12 [---] Starting BOINC client version 4.06 for powerpc-apple-darwin
2004-09-16 03:05:12 [SETI@home] Project prefs: no separate prefs for home; using your defaults
2004-09-16 03:05:12 [SETI@home] Found app_info.xml; using anonymous platform
2004-09-16 03:05:12 [SETI@home] WU refers to nonexistent app_version: setiathome 402
2004-09-16 03:05:12 [SETI@home] WU refers to nonexistent app_version: setiathome 402
2004-09-16 03:05:12 [SETI@home] Can't link workunit in state file
2004-09-16 03:05:12 [SETI@home] Can't link workunit in state file
2004-09-16 03:05:12 [SETI@home] WU refers to nonexistent app_version: setiathome 402
2004-09-16 03:05:12 [SETI@home] WU refers to nonexistent app_version: setiathome 402
2004-09-16 03:05:12 [SETI@home] Can't link workunit in state file
2004-09-16 03:05:12 [SETI@home] Can't link workunit in state file
2004-09-16 03:05:12 [SETI@home] WU refers to nonexistent app_version: setiathome 402
2004-09-16 03:05:12 [SETI@home] WU refers to nonexistent app_version: setiathome 402
2004-09-16 03:05:12 [SETI@home] Can't link workunit in state file
2004-09-16 03:05:12 [SETI@home] Can't link workunit in state file
2004-09-16 03:05:12 [SETI@home] WU refers to nonexistent app_version: setiathome 402
2004-09-16 03:05:12 [SETI@home] WU refers to nonexistent app_version: setiathome 402
2004-09-16 03:05:12 [SETI@home] Can't link workunit in state file
2004-09-16 03:05:12 [SETI@home] Can't link workunit in state file
2004-09-16 03:05:12 [SETI@home] link_result: nonexistent WU 06my04ab.10554.12465.667316.225
2004-09-16 03:05:12 [SETI@home] link_result: nonexistent WU 06my04ab.10554.12465.667316.225
2004-09-16 03:05:12 [SETI@home] Can't link result 06my04ab.10554.12465.667316.225_2 in state file
2004-09-16 03:05:12 [SETI@home] Can't link result 06my04ab.10554.12465.667316.225_2 in state file
2004-09-16 03:05:12 [SETI@home] link_result: nonexistent WU 06my04ab.10554.12465.667316.223
2004-09-16 03:05:12 [SETI@home] link_result: nonexistent WU 06my04ab.10554.12465.667316.223
2004-09-16 03:05:12 [SETI@home] Can't link result 06my04ab.10554.12465.667316.223_2 in state file
2004-09-16 03:05:12 [SETI@home] Can't link result 06my04ab.10554.12465.667316.223_2 in state file
2004-09-16 03:05:12 [SETI@home] link_result: nonexistent WU 06my04ab.10554.12560.1047142.24
2004-09-16 03:05:12 [SETI@home] link_result: nonexistent WU 06my04ab.10554.12560.1047142.24
2004-09-16 03:05:12 [SETI@home] Can't link result 06my04ab.10554.12560.1047142.24_1 in state file
2004-09-16 03:05:12 [SETI@home] Can't link result 06my04ab.10554.12560.1047142.24_1 in state file
2004-09-16 03:05:12 [SETI@home] link_result: nonexistent WU 06my04ab.10554.12560.1047142.23
2004-09-16 03:05:12 [SETI@home] link_result: nonexistent WU 06my04ab.10554.12560.1047142.23
2004-09-16 03:05:12 [SETI@home] Can't link result 06my04ab.10554.12560.1047142.23_0 in state file
2004-09-16 03:05:12 [SETI@home] Can't link result 06my04ab.10554.12560.1047142.23_0 in state file
2004-09-16 03:05:12 [SETI@home] ACTIVE_TASK:

arse(): result not found
2004-09-16 03:05:12 [SETI@home] ACTIVE_TASK:

arse(): result not found
2004-09-16 03:05:12 [SETI@home] Host ID is 181026
2004-09-16 03:05:12 [---] General prefs: from SETI@home (last modified 2004-06-25 01:45:45)
2004-09-16 03:05:12 [---] General prefs: no separate prefs for home; using your defaults
2004-09-16 03:05:12 [---] Insufficient work; requesting more

mikkyo · Sep 15, 2004, 10:55 PM

Work units are dished out for specific platforms.
So your work from another different install without a custom seti worker is not valid when run with the custom worker.
New worker, new work.
If you care about the old workunits, you need to finish them on the original install.
You can see the errors in the log say that the work unit is looking for the setiathome 402 worker.

Mr Zippy · Sep 16, 2004, 07:13 AM

Ah I follow now, was very late last night when I was looking at it.

The old work units are deleted now, I am right in thinking SETI keeps track of results it does not get back?

I am very impressed with the optimised compile of BONIC and the SETI worker.

Neil