what problems with seti claasic
the only problem with seti classic
was forced switching to boinc

seti classic was working
while boinc is not

thats the fact

If you didn't have such a poor memory, you would have recalled that when Seti Classic was this age, it often had even MORE problems than Seti BOINC does. It was surprisingly problematic for the first few years of it's life. Most of us "old timers" remember this and understand that whatever is going on now, the Seti team will eventually work the bugs out and get it working again.

---

You will be assimilated...bunghole!

lets face the truth
this whole boinc thing sucks
why the hell they close classic seti

Waah Waah. Crybaby. $hit happens. Deal with it. So BOINC is having issues with uploads right now. Big deal. Get on with your life.

Bonic is not having the issue, Seti is having the issue. COme on guys, lets get it right

Oh whatever. Dealing with Classic "trolls" leaves me little patience for picking nits. :)

---

You will be assimilated...bunghole!

The problem, in my opinion, is that too many people think that BOINC = SETI. BOINC is not equal to SETI. BOINC is a framework for many projects to work on. SETI is an actual project for BOINC.

The problems with classic were MUCH more than just a forced switch to SETI BOINC, which is not technically true anyway. The largest problem was that people were crunching units time and time again, whereas with BOINC every unit is crunched for a quorum of 3 and then that's one WU done, and more WUs fill the pipe. The biggest problems faced at the moment may not even be the fault of those at Berkeley. It may be that Cogent communication PLC are responsible. I mean, it wouldn't be the first time.

Please note that the above views are the views of myself and therefore I see no reason for anyone to attack these views.

---

what problems with seti claasic
the only problem with seti classic
was forced switching to boinc

seti classic was working
while boinc is not

thats the fact

thats NOT a fact. I am running BOINC as we speak...no problems AT ALL. The only issue BOINC is having is with SETI. I am running 2 other projects on BOINC and they are doing just fine. SETI classic was old. They needed to catch up with technology and use what everyone else was starting to use. Its easier in my opinion and allows you to run MULTIPLE projects. It was not forced to switch to BOINC they made the decision based on the amount of people using the software. Remember, Berkeley created BOINC and SETI@home. so there is no forcing anywhere.

---

"By faith we understand that the universe was formed at God's command, so that what is seen was not made out of what was visible". Hebrews 11.3

what problems with seti claasic
the only problem with seti classic
was forced switching to boinc

seti classic was working
while boinc is not

thats the fact

there are dozens of threads that describe in detail why classic needed to go away. Not the least of which was that the BOINC structure gave a way for better science to be done and done more efficiently. Please take the time to read those posts so you don't give the wrong impression.

BOINC is NOT the current problem, it's the SETI hardware that works with it. They are two separate things. Different programs, different hardware. Some BOINC projects have servers that are located overseas!

Saying that BOINC sucks is like saying that television sucks simply because you don't like one of the available channels.

---

Without love, breath is just a clock ... ticking.
Equilibrium

My post is about problems with Classic not with SETI/BOINC.

Classic or BOINC...does not matter. The issues are with Berkeley, not us. Classic is shuttig down. So its not a problem its a process. Classic will not exist at all in a short while. So if you would like to continue with SETI@Home you will HAVE to use BOINC.

Please do not use my post about Classic to draw any conclusions as to the operation of SETI/BOINC.

My statement is only valid with regard to why Classic will not continue, and is intended only for those who think that Classic is perfect and cannot be improved upon.

---

what problems with seti claasic
the only problem with seti classic
was forced switching to boinc

seti classic was working
while boinc is not

thats the fact

If you didn't have such a poor memory, you would have recalled that when Seti Classic was this age, it often had even MORE problems than Seti BOINC does. It was surprisingly problematic for the first few years of it's life. Most of us "old timers" remember this and understand that whatever is going on now, the Seti team will eventually work the bugs out and get it working again.

