good morning,
pleas help me understand why is Boinc often"currently idle" ? having finished 100% of his work , he can't connect with the seti server...so he stops working for hours and fails uploading the results he has generated...
Excuse my english I'm an french-native speaker...
Thanks...

---

good morning,
pleas help me understand why is Boinc often"currently idle" ? having finished 100% of his work , he can't connect with the seti server...so he stops working for hours and fails uploading the results he has generated...
Excuse my english I'm an french-native speaker...
Thanks...

The project is down. Some people are figuring it is the server. Your english is way better than my french.

À la prochaine (I had to use Google)

---

good morning,
pleas help me understand why is Boinc often"currently idle" ? having finished 100% of his work , he can't connect with the seti server...so he stops working for hours and fails uploading the results he has generated...
Excuse my english I'm an french-native speaker...
Thanks...

There seems to be a problem in Berkeley. Nobody can connect to server for uploading/downloading.
Have a look at this thread for further details.

regards

good morning,
pleas help me understand why is Boinc often"currently idle" ? having finished 100% of his work , he can't connect with the seti server...so he stops working for hours and fails uploading the results he has generated...
Excuse my english I'm an french-native speaker...
Thanks...

This is why all of the projects suggest that you join at LEAST one more project.

There are 5 open projects right now that are doing production work including SETI@Home. Look here for a list.

LHC@Home I think is closed for new signup, and they are only doing "spotty" issues of work though I have a number of work units on almost all of my machines.

I like ClimatePrediction.net for the real long work units as that means, it is hard to run dry of work ...

---

[quote]good morning,
pleas help me understand why is Boinc often"currently idle" ? having finished 100% of his work , he can't connect with the seti server...so he stops working for hours and fails uploading the results he has generated...
Excuse my english I'm an french-native speaker...
Thanks...

This is why all of the projects suggest that you join at LEAST one more project.


That really is beside the point. some of us JUST want to do Seti. In the classic Seti days there were SOME days of downtime to be sure but it was NOTHING like Boinc which is up and down all the time.

Recommending we join another project is really not the point. We just want to do Seti and we just want it to be as reliable as classic Seti. I dont see that as asking too much.

This is why all of the projects suggest that you join at LEAST one more project.

That really is beside the point. some of us JUST want to do Seti. In the classic Seti days there were SOME days of downtime to be sure but it was NOTHING like Boinc which is up and down all the time.

Recommending we join another project is really not the point. We just want to do Seti and we just want it to be as reliable as classic Seti. I dont see that as asking too much.

Well, I converted 4 years of logs, and they are on my site, and Classic had its moments too. And a couple of the last outages (and I am guessing this one too) affected both sides of the house.

As far as only doing SETI@Home, that is fine. But, it is a risk that you will run out of work. Heck, Dr. Anderson has also pointed out when Classic closes that it is possible that we will keep up with the data flow because BOINC is more efficient than Classic in production (reduction of repitition) that we may not be able to keep everyone busy.

Anyway, it is your choice and you have to live with the occasional outage.

---

Hi Paul,

Seticlassic works still fine. I just send some WU's. So it seems to be a problem that is related to the new version.

---

_\|/_
U r s

[quote]good morning,
pleas help me understand why is Boinc often"currently idle" ? having finished 100% of his work , he can't connect with the seti server...so he stops working for hours and fails uploading the results he has generated...
Excuse my english I'm an french-native speaker...
Thanks...

This is why all of the projects suggest that you join at LEAST one more project.


That really is beside the point. some of us JUST want to do Seti. In the classic Seti days there were SOME days of downtime to be sure but it was NOTHING like Boinc which is up and down all the time.

Recommending we join another project is really not the point. We just want to do Seti and we just want it to be as reliable as classic Seti. I dont see that as asking too much.

You have missed the point bigtime, I suggest that you read up on the purpose of Boinc.

Rules and Policies



Other BOINC projects
Other projects use the same platform, BOINC, as SETI@home. You may want to consider participating in one or more of these projects. By doing so, your computer will do useful work even when SETI@home has no work available for it.

---

Semper Eadem
So long Paul, it has been a hell of a ride.

Park your ego's, fire up the computers, Science YES, Credits No.

just switched to SETICLASSIC
don't wanna waste my CPU time:)

---

http://www.cyclistlog.com/

just switched to SETICLASSIC
don't wanna waste my CPU time:)

As Paul says, sign up to CPDN. You will never run short of work.

An added bonus is that you will be doing something that might ensure we are still here to receive the first Alien signal :)

EDIT: corrected spelling

