Unless you installed the previous science application through the anonymous platform -highly unlikely on an Android device- the Seti applications will update automatically.

Cause Mateusz SETI MultiBeam v7 app faster than stock, compatible with more types of Android devices and comes with NativeBOINC that still more convenient than stock... I would say it's quite likely thing - Anonymous platform under Android.

Not if the person just installed BOINC from the Google Play Store, be it Berkeley BOINC or NativeBOINC. In both you'll have to add the project in the normal way through the GUI, the project then sends you the applications. Which is what we were talking about here.

But just for the sake of arguing, have you ever tried getting into the Seti@Home directory on an Android device? It's not easy. You have to root the device, and just to navigate to the Seti directory (at data\data\edu.berkeley.boinc\projects\edu.berkeley.setiathome\) you already need an app, like X-Plore. Without a rooted device you can't even get to the directory. It's hidden.

So in all, not something that a general Joe will be able to do, and therefore highly unlikely that Dave has done so.

---

Thanks Richard for the app_info details.

I was scratching my head why I couldn't get v8 files with ReadConfigFiles, then tried a BOINIC restart, and poof, it worked.

It is running now, but I do see a 1C temp increase with 1 V8, and 3 AP tasks running on CPU.

Yes, i have noticed that also.
V8 seems to utilise the CPU better so its getting a little bit warmer.

---

With each crime and every kindness we birth our future.

Interesting,

I have a v8 task that makes it to about 40 sec done, then the time restarts at 0.

not sure what is up with that.

I have one V8 task on the Linux laptop and 3 ready to start. It is at 2.279% after 21 minutes.
Tullio

---

Interesting,

I have a v8 task that makes it to about 40 sec done, then the time restarts at 0.

not sure what is up with that.

Some Recent Boinc's will estimate the progress until the app starts reporting it's progress, More recent Boinc's stay at 0% until the app starts reporting it's progress.
although you said time and not % progress, In that case you may wish to burrow down to it's slot directory, and read what the stderr.txt says.

What happens in the first 40 seconds? FFTW 3.3.4 wisdom planning, and Seti v8 app function choice selection.

Claggy

Ohh crap I should check the log:

2016-01-02 10:02:47 AM | SETI@home | Task 09se11af.5180.2043140.13.40.60_1 exited with zero status but no 'finished' file
2016-01-02 10:02:47 AM | SETI@home | If this happens repeatedly you may need to reset the project.


I will give it 15 minutes, then abort task.

Ohh crap I should check the log:

2016-01-02 10:02:47 AM | SETI@home | Task 09se11af.5180.2043140.13.40.60_1 exited with zero status but no 'finished' file
2016-01-02 10:02:47 AM | SETI@home | If this happens repeatedly you may need to reset the project.


I will give it 15 minutes, then abort task.

It's not going to fix itself on it's own, try restarting Boinc, what does the stderr.txt say in it's slot directory?

Claggy

I have been trying to catch the stderr from slot4, but it never shows up.

I will restart BOINC.

I have been trying to catch the stderr from slot4, but it never shows up.

I will restart BOINC.

Is there a wisdom.sah in the slot directory, and is there anything in it?

Claggy

Memo to self:
Don't forget to stop/start cycle BOINC after updating app_info.xml and loading the application files into the project folder...

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

I can't seem to capture anything from my slot, MB they are just gone too fast.

I keep seeing this message.

2016-01-02 10:44:18 AM | SETI@home | [task] task_state=EXECUTING for 09se11af.5180.2043140.13.40.60_1 from start
2016-01-02 10:44:18 AM | SETI@home | [cpu_sched] Restarting task 09se11af.5180.2043140.13.40.60_1 using setiathome_v8 version 800 in slot 4

40 seconds later it restarts.

I can kill the task, but just trying to help debug v8 the best I can.

I can't seem to capture anything from my slot, MB they are just gone too fast.

I keep seeing this message.

