What people are seeing is the time to produce the higher quality analysis of the Seti Signal takes longer.

I trust that with this additional time there is also a built-in language translator?

---

me@rescam.org

I am not sure that Eric has that built in yet... I think it is still Alpha testing..

What people are seeing is the time to produce the higher quality analysis of the Seti Signal takes longer.

I trust that with this additional time there is also a built-in language translator?

Al

---

Please consider a Donation to the Seti Project.

I signed up, and man this WU's are huge. I hope to have at least one done sometime this week, lol.

---

AMD Athlon 64 X2 4400+
AMD Athlon 64 3800+
AMD AthlonXP 3200+

Hmm.. I wonder how much credit I'll get for a 50hr WU.

Hmm.. I wonder how much credit I'll get for a 50hr WU.

Around 195 to 220.

That's the minimum and maximum I have seen so far.
The "lower Angle Ranges" lie around 45-50 credits.

---

Hmm.. I wonder how much credit I'll get for a 50hr WU.

If you can dig out the angle_range of the unit, then we might be able to tell you more accurately. If it is one of the recent 0.189 units from 05jl01ab then 220 +/- fractions.

---

Well I haven't read up on the angle thing so I can't address that. But here is that WU. I still have 13 hours to go.

Misfit, since the unit is still going, go to \\BOINC\\Projects\\Setiweb.ssl.berkeley.edu_beta and open the unit BOINC is crunching. It'll be 354 to 364 KB, you can open it with Notepad in Windows.

Then look up and copy out the number between the <true_angle_range></true_angle_range> tags. Don't save the file, just exit it.

Rightclick in an answer window here and post what you have. I'm sure someone else can tell you all about it. ;)

---

0.41198824224476

0.41198824224476

191 credits

---

I will note that there are some issues with older machines and efforts are happening to insure the can contribute what the users wants to contribute.

Once again I extend an Invitation to Go Look and Crunch and Enahnced workunit.

Thanks, but no thanks ... I was considering signing up, but from the processing times quoted here I doubt my system would be able to produce any results before their deadlines expire. Or am I wrong in guessing that a G4/400 Mac would be looking at over two hundred hours per WU? (200 h / 120 h/week ~= 1.6 weeks and I have two other projects already.)

---

I will note that there are some issues with older machines and efforts are happening to insure the can contribute what the users wants to contribute.

Once again I extend an Invitation to Go Look and Crunch and Enahnced workunit.

Thanks, but no thanks ... I was considering signing up, but from the processing times quoted here I doubt my system would be able to produce any results before their deadlines expire. Or am I wrong in guessing that a G4/400 Mac would be looking at over two hundred hours per WU? (200 h / 120 h/week ~= 1.6 weeks and I have two other projects already.)

Actully the deadlines are pretty long. The one I'm crunching now isn't due until March 8th and I've had it at least a week or so on my machine.

---

Kathryn :o)
The BOINC FAQ Service
The Unofficial BOINC Wiki
The Trac System
More BOINC information than you can shake a stick of RAM at.

The times to crunch SetiB Enhanced are quite long, this is a provisional list produced by Ingleside recently, but they are continually being adjusted as the actual crunching times for the various angle ranges is found.

Crunch-times and Deadlines in Seti_Enhanced is heavily influenced by angle-range, so for a computer using 3h10m with the "standard" v4.18-seti-application can setup a table like this:

AR - cpu-time (h) - Deadline (days)
0.11 - 12.11 - 25.46 (same for smaller angle-range)
0.12 - 12.92 - 27.16
0.15 - 14.41 - 30.29
0.20 - 16.89 - 35.49
0.225 - 18.13 - 38.10
0.226 - 56.12 - 117.93
0.25 - 49.33 - 103.67
0.30 - 39.27 - 82.54
0.35 - 32.39 - 68.07
0.40 - 27.41 - 57.61
0.41 - 26.58 - 55.86
0.42 - 25.79 - 54.20
0.43 - 25.04 - 52.63
0.44 - 24.33 - 51.14
0.45 - 23.66 - 49.72
0.46 - 23.02 - 48.37
0.47 - 22.41 - 47.09
0.48 - 21.82 - 45.87
0.49 - 21.27 - 44.70
0.50 - 20.74 - 43.59
0.55 - 18.41 - 38.69
0.60 - 16.51 - 34.70
0.65 - 14.94 - 31.40
0.70 - 13.61 - 28.62
0.75 - 12.49 - 26.26
0.80 - 11.52 - 24.22
0.85 - 10.68 - 22.45
0.90 - 9.94 - 20.91
0.95 - 9.30 - 19.54
1.00 - 8.72 - 18.33
1.05 - 8.20 - 17.24
1.10 - 7.74 - 16.27
1.13 - 7.48 - 15.73
1.14 - 4.13 - 8.68 (same for larger angle-range)