---

Need help? Check out the excellent Unofficial BOINC-Wiki!
'We are the BOINC. Prepare to be assimilated.'

[quote]good morning,
pleas help me understand why is Boinc often"currently idle" ? having finished 100% of his work , he can't connect with the seti server...so he stops working for hours and fails uploading the results he has generated...
Excuse my english I'm an french-native speaker...
Thanks...

This is why all of the projects suggest that you join at LEAST one more project.


That really is beside the point. some of us JUST want to do Seti. In the classic Seti days there were SOME days of downtime to be sure but it was NOTHING like Boinc which is up and down all the time.

Recommending we join another project is really not the point. We just want to do Seti and we just want it to be as reliable as classic Seti. I dont see that as asking too much.

Hear Hear. Exactly. I don't want one single CPU cycle that _could_ go to SETI going _anywhere_ else. BOINC simply does not cater for this scenario.
I dont't object to running other projects if - and only if - there is no SETI work to run.
BOINC has no concept of a fallback project - one to be run _only_ if the main project is out of work. Even if I set SETI share to 1000 and another project to 1, the other project will eventually build-up debt and run - probably in panic mode even when I have a cache full of SETI. Useless.

---

[quote]good morning,
pleas help me understand why is Boinc often"currently idle" ? having finished 100% of his work , he can't connect with the seti server...so he stops working for hours and fails uploading the results he has generated...
Excuse my english I'm an french-native speaker...
Thanks...

This is why all of the projects suggest that you join at LEAST one more project.


That really is beside the point. some of us JUST want to do Seti. In the classic Seti days there were SOME days of downtime to be sure but it was NOTHING like Boinc which is up and down all the time.

Recommending we join another project is really not the point. We just want to do Seti and we just want it to be as reliable as classic Seti. I dont see that as asking too much.

Hear Hear. Exactly. I don't want one single CPU cycle that _could_ go to SETI going _anywhere_ else. BOINC simply does not cater for this scenario.
I dont't object to running other projects if - and only if - there is no SETI work to run.
BOINC has no concept of a fallback project - one to be run _only_ if the main project is out of work. Even if I set SETI share to 1000 and another project to 1, the other project will eventually build-up debt and run - probably in panic mode even when I have a cache full of SETI. Useless.

That sort of depends on how often SETI is out of work. In your scenario, S@H wouled have to have less downtime than 1 day out of 3 years to get the second WU from your backup project without S@H being down. Getting the first just sets things up.

---

BOINC WIKI

BOINC has no concept of a fallback project - one to be run _only_ if the main project is out of work.

It's called the Suspend button under both the Project tab and the Work tab. Okay, it needs user input, but I take it that's not too difficult to do. :)

---

That really is beside the point. some of us JUST want to do Seti. In the classic Seti days there were SOME days of downtime to be sure but it was NOTHING like Boinc which is up and down all the time.

Recommending we join another project is really not the point. We just want to do Seti and we just want it to be as reliable as classic Seti. I dont see that as asking too much.

Actually, I think BOINC has been solid for at least a month, but that is beside the point as well.

If you only want to do one project, carry a big cache -- set "connect every 'x'" to something like 6 or 7 days.

---

BOINC has no concept of a fallback project - one to be run _only_ if the main project is out of work. Even if I set SETI share to 1000 and another project to 1, the other project will eventually build-up debt and run - probably in panic mode even when I have a cache full of SETI. Useless.

Unless you're running 4.43 or 4.44, setting the shares that far apart won't work.

Assuming that the other project takes about four hours, that'd be one work unit for the other project every 4000 hours -- about 1 every five months if you crunch 24/7.

That may not be exactly the same as a "fallback" project, but it's really close, and you could set the resource share for SETI higher -- 2500 should be about once a year.

It wouldn't be that big a deal to reset the backup project every six months -- I'm pretty sure resetting will clear out the debts.

---

Hey Guys, Could you please tell me if there is currently a problem with the server as i am unable to upload results or download more work, Thanks in advance

---

That really is beside the point. some of us JUST want to do Seti. In the classic Seti days there were SOME days of downtime to be sure but it was NOTHING like Boinc which is up and down all the time.

Recommending we join another project is really not the point. We just want to do Seti and we just want it to be as reliable as classic Seti. I dont see that as asking too much.

Actually, I think BOINC has been solid for at least a month, but that is beside the point as well.

If you only want to do one project, carry a big cache -- set "connect every 'x'" to something like 6 or 7 days.

Looking at the long-term cricket graphs, we had a short outage in early May (about a month ago) -- we're in week 22, that was week 18.

