How much effort would it be for the results viewing page to be sorted by time reported before issuing to the web? If the seti engine were working correctly, then I suspect we wouldn't hit the web page as often to see the pending results buried many pages deep, since they would be the most recent ones that were not queued.

Also anybody have the following bug: last week seti posted about 500 (really) work units to one of my computers. They were not actually downloaded (I don't think), just posted to the view pages (and therefore assigned to me in the database). That is, my queue has maintained just 20-30 wu's throughout. I think I was running 4.45 at the time. Using a laptop, I was getting some spotty connections on the Oregon beach, but 500 ether-units seems wierd??

---

May this Farce be with You

How much effort would it be for the results viewing page to be sorted by time reported before issuing to the web? If the seti engine were working correctly, then I suspect we wouldn't hit the web page as often to see the pending results buried many pages deep, since they would be the most recent ones that were not queued.

By the date who reported them?
AFAIK, they are reported in the order they were issued to you. Since BOINC generally runs them in the order they were sent and therefore returns them in the same order, they are effectively in reported order.

The reason that some of your pending results are burried pages down is because others have not yet returned them and nothing to do with the order you did them.

Also anybody have the following bug: last week seti posted about 500 (really) work units to one of my computers. They were not actually downloaded (I don't think), just posted to the view pages (and therefore assigned to me in the database). That is, my queue has maintained just 20-30 wu's throughout. I think I was running 4.45 at the time. Using a laptop, I was getting some spotty connections on the Oregon beach, but 500 ether-units seems wierd??

[/quote]
This seems to be an exteem example of the ghost WU issue discussed in other threads. The will dissapear from your queue automatically about two weeks after the deadline expires. Some mods are being made I believe to improve the handshaking between the clients and servers to prevent this in future.

---

Thanks. Didn't know about ghost WU's.

Regarding the listing, what is important to me is to see what of mine is pending and which computers are hung. Since the system doesn't have the resources to a proper query on pending results (I'm told), the next best thing might be to sort by the time I reported a result. This would tend to put the pending ones up front and reduce the number of page requests I make to see where my pending wu's are. Since I'm probably not unique in this desire, sorting the list differently may reduce the web server requirements.

I don't know what AFAIK is. New gov agency?

It also may be nice to list the computer in the view results. Right now, people have to click like crazy to check the status of each of there computers, assuming they have more than one active box.

---

May this Farce be with You

I don't know what AFAIK is. New gov agency?

As far as I know, AFAIK, IS "As far as I know"

It also may be nice to list the computer in the view results. Right now, people have to click like crazy to check the status of each of there computers, assuming they have more than one active box.

Nope, do it with BOINC View real time ...

I can see which work units are being processed "right now", along with those waiting to be reported and those paused. I usually "hide" the unstarted ones as that is a long list ... if I get another Xeon, I may have to start hiding others ...

---

Is Boinc View stable? If so, great. I'll load it up.

---

May this Farce be with You

Nope, do it with BOINC View real time ...

I can see which work units are being processed "right now", along with those waiting to be reported and those paused. I usually "hide" the unstarted ones as that is a long list ... if I get another Xeon, I may have to start hiding others ...

I think this doesn't address his issue, which seems to be the status of already reported work units: which are pending, which are validated, invalid, etc... all the stuff that sits on the server. Last I knew, BOINCView only dealt with units on the hosts.

---

Nope, do it with BOINC View real time ...

I can see which work units are being processed "right now", along with those waiting to be reported and those paused. I usually "hide" the unstarted ones as that is a long list ... if I get another Xeon, I may have to start hiding others ...

I think this doesn't address his issue, which seems to be the status of already reported work units: which are pending, which are validated, invalid, etc... all the stuff that sits on the server. Last I knew, BOINCView only dealt with units on the hosts.

yes, true, though you can log the results, and if ambitious you can make an MySQL table that you can load them into and then do silly things like I do ... :)

BOINC Log-X is out there too ...

---

Is Boinc View stable? If so, great. I'll load it up.

It may not be perfect, but it does a good job reliably IMO.
I think I have run every version (including betas) and had no problems I rate any worse than minor.

---