Please note, this info is based on the current estimates the Splitter is using, so your real cpu-times will very likely be different. Also, even if estimates is correct for one Angle Range, it doesn't mean isn't 2x away for another angle-range.

---

Odysseus

There quite a few windows boxes, there is a good representation of Nix boxes... There are very few Mac's working, less than 1%...

Al

I will note that there are some issues with older machines and efforts are happening to insure the can contribute what the users wants to contribute.

Once again I extend an Invitation to Go Look and Crunch and Enahnced workunit.

Thanks, but no thanks ... I was considering signing up, but from the processing times quoted here I doubt my system would be able to produce any results before their deadlines expire. Or am I wrong in guessing that a G4/400 Mac would be looking at over two hundred hours per WU? (200 h / 120 h/week ~= 1.6 weeks and I have two other projects already.)

---

Please consider a Donation to the Seti Project.

i joint the beta too , is there a optimized apps for sse only cpu's ?! :)

edit: heheeheh i JOIN this joint :) hheheh i have only joint in my head :) I have one more question , when the beta becoms official , the statistics will be reset or not ?!

---

Dell XPS L702x
smokin' weed and searching for aliens .... ;]
TRUSTNO1

Actully the deadlines are pretty long. The one I'm crunching now isn't due until March 8th and I've had it at least a week or so on my machine.

Thanks; I thought the two-week turnaround limit was a BOINC-wide policy.

If I attach only one host (that I can keep an eye on most of the time) to Beta, how will its resource share affect the others: will they go idle for one third (or whatever proportion) of the time? Should I assign the Beta host to its own venue (I have School available) to isolate its resource-share preference from the others?

---

Thanks; I thought the two-week turnaround limit was a BOINC-wide policy.

Each project can pick its own deadline, to meet the needs of the project. For the ones I run it ranges from a day on Pirates (when they've got any work to crunch) to 11+ months for CPDN.

If I attach only one host (that I can keep an eye on most of the time) to Beta, how will its resource share affect the others: will they go idle for one third (or whatever proportion) of the time? Should I assign the Beta host to its own venue (I have School available) to isolate its resource-share preference from the others?

Resourse shares aren't determined by the number of results you process, it goes by time, CPU seconds. If you divide evenly, over the course of a month you'll give half your time to SETI, and the same amount of time to fewer Beta results. All eight of the projects listed in my sig are on one computer with three different levels of resource time, it's interesting (to me anyway!) to watch the dance among them for my computer time.

MJ

---

Resourse shares aren't determined by the number of results you process, it goes by time, CPU seconds. If you divide evenly, over the course of a month you'll give half your time to SETI, and the same amount of time to fewer Beta results. ...

I realize that the share is time, not production.

My question is whether or not hosts that haven't been attached to a given project--among those allocated a resource share in the user's preferences--will be affected. Suppose I had two hosts running S@h only, resource share at the default 100. Then I attach one of them to Beta, where my preference is also at 100. That host will now spend half its time crunching and the other half testing, so to speak. What about the second host, though? Will it spend half its time waiting to be attached to Beta, or will it continue working full-time, ignoring the setting that says it should be dividing its efforts?

---

I realize that the share is time, not production.

My question is whether or not hosts that haven't been attached to a given project--among those allocated a resource share in the user's preferences--will be affected. Suppose I had two hosts running S@h only, resource share at the default 100. Then I attach one of them to Beta, where my preference is also at 100. That host will now spend half its time crunching and the other half testing, so to speak. What about the second host, though? Will it spend half its time waiting to be attached to Beta, or will it continue working full-time, ignoring the setting that says it should be dividing its efforts?

Ah, ok, I get you.

Each host calculates itself separately. If you have three projects, all set at 100, the computer that runs all three will give 1/3 of its time to each project that it runs. The computer that only runs two will give 1/2 of its time to each project that it runs.

MJ

---

Each host calculates itself separately. If you have three projects, all set at 100, the computer that runs all three will give 1/3 of its time to each project that it runs. The computer that only runs two will give 1/2 of its time to each project that it runs.

Great; that makes sense, but one never knows ... I guess this flexibility is facilitated by the allocation of resources by 'weight' instead of as percentages; each host works with the relevant values without having to worry about 'fixed' proportions not adding up.

---