The previous outage was mid-march.

---

Hey Guys, Could you please tell me if there is currently a problem with the server as i am unable to upload results or download more work, Thanks in advance

It doesn't look like there is anything wrong with the servers (more than one) but there does appear to be a problem reaching them.

There are inevitably several threads that discuss this -- inevitably they are all started within minutes of the slightest hiccup.

---

Hear Hear. Exactly. I don't want one single CPU cycle that _could_ go to SETI going _anywhere_ else. BOINC simply does not cater for this scenario.
I dont't object to running other projects if - and only if - there is no SETI work to run.
BOINC has no concept of a fallback project - one to be run _only_ if the main project is out of work. Even if I set SETI share to 1000 and another project to 1, the other project will eventually build-up debt and run - probably in panic mode even when I have a cache full of SETI. Useless.

Even if that CPU cycle is wasted as it was in seti classic? 30-40% of your CPU cycles were completely wasted in seti classic because work units got sent out more times than was needed just to keep users supplied with work. I believe I may have already posted this but it has been a while.

The data recorders at the radio telescope record enough data to produce about 800,000 work units every 24 hours. The math: 86,400 seconds in a day / 107 (length of a work unit) * 256 (number of sub-bands split out into work units for every 107 second period) * 4 (number of "results" created by boinc for each work unit) = 826856. Add in results that need to be re-checked due to errors and you get the 1 million work units per day that some of the admins have put forth as the goal for seti/BOINC. That is all the work there is to do for seti. Over on classic, there were 1,490,487 work units returned by in the last 24 hours by the ~400,000 active classic users. That means that about 33% of their CPU cycles were wasted. (actually more since BOINC is doing some of the work as well)

A while ago one of the admins here said that BOINC was sending out about 250,000 work units per day and seti/BOINC has less than 60,000 active users. Do the math. That means BOINC only has enough work for 2-300,000 users. When classic finally gets turned off, I immagine we will get a couple hundred thousand new users in short order and we will all start seeing "No work from project" messages in our logs not because there is a problem at Berkeley but simply because there is no more work to do! At that point you might as well just set up a 2nd project and set it to ~20% resource share and let it be.

These are the cold hard numbers. If you see a problem with them, lets have it. Otherwise I will expect everyone to be signed up with a second project by this time tomorrow! Ok... just kidding - but it IS a good idea :)

---

A member of The Knights Who Say NI!
For rankings, history graphs and more, check out:
My BOINC stats site

Hear Hear. Exactly. I don't want one single CPU cycle that _could_ go to SETI going _anywhere_ else. BOINC simply does not cater for this scenario.
I dont't object to running other projects if - and only if - there is no SETI work to run.
BOINC has no concept of a fallback project - one to be run _only_ if the main project is out of work. Even if I set SETI share to 1000 and another project to 1, the other project will eventually build-up debt and run - probably in panic mode even when I have a cache full of SETI. Useless.

Even if that CPU cycle is wasted as it was in seti classic? 30-40% of your CPU cycles were completely wasted in seti classic because work units got sent out more times than was needed just to keep users supplied with work. I believe I may have already posted this but it has been a while.

The data recorders at the radio telescope record enough data to produce about 800,000 work units every 24 hours. The math: 86,400 seconds in a day / 107 (length of a work unit) * 256 (number of sub-bands split out into work units for every 107 second period) * 4 (number of "results" created by boinc for each work unit) = 826856. Add in results that need to be re-checked due to errors and you get the 1 million work units per day that some of the admins have put forth as the goal for seti/BOINC. That is all the work there is to do for seti. Over on classic, there were 1,490,487 work units returned by in the last 24 hours by the ~400,000 active classic users. That means that about 33% of their CPU cycles were wasted. (actually more since BOINC is doing some of the work as well)

A while ago one of the admins here said that BOINC was sending out about 250,000 work units per day and seti/BOINC has less than 60,000 active users. Do the math. That means BOINC only has enough work for 2-300,000 users. When classic finally gets turned off, I immagine we will get a couple hundred thousand new users in short order and we will all start seeing "No work from project" messages in our logs not because there is a problem at Berkeley but simply because there is no more work to do! At that point you might as well just set up a 2nd project and set it to ~20% resource share and let it be.

These are the cold hard numbers. If you see a problem with them, lets have it. Otherwise I will expect everyone to be signed up with a second project by this time tomorrow! Ok... just kidding - but it IS a good idea :)

now multiply that result by 3 or 4. Need three people to validate the result.

---