No you don't need to do anything. Once the work unit is complete, the result is uploaded to Einstein server. Status of the Work Unit on your client will now say 'ready to report'.
Next time your PC connects to the host, it will report that result and you will then be eligible to receive Credit for that result.
I don't know why the results are spit into 2 stages like this.. perhaps one of the BOINC gurus will be able to answer that one!
anyway, the upshot: you don't need to do anything. The client will take care of itself in due course.
> Hi all,finished my first project and it say ready to report,do i have to do
> anything as im online almost all of the time.ie is it auto sending.Thanks
>
>
> oh yeah and im using boinc 4.19
You can just wait and it will get uploaded. OR you can do 'update project' and it will get uploaded right away, and you'll possibly get new work at the same time.
> I don't know why the results are spit into 2 stages like this.. perhaps one of
> the BOINC gurus will be able to answer that one!
As far as I understand:
you cannot upload and report at the same time - imagine if you report, and the download still takes more time. But at the server end the result set is complete, and here validator kicks in. But it will not find the result files yet, or they would be incomplete. So it would mark the result as "invalid", and there would be no use of the data files uploaded three seconds later :)
> As far as I understand:
>
> you cannot upload and report at the same time - imagine if you report, and the
> download still takes more time. But at the server end the result set is
> complete, and here validator kicks in. But it will not find the result files
> yet, or they would be incomplete. So it would mark the result as "invalid",
> and there would be no use of the data files uploaded three seconds later :)
More importantly (perhaps) is that you are also involving more servers. The Result Data File(s) (to separate them from the "Result" itself) are uploaded to the data server. The "Reporting" talks to the scheduling server (and also, through that, the database server). So, now, if you have ANY bottleneck you have bolixed up a lot of stuff, and, with insurance built in to not lose work, well, your time issues get even more important in the dance.
By making it a two stage process, the data server loads have nothing in common with the scheduling server loads. So, if it takes longer to upload the data files we don't have to maintain a connection to the scheduling server open at the same time. SO, with a disconenct between the two parts, the system is "looser" and more sustainable ...
ready to report
)
Hi Pincher.
No you don't need to do anything. Once the work unit is complete, the result is uploaded to Einstein server. Status of the Work Unit on your client will now say 'ready to report'.
Next time your PC connects to the host, it will report that result and you will then be eligible to receive Credit for that result.
I don't know why the results are spit into 2 stages like this.. perhaps one of the BOINC gurus will be able to answer that one!
anyway, the upshot: you don't need to do anything. The client will take care of itself in due course.
Paul.
Wanna visit BOINC Synergy site? Click my stats!
Join BOINC Synergy Team
many thanks for getting back
)
many thanks for getting back so quick paul.i can relax now.
No problem!
)
No problem!
Wanna visit BOINC Synergy site? Click my stats!
Join BOINC Synergy Team
> Hi all,finished my first
)
> Hi all,finished my first project and it say ready to report,do i have to do
> anything as im online almost all of the time.ie is it auto sending.Thanks
>
>
> oh yeah and im using boinc 4.19
You can just wait and it will get uploaded. OR you can do 'update project' and it will get uploaded right away, and you'll possibly get new work at the same time.
Bruce
Director, Einstein@Home
> I don't know why the
)
> I don't know why the results are spit into 2 stages like this.. perhaps one of
> the BOINC gurus will be able to answer that one!
As far as I understand:
you cannot upload and report at the same time - imagine if you report, and the download still takes more time. But at the server end the result set is complete, and here validator kicks in. But it will not find the result files yet, or they would be incomplete. So it would mark the result as "invalid", and there would be no use of the data files uploaded three seconds later :)
Administrator
Message@Home
> As far as I understand: >
)
> As far as I understand:
>
> you cannot upload and report at the same time - imagine if you report, and the
> download still takes more time. But at the server end the result set is
> complete, and here validator kicks in. But it will not find the result files
> yet, or they would be incomplete. So it would mark the result as "invalid",
> and there would be no use of the data files uploaded three seconds later :)
More importantly (perhaps) is that you are also involving more servers. The Result Data File(s) (to separate them from the "Result" itself) are uploaded to the data server. The "Reporting" talks to the scheduling server (and also, through that, the database server). So, now, if you have ANY bottleneck you have bolixed up a lot of stuff, and, with insurance built in to not lose work, well, your time issues get even more important in the dance.
By making it a two stage process, the data server loads have nothing in common with the scheduling server loads. So, if it takes longer to upload the data files we don't have to maintain a connection to the scheduling server open at the same time. SO, with a disconenct between the two parts, the system is "looser" and more sustainable ...