A suggestion for the interface - and in making the suggestion I am gently treading on eggshells ...... I am acutely aware of the work involved in all this, may well be this would get held off until a later version, however ...

To populate the list of WUs the DB has to be queeried anyway, how about adding another element to that query re "Wingman Completed" ? I dont know how you are querying the DB, but on the face of it, it would seem to be a simple small addition to the query. If the wingman has completed their bit, colour the relevant cell in Result Column - say - green. Probably not worth doing the reverse (ie not yet done) as it would be too much on the eyes.

Utility is micro-manageing which we all get into from time to time, some even make a lifes work of it. Knowing a wingman has completed may provide an incentive to get that one done "next". Whilst I agree its not much effort to make one more click to find out if they have finished, its all grist to the mill to make it user friendly - it could be an awful lot of clicks in a long list to find one that has completed :) SETI will love you for it, as I am convinced a lot of queries are made by crunchers trying to find this out - and it will make a significant impact on reducing DB queries/hits on the DB.

From that point, may even be possible to reorder "next to crunch" based on wingman complete. That really would be a Major Win, as it would help greatly shorten the Pending queues, particularly for the mega crunchers. The latter half of the suggestion may well be too much at this stage, as its beyond a simple query amendment - at least knowing its been done by the wingman would be good in itself.

Regards
Zy

---

A suggestion for the interface - and in making the suggestion I am gently treading on eggshells ...... I am acutely aware of the work involved in all this, may well be this would get held off until a later version, however ...

To populate the list of WUs the DB has to be queeried anyway, how about adding another element to that query re "Wingman Completed" ? I dont know how you are querying the DB, but on the face of it, it would seem to be a simple small addition to the query. If the wingman has completed their bit, colour the relevant cell in Result Column - say - green. Probably not worth doing the reverse (ie not yet done) as it would be too much on the eyes.

Utility is micro-manageing which we all get into from time to time, some even make a lifes work of it. Knowing a wingman has completed may provide an incentive to get that one done "next". Whilst I agree its not much effort to make one more click to find out if they have finished, its all grist to the mill to make it user friendly - it could be an awful lot of clicks in a long list to find one that has completed :) SETI will love you for it, as I am convinced a lot of queries are made by crunchers trying to find this out - and it will make a significant impact on reducing DB queries/hits on the DB.

From that point, may even be possible to reorder "next to crunch" based on wingman complete. That really would be a Major Win, as it would help greatly shorten the Pending queues, particularly for the mega crunchers. The latter half of the suggestion may well be too much at this stage, as its beyond a simple query amendment - at least knowing its been done by the wingman would be good in itself.

Regards
Zy

This sounds a lot simpler than it is. It would probably require multiple queries of the database. You would most likely need to scrape all the user info then parse it to get the links to the individual WUs. You then would need to do a follow up queries for each and every WU then parse that information.

Most people only look at a few WU. If automated every WU (possibly 1000s) would be looked at. This would indeed place a much heavier load on the database and it would probably need to be done every time the manager contacted the projects. I can't see a simple way of doing this that wouldn't overload the internet connection and the database server.

---

Boinc V7.2.42
Win7 i5 3.33G 4GB, GTX470

Good point - as will be obvious me no programmer ....

I certainly would not like to "scrape" - I suspect Matt has had enough of that :)

I hear the realities, shame though, there's a big win there tantilisingly close ....

Regards
Zy

---

... To populate the list of WUs the DB has to be queeried anyway, ...

That's not true, you have all the info what needed for this, on your computers inside the Boinc data directory, in the client_state.xml and the wu files under the project directory. BTW i like the idea, but that really would hit the servers.

---

... To populate the list of WUs the DB has to be queeried anyway, ...

That's not true, you have all the info what needed for this, on your computers inside the Boinc data directory, in the client_state.xml and the wu files under the project directory. BTW i like the idea, but that really would hit the servers.

Actually, There is NO information regarding 'wingmen' in any of the tables.
I have been staring at theses xml tables for weeks now. If you know something I dont about this.. by all means, share.. I love to learn and be corrected when Im mistaken.
You can find out thier state.. running, done.. trashed.. name.. deadine.. and so on.. but as was mentioned before, you would have to search the master DBs of projects and pair up the WUs with other other computers.
Im not sure that can even be done. The servers would probablty look at it as an invasion and lock out the IPs.. Im not sure, I dont know how all that side works.
None the less, It surely would of been a cool feature.
Keep the ideas rolling in..
-- Mike

---

Not Ready Reading BRAIN. Abort/Retry/Fail?

Locking out the IP is done manually. After Matt notices that there is an "attack" mounted based on screen scraping...

The is nothing on the participant's side that indicates the coupling to other systems. All you have is your own performance information as Mike indicated. A lot can be done with that information if you like to play around with that kind of thing.

Sorry, I think there is a misunderstanding.

My comment was only for the

To populate the list of WUs, the DB has to be queeried anyway,

part, and I thought the 'DB' is stands for the main seti databases.
For this basic manager function (list the WUs), the client side data is enought.

Of course, checking the wingmen's state is an another story, which requires a connection to the seti servers.

BTW, the program looks really cool!

---

Of course, checking the wingmen's state is an another story, which requires a connection to the seti servers.

BTW, the program looks really cool!

Thanks :)

Yes.. You would need to contact the servers of ALL projects to get the wingmans state. Im not even sure that can be done with seti's servers or any projects.
Besides, The time to do it would make it something you would want to do as needed, Not be updated constantly like the state of the core clients are in my program.


I got the project attach to work and the UI for this part is pretty cool how I did it. I guess you will have to wait for the beta to see it ;)

-- Happy Memorial Day :) I hope there are no flowers you have to place.
-- Mike

---

Not Ready Reading BRAIN. Abort/Retry/Fail?

It would be nice for projects to provide an XML API for accessing information about user tasks from the website. Anyone know if such a thing exists or if the developers might consider adding it? I know here at SETI, the data might have to be pulled from the replica DB, meaning the data is liable to be stale...

---

. . . Mike - Happy 'belated' Birthday Sir - Terri [hello to you as well] and a Happy SETI@home 10th Anniversary to All

< nice work you've been doin' Mike - Accolades to All that you've worked on and Kudo's to You Sir for All your efforts . . .

< keep care of each other [hugs from joanne & myself]

< might speak w/ Paul [D. Buck] - see PM

Stay well . . .

---

BOINC Wiki . . .

Science Status Page . . .

Thanks Doc :)
Be well your self!
-- Mike

---

Not Ready Reading BRAIN. Abort/Retry/Fail?