Seti@Home optimized science apps and information

Optimized Seti@Home apps => Windows => Topic started by: efmer (fred) on 07 Aug 2009, 04:01:11 am

Title: Reading WU report after completion and reporting
Post by: efmer (fred) on 07 Aug 2009, 04:01:11 am

I'm working on a new project http://www.efmer.eu/boinc/boinc_tasks/
And I want to get information about the completed WU, like the stderr file, but after competion, upload and reporting.
I want this to check if there are any errors in the report.

Title: Re: Reading WU report after completion and reporting
Post by: Marius on 07 Aug 2009, 02:09:17 pm

Thats an incredible amount of work Fred! Some of it (mayby most) can be retrieved via the client_state where the results are cached before sending, but you can easely miss a couple of units this way (if boinc starts sending without you having parsed the file).

Another method is creating a tcp/ip proxy which cached all info you need. Personally i would opt for this one as its the easiest to build.


Another method would be to check the workunit online via http://setiathome.berkeley.edu/results.php?userid=xxxx, very slow and i'm sure the site can't handle a couple of hundreds users doing this <g>)

Groetjes,
Marius

Title: Re: Reading WU report after completion and reporting
Post by: Richard Haselgrove on 07 Aug 2009, 02:28:02 pm

We've discussed some other possibilities in Fred's parallel Reading WU report file after uploading (http://boinc.berkeley.edu/dev/forum_thread.php?id=4163) thread on the BOINC message boards. Jord's suggestion of monitoring the sched_request.xml messages sounds particularly promising.

Title: Re: Reading WU report after completion and reporting
Post by: efmer (fred) on 07 Aug 2009, 02:51:06 pm

Quote from: Marius on 07 Aug 2009, 02:09:17 pm

Thats an incredible amount of work Fred! Some of it (mayby most) can be retrieved via the client_state where the results are cached before sending, but you can easely miss a couple of units this way (if boinc starts sending without you having parsed the file).

Another method is creating a tcp/ip proxy which cached all info you need. Personally i would opt for this one as its the easiest to build.


Another method would be to check the workunit online via http://setiathome.berkeley.edu/results.php?userid=xxxx, very slow and i'm sure the site can't handle a couple of hundreds users doing this <g>)

Groetjes,
Marius

As I'm doing remote clients, proxy will be a bit complicated.
And I'm not afraid of a bit of work.
Ok the last method is marked illegal by SETI and punishable by....when automated that is.