2016-01-02 10:44:18 AM | SETI@home | [task] task_state=EXECUTING for 09se11af.5180.2043140.13.40.60_1 from start
2016-01-02 10:44:18 AM | SETI@home | [cpu_sched] Restarting task 09se11af.5180.2043140.13.40.60_1 using setiathome_v8 version 800 in slot 4

40 seconds later it restarts.

I can kill the task, but just trying to help debug v8 the best I can.

Are there any files in the Slot 4 directory? and what are they?

Claggy

Well it doesn't change no matter how many times I refresh.


init_data.xml
libfftw3f-3-3-4_x86.dll
result.sah
setiathome_8.00_windows_intelx86.exe
work_unit.sah


init_data.xml is current date stamp, the others are all 5 hours old.

Thanks Richard for that app_info with the graphics support.

Nice to see those graphics again.

Running good. Should have suspended any new work starting and let the current ones finished, trashed 16 work units.

Oh well, someone will pick those up.

Need guidance. There are no GPU apps for V8. I crunch on both CPU and GPU. If check off both V8 and V7 will I continue to get GPU V7 MB's?

In what order to my caches get filled for CPU work? V8's if available then V7's?

Herb

PS. The app_info.xml posted for Lunatic's users seems to be fine. I added the changes to one rigs and it has started downloading V8 work units. It will take awhile before the older V7's clear out and they start to run.

Thank you for everyone involved in developing the new v8 app.

I have run some WU's and all have validated.
I run on linux 64-bit with i7 3930K. The app I'm using is 32 bit.

Which version would be best suited for my GPU?

See run times here: http://setiathome.berkeley.edu/results.php?hostid=7475713&offset=0&show_names=0&state=4&appid=29

Petri

---

To overcome Heisenbergs:
"You can't always get what you want / but if you try sometimes you just might find / you get what you need." -- Rolling Stones

@ Fawkesguy,

Look at the line immediately following

<app_version>

In every case, it's an <app_name> - EXCEPT the one you added in red. It'll be

<app_name>setiathome_v8</app_name>

of course.

@ TBar - he quoted your post, which is where the error came from. Please proof-read, or better yet test, before posting.

Richard, thank you for catching that. :-)

Think Raistmer and Urs might be pretty close With OpenCL builds now last kinks seem to be being ironed out with CPU. Cuda one probably available as (regular slow) code tomorrow. Not sure when the project will release GPU binaries and tasks for v8 on main yet (assuming not yet), But Eric seems to be fasttracking things.

---

"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.

Thank you for everyone involved in developing the new v8 app.

I have run some WU's and all have validated.
I run on linux 64-bit with i7 3930K. The app I'm using is 32 bit.

Which version would be best suited for my GPU?

See run times here: http://setiathome.berkeley.edu/results.php?hostid=7475713&offset=0&show_names=0&state=4&appid=29

Petri

Petri, I question some of your results as you are validating a -9 overflow against a -9 overflow. (of course that may be correct)

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

Well it doesn't change no matter how many times I refresh.


init_data.xml
libfftw3f-3-3-4_x86.dll
result.sah
setiathome_8.00_windows_intelx86.exe
work_unit.sah


init_data.xml is current date stamp, the others are all 5 hours old.

What you get with a correctly working app is (with Boinc 7.6.22):

boinc_lockfile
boinc_task_state.xml (Only with recent Boinc's I believe)
graphics_app (If app_info has graphics app and associated files included)
init_data.xml
libfftw3f-3-3-4_x86.dll
result.sah
seti_logo (If app_info has graphics app and associated files included)
setiathome_8.00_windows_intelx86.exe
sponsor_bkg (If app_info has graphics app and associated files included)
sponsor_logo (If app_info has graphics app and associated files included)
state.sah (only generated once the wisdom and app function choices are done)
stderr.txt
stderrgfx.txt (If you're opened the graphics app)
wisdom.sah
work_unit.sah

I'd try updating to Boinc 7.6.22 on that host in case it's an api problem.

Claggy