There is something bogus with the tech news boinc is giving us, they say we are uploading 35 units per second now and if you watch closly thenot validated numbers that cant be true 35 per second ( they announced them 3 days ago would be some 9.072.000 in 3 days, but reality is that the validater acumulayion in the last thre days where only some 150.000 packages this would be around 35 per minute and not per second.Was this an error or is there sombody covering the truth.
nikolaus

---

The problem, in my opinion, is that too many people think that BOINC = SETI. BOINC is not equal to SETI. BOINC is a framework for many projects to work on. SETI is an actual project for BOINC.

The problems with classic were MUCH more than just a forced switch to SETI BOINC, which is not technically true anyway. The largest problem was that people were crunching units time and time again, whereas with BOINC every unit is crunched for a quorum of 3 and then that's one WU done, and more WUs fill the pipe. The biggest problems faced at the moment may not even be the fault of those at Berkeley. It may be that Cogent communication PLC are responsible. I mean, it wouldn't be the first time.

Please note that the above views are the views of myself and therefore I see no reason for anyone to attack these views.

This is not an attack but please remember that the classic crunchers do not choose which units to process, they handle what the back-office system sends them! Many people seem to forget this crucial fact and blame us for repeating work. But, are all the results exactly the same? It would appear not since they are processed multiple times even under BOINC, so is a mere 3 enough to assume that voting for 2 of them gives the right answer? And how do we know if it is the right answer?

Most people don't like BOINC because the credits accumulated since 1999 haven't been added to the total of a strange and meaningless counting system, and that the project team does not talk to anyone or respond to constructive comments or complaints.

And since we are operating and communicating on the SETI project BBs the difference between classic and boinc is easier to write about by using those titles.

We are all for new and more effective ways of working, but being new does not necessarily mean it is best and especially since many problems remain.

---

Seti desperately needs to switch over to the "Enhanced" app, which will greatly reduce the traffic. I hope they can iron the bugs out of it quickly...

---

what problems with seti claasic
the only problem with seti classic
was forced switching to boinc

seti classic was working
while boinc is not

thats the fact

Over the past day, BOINC based projects have done 167 teraflops of work.

That of course does not count the SETI work that is being done right now, and will be reported as the backlog decreases.

Many of us have seen the same kind of problems we're seeing right now, and with more than a bit of work by the SETI operations staff, and a little patience, everything works out just fine.

My strong suggestion is to simply be patient, leave BOINC running, and don't worry about losing work or not getting credits.

By comparison, Classic just plain stopped when the servers went down, unless you installed and configured some third-party add-ons.

---

what problems with seti claasic
the only problem with seti classic
was forced switching to boinc

seti classic was working
while boinc is not

thats the fact

If you didn't have such a poor memory, you would have recalled that when Seti Classic was this age, it often had even MORE problems than Seti BOINC does. It was surprisingly problematic for the first few years of it's life. Most of us "old timers" remember this and understand that whatever is going on now, the Seti team will eventually work the bugs out and get it working again.

There is something bogus with the tech news boinc is giving us, they say we are uploading 35 units per second now and if you watch closly thenot validated numbers that cant be true 35 per second ( they announced them 3 days ago would be some 9.072.000 in 3 days, but reality is that the validater acumulayion in the last thre days where only some 150.000 packages this would be around 35 per minute and not per second.Was this an error or is there sombody covering the truth.
nikolaus

Your math is a bit off. The 35 results per second number is from yesterday...not the past three days. 35 results per second = 3 million results returned over the last 24 hours. But keep in mind two things. First, the validators WERE running last night / earlier today. I saw the green in the status page. Second, the number in "waiting for validation" is the number of work units...not results. There are 4 results per work unit. So over the past 24 hours, the number should be no higher than 756,000. But since the validators were running for several hours, that number will naturally be lower. So actually I think it's about right.

---

You will be assimilated...bunghole!

We are all for new and more effective ways of working, but being new does not necessarily mean it is best and especially since many problems remain.

... and yet, for all the problems, much useful science is being accomplished.

7.5 million credits yesterday according to BOINCstats, and that is without SETI.

We'll see a big jump when the validators are turned back on.

---

Nice, original idea, Ace. We haven't read this in a dozen other threads. Thanks for the contribution.

Yea it has been read in a dozen other threads, but theres still no answer, so yes i did make a new thread and expected someone to complain about it but o well.

If there is so much of an overload on the servers why can we not get a new server? Even if Seti@home is poor there has to be some way to get a new server. You cant seriously say that out of the hundreds of thousands of Seti crunchers there arent millionaires participating in this project! Why dont we ask them for the money!!!???

Geek@Play I cant see them discarding 5 days of work. If that happened, and people knew it happened, 10s of thousands would quit. With the way ppl want to quit just because of BOINC in general you cant expect them to stay if we do something like toss out 5 days of work.


-----Please note there may have been some sarcasm in that second paragraph

---

I betcha if they wouldn't give the classc ending message everytime a classic client tries to upload, a major problem could be fixed. Lot's of setiqueues which uploaded a wu and think they didn't upload so they try again. All those extra tries clogging up the system.

---

what problems with seti claasic
the only problem with seti classic
was forced switching to boinc

seti classic was working
while boinc is not

thats the fact

If you didn't have such a poor memory, you would have recalled that when Seti Classic was this age, it often had even MORE problems than Seti BOINC does. It was surprisingly problematic for the first few years of it's life. Most of us "old timers" remember this and understand that whatever is going on now, the Seti team will eventually work the bugs out and get it working again.

There is something bogus with the tech news boinc is giving us, they say we are uploading 35 units per second now and if you watch closly thenot validated numbers that cant be true 35 per second ( they announced them 3 days ago would be some 9.072.000 in 3 days, but reality is that the validater acumulayion in the last thre days where only some 150.000 packages this would be around 35 per minute and not per second.Was this an error or is there sombody covering the truth.
nikolaus

Your math is a bit off. The 35 results per second number is from yesterday...not the past three days. 35 results per second = 3 million results returned over the last 24 hours. But keep in mind two things. First, the validators WERE running last night / earlier today. I saw the green in the status page. Second, the number in "waiting for validation" is the number of work units...not results. There are 4 results per work unit. So over the past 24 hours, the number should be no higher than 756,000. But since the validators were running for several hours, that number will naturally be lower. So actually I think it's about right.

Ummm i checked the last hour and it was only some 2000 workunits well this would be some 8000 results per hour or 2.22 per second so i am still far off?
nikolaus ( the upload and download server was still working)

---

My post is about problems with Classic not with SETI/BOINC.

Classic or BOINC...does not matter. The issues are with Berkeley, not us. Classic is shuttig down. So its not a problem its a process. Classic will not exist at all in a short while. So if you would like to continue with SETI@Home you will HAVE to use BOINC.

Please do not use my post about Classic to draw any conclusions as to the operation of SETI/BOINC.

My statement is only valid with regard to why Classic will not continue, and is intended only for those who think that Classic is perfect and cannot be improved upon.

Classic is not perfect...its old/out-of-date. The new software is faster and more reliable. And again the same people that made SETI Classic made BOINC.

---

"By faith we understand that the universe was formed at God's command, so that what is seen was not made out of what was visible". Hebrews 11.3

I betcha if they wouldn't give the classc ending message everytime a classic client tries to upload, a major problem could be fixed. Lot's of setiqueues which uploaded a wu and think they didn't upload so they try again. All those extra tries clogging up the system.

You know darn well that the servers that service Classic are not the same servers that service BOINC.

But I am rather impressed that you waited this long to complain. Were you sick or something?

I betcha if they wouldn't give the classc ending message everytime a classic client tries to upload, a major problem could be fixed. Lot's of setiqueues which uploaded a wu and think they didn't upload so they try again. All those extra tries clogging up the system.

You know darn well that the servers that service Classic are not the same servers that service BOINC.

But I am rather impressed that you waited this long to complain. Were you sick or something?

Same router links to university. Who says the bottleneck is directly at servers.

---

I betcha if they wouldn't give the classc ending message everytime a classic client tries to upload, a major problem could be fixed. Lot's of setiqueues which uploaded a wu and think they didn't upload so they try again. All those extra tries clogging up the system.

You know darn well that the servers that service Classic are not the same servers that service BOINC.

But I am rather impressed that you waited this long to complain. Were you sick or something?

Same router links to university. Who says the bottleneck is directly at servers.

If you see the Server Status Page of the servers not running only 1 is in the red the others were turned off by Berkeley. Thats why nothing is working. SETI is noting working for 90% of everyone here. They have it turned off to get all there stuff to BOINC. Time. It takes time.

Calm down everyone. It will be up and running again soon. Give them the time they need to do their job. Yelling and threatening to leave SETI or even BOINC is not going to make anything better or make things go any faster for that matter.

---

"By faith we understand that the universe was formed at God's command, so that what is seen was not made out of what was visible". Hebrews 11.3

what problems with seti claasic
the only problem with seti classic
was forced switching to boinc

seti classic was working
while boinc is not

thats the fact

If you didn't have such a poor memory, you would have recalled that when Seti Classic was this age, it often had even MORE problems than Seti BOINC does. It was surprisingly problematic for the first few years of it's life. Most of us "old timers" remember this and understand that whatever is going on now, the Seti team will eventually work the bugs out and get it working again.

There is something bogus with the tech news boinc is giving us, they say we are uploading 35 units per second now and if you watch closly thenot validated numbers that cant be true 35 per second ( they announced them 3 days ago would be some 9.072.000 in 3 days, but reality is that the validater acumulayion in the last thre days where only some 150.000 packages this would be around 35 per minute and not per second.Was this an error or is there sombody covering the truth.
nikolaus

Your math is a bit off. The 35 results per second number is from yesterday...not the past three days. 35 results per second = 3 million results returned over the last 24 hours. But keep in mind two things. First, the validators WERE running last night / earlier today. I saw the green in the status page. Second, the number in "waiting for validation" is the number of work units...not results. There are 4 results per work unit. So over the past 24 hours, the number should be no higher than 756,000. But since the validators were running for several hours, that number will naturally be lower. So actually I think it's about right.

Ummm i checked the last hour and it was only some 2000 workunits well this would be some 8000 results per hour or 2.22 per second so i am still far off?
nikolaus ( the upload and download server was still working)

The page is only updated every 30 minutes. Collect your stats after...say...12 hours and see what the number is.

---

You will be assimilated...bunghole!