Mikkyo of team MacNN has successfully recompiled the boinc client and core worker of SETI 3.08.

I have tested myself last night and it works well.

The files can be found at

http://members.dslextreme.com/~readerforum/forum_team/boinc.html

Many thanks to Mikkyo and the great team MacNN for their effort.

Cheers
Marc

Please repost the COMPLETE web address.

http://members.dslextreme.com/~read...team/boinc.html

gives an error:

Not Found
The requested URL /~read...team/boinc.html was not found on this server.

Thanks.

> Please repost the COMPLETE web address.
>
> http://members.dslextreme.com/~read...team/boinc.html
>
> gives an error:
>
> Not Found
> The requested URL /~read...team/boinc.html was not found on this server.
>
> Thanks.
>

I have just tested it this one should work

http://members.dslextreme.com/~readerforum/forum_team/boinc.html

yah!!! this works, just a question, is there any way to check the status of completion like I was able to do in the classic version using terminal like this grep prog= state.sah??
I tried with this version but terminal can't see any of the files in the /slots/0/ folder???

> yah!!! this works, just a question, is there any way to check the status
> of completion like I was able to do in the classic version using terminal
> like this grep prog= state.sah??
> I tried with this version but terminal can't see any of the files in the
> /slots/0/ folder???
>

I am also looking for that. have a look at this thread. Please let me know if it works
and tell me how to run that, not being a unix guy, I found all these cmd confusing.

http://setiweb.ssl.berkeley.edu/forum_thread.php?id=1122

Marc
[img] TeamSetiSig2.gif

> yah!!! this works, just a question, is there any way to check the status
> of completion like I was able to do in the classic version using terminal
> like this grep prog= state.sah??
> I tried with this version but terminal can't see any of the files in the
> /slots/0/ folder???


I got it to work, i guess it just takes awhile at first for the files to show up or something, but
in a new Terminal window., cd where.ever.your.boinc-seti is/slots/0/ then press return,
then type in grep prog state.sah press return result should be something like this->
mattruthsimac:boinc-seti10.2.8/slots/0] mattruth% grep prog state.sah
0.44568963
[mattruthsimac:boinc-seti10.2.8/slots/0] mattruth%

hope this helps alot of u out... remember the /slots/0/ folders are important to go to in order to do this..

Matt..

> > yah!!! this works, just a question, is there any way to check the
> status
> > of completion like I was able to do in the classic version using
> terminal
> > like this grep prog= state.sah??
> > I tried with this version but terminal can't see any of the files in
> the
> > /slots/0/ folder???
>
>
> I got it to work, i guess it just takes awhile at first for the files to
> show up or something, but
> in a new Terminal window., cd where.ever.your.boinc-seti is/slots/0/ then
> press return,
> then type in grep prog state.sah press return result should be something
> like this->
> mattruthsimac:boinc-seti10.2.8/slots/0] mattruth% grep prog state.sah
> 0.44568963
> [mattruthsimac:boinc-seti10.2.8/slots/0] mattruth%
>
> hope this helps alot of u out... remember the /slots/0/ folders are
> important to go to in order to do this..
>
> Matt..
>
>

Thanks Matt it works here too.
Marc

not really a reply to anything, just a Question, I just finished a WU, and am wondering about how in 10-15minutes or so after downloading a new WU, that how it can already be at 28% done according to doing this in terminal grep prog state.sah, I enjoy how fast this is, but am wondering how it can be that fast, compared to the classic CLI version of setiathome?

> not really a reply to anything, just a Question, I just finished a WU,
> and am wondering about how in 10-15minutes or so after downloading a new WU,
> that how it can already be at 28% done according to doing this in terminal
> grep prog state.sah, I enjoy how fast this is, but am wondering how it can be
> that fast, compared to the classic CLI version of setiathome?
>
>
I haven't check that on my Mac but it's doing that on my PC. I can see it
on the GUI. It goes like hell at the beggining (about 40% in 15 Min)and then starts to slow down. I don't know why but it's not a Mac or MacNN specific.
Completion time at the end is normal here on both platforms compare to previous versions. It does that for everyone I guess.

> > not really a reply to anything, just a Question, I just finished a
> WU,
> > and am wondering about how in 10-15minutes or so after downloading a new
> WU,
> > that how it can already be at 28% done according to doing this in
> terminal
> > grep prog state.sah, I enjoy how fast this is, but am wondering how it
> can be
> > that fast, compared to the classic CLI version of setiathome?
> >
> >
> I haven't check that on my Mac but it's doing that on my PC. I can see it
> on the GUI. It goes like hell at the beggining (about 40% in 15 Min)and then
> starts to slow down. I don't know why but it's not a Mac or MacNN specific.
> Completion time at the end is normal here on both platforms compare to
> previous versions. It does that for everyone I guess.

My Guess would be that bionc has better coding or something to do that, if its like that for everyone, on all platforms... but thats just a guess.... also it may slow down a bit if it finds anything at the beginning and so it anylizes those results abit more deeper...

Work unit information varies significantly from one work unit to another. There does appear to be a general trend of work units starting fast, and then slowing down as the information density increases, but it varies from one work unit to another.

The beauty of BOINC is that it rewards you for the amount of work that you do, so work units that take longer, provide more credit, then work units that go quickly. When one considers the unknown quantities dealt with in Science, BOINC is a very good system. It also allows the various projects using BOINC to adjust their scientific parameters according to need, without penalizing the participants who donate their computer time.

This isn't to say that there aren't currently significant problems with BOINC & SETI, but in another three months, hardly anyone will even remember the problems of today.

Matt, thanks for the tip on how to read percentage done in the terminal. Didn't know that one.


The best Macintosh team ever assembled.

> Work unit information varies significantly from one work unit to another.
> There does appear to be a general trend of work units starting fast, and then
> slowing down as the information density increases, but it varies from one work
> unit to another.
>
> The beauty of BOINC is that it rewards you for the amount of work that you do,
> so work units that take longer, provide more credit, then work units that go
> quickly. When one considers the unknown quantities dealt with in Science,
> BOINC is a very good system. It also allows the various projects using BOINC
> to adjust their scientific parameters according to need, without penalizing
> the participants who donate their computer time.
>
> This isn't to say that there aren't currently significant problems with BOINC
> & SETI, but in another three months, hardly anyone will even remember the
> problems of today.
>
> Matt, thanks for the tip on how to read percentage done in the terminal.
> Didn't know that one.
>
> [url=http://team.macnn.com]
> The best Macintosh team ever assembled.


Your Welcome, I have known about the grep command for years since i have worked on all flavors of UNIX, esspecially FreeBSD when I had the old macs way before OS X... And thank you for the info...

Matt..

Also I wanted to post from the boinc projects email i subscibe too and how they are going to do builds from 10.2 from now on since i had 1st asked the question...


We've been doing our Mac builds on a 10.3 machine,
and apparently they don't work on 10.2.
We have a 10.2 machine that we recently revived,
and we'll do the builds there from now on.
-- David


Matt..

> Also I wanted to post from the boinc projects email i subscibe too and how
> they are going to do builds from 10.2 from now on since i had 1st asked the
> question...
>
>
> We've been doing our Mac builds on a 10.3 machine,
> and apparently they don't work on 10.2.
> We have a 10.2 machine that we recently revived,
> and we'll do the builds there from now on.
> -- David
>
>
> Matt..


Hey Guys! Dave has emailed me letting me know about them adding the Team MacNN link on the download page as download from a third-party site. http://setiweb.ssl.berkeley.edu/sah/download_other.php

Matt.