Questions and Answers :
Windows :
Status "Ready to report" after upload
Message board moderation
Author | Message |
---|---|
Sir Alan Send message Joined: 21 Sep 02 Posts: 17 Credit: 235,035 RAC: 0 ![]() |
The status of each completed task is "Ready to report". This status does not change after the result has been uploaded successfully. Surely the status should then be something like "Reported" or "Uploaded"? "Progress just makes bad things happen faster." - Granny Weatherwax |
![]() ![]() Send message Joined: 20 Aug 02 Posts: 3083 Credit: 150,096 RAC: 0 ![]() |
|
Sir Alan Send message Joined: 21 Sep 02 Posts: 17 Credit: 235,035 RAC: 0 ![]() |
> You will find the answer in this thread. That's the answer to a different question. I did not ask how to upload results. I said the status remains unchanged ("Ready to report") after the result has been uploaded successfully (i.e. reported). "Progress just makes bad things happen faster." - Granny Weatherwax |
EclipseHA Send message Joined: 28 Jul 99 Posts: 1018 Credit: 530,719 RAC: 0 ![]() |
> > You will find the answer in this thread. > > That's the answer to a different question. I did not ask how to upload > results. I said the status remains unchanged ("Ready to report") after the > result has been uploaded successfully (i.e. reported). > > > "Progress just makes bad things happen faster." - Granny Weatherwax > Returning results is for some reason, a two step process.. When processing is complete, the results are sent back to BOINC. The WU then becomes "Ready to Report". Sometime later, the scheduler is contacted (may be when the next WU finishes), and then WU1 is "reported". WU2 then becomes "ready to report"! To Manually advance it from RTR, (windows), go to projects, right click on seti, and choose update... On Linux, I user "-report_results_immediately" on the command line, and this seems to work unless the scheduler/project is down. "Ready to Report" has confused me for months (as to the reason for the delay). It just seems that when the results have been uploaded, it should be reported to the scheduler, without this delay. |
Sir Alan Send message Joined: 21 Sep 02 Posts: 17 Credit: 235,035 RAC: 0 ![]() |
Thanks for that, Woody, it makes it a bit clearer. One of my pcs now has five completed tasks in "Ready to report" status, all of them having been uploaded... Seems designed to confuse! "Progress just makes bad things happen faster." - Granny Weatherwax |
![]() Send message Joined: 3 Apr 99 Posts: 70 Credit: 948 RAC: 0 ![]() |
> Thanks for that, Woody, it makes it a bit clearer. One of my pcs now has five > completed tasks in "Ready to report" status, all of them having been > uploaded... Seems designed to confuse! > "Progress just makes bad things happen faster." - Granny Weatherwax > the wu's are removed when they are uploaded ttyl Jeff |
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0 ![]() |
> > > You will find the answer in this thread. > > > > That's the answer to a different question. I did not ask how to upload > > results. I said the status remains unchanged ("Ready to report") after > the > > result has been uploaded successfully (i.e. reported). > > > > > > "Progress just makes bad things happen faster." - Granny Weatherwax > > > > Returning results is for some reason, a two step process.. > > When processing is complete, the results are sent back to BOINC. The WU then > becomes "Ready to Report". > > Sometime later, the scheduler is contacted (may be when the next WU finishes), > and then WU1 is "reported". WU2 then becomes "ready to report"! > > To Manually advance it from RTR, (windows), go to projects, right click on > seti, and choose update... On Linux, I user "-report_results_immediately" on > the command line, and this seems to work unless the scheduler/project is > down. > > "Ready to Report" has confused me for months (as to the reason for the delay). > It just seems that when the results have been uploaded, it should be reported > to the scheduler, without this delay. > I believe the design was done this way to reduce server load. ![]() |
©2025 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.