> Example: One user have a two computers - one for CPDN and another - for
> Einstein@Home.
> Both accounts created with using same e-mail address, but absolutely
> separately. First computer only for CPDN, and another computer - only for
> Einstein. What "say" the statistic systems about this situation?
>
There will be two separate CPIDs as there is no path from project server to client to project server that covers all project servers.
you could always make sure that a computer for which the "real" cpid is known is attached to a new project until you're sure the cpid is syncronized for your new project account - and then dettach it again if you want. At least that's how I'd do it. I have a primary computer that currently runs all projects I participate in, but some day that computer can't handle any more projects. Then I'll branch out a bit, but always attach the primary computer to any new projects first, and make sure the correct cpid is registered on my new project account.
> you could always make sure that a computer for which the "real" cpid is known
> is attached to a new project until you're sure the cpid is syncronized for
> your new project account - and then dettach it again if you want. At least
> that's how I'd do it. I have a primary computer that currently runs all
> projects I participate in, but some day that computer can't handle any more
> projects. Then I'll branch out a bit, but always attach the primary computer
> to any new projects first, and make sure the correct cpid is registered on my
> new project account.
>
The latest debelopment version of BOINC does its best to meet deadlines, and honor your resource shares. However in doing this, it may not keep all of the projects that you have signed up for on your computer at all times. It may also not crunch in a round robin all of the time. However, it maintains a debt ofer a long term, and crunches the nearest deadline result when it has to.
1) If participant joins to other project for synchronize cpid, he must download all units with data? Or after two seconds of participating, he can detach from project?
2) What we should make, if participant already have two separate computers that crunching data from different projects? Attaching for second project from "main computer", and update project from another?
Thank you Bruno G. Olsen, thank you John McLeod VII!
> Two questions:
>
> 1) If participant joins to other project for synchronize cpid, he must
> download all units with data? Or after two seconds of participating, he can
> detach from project?
It would take some time and connections for the cpid to get sync'd. Personally I would attach to the second project on the main computer, let it download the client and the first (batch of) wu(s), then turn of requests for more work at that computer for that project, and let the wu(s) finish and get reported before dettaching again. This way I wouldn't be the course of a slowdown of the project progress and I would be more certain that the cpid would have been sync'd ;)
> 2) What we should make, if participant already have two separate computers
> that crunching data from different projects? Attaching for second project from
> "main computer", and update project from another?
hmm. guess some of this was answered above :) As mentioned, cpid sync can take some time, but given that time this would be the approach, yes.
> Hi
>
> The result must returned by the same machine it was downloaded with.
> You can´t transferring results between puters.
True. On another board someone asked if it was possible to download wu's to a shared folder in a lan, and then have whatever computer on that lan he was logged onto continue where another left of (possible in seti classic), and that would not be possible with boinc
> Two questions:
>
> 1) If participant joins to other project for synchronize cpid, he must
> download all units with data? Or after two seconds of participating, he can
> detach from project?
You will probably get some work whild synchronizing the CPIDs. If you use 4.25 and BOINC View you can request no more work for a project and crunch it down after the initial download. With 4.32? 4.35? you should b3e able to attach each computer to as many projects as you like and almost all of the work will get in on time.
>
> 2) What we should make, if participant already have two separate computers
> that crunching data from different projects? Attaching for second project from
> "main computer", and update project from another?
It sort of depends on which version of BOINC you are running. In 4.19, this will work. In 4.25 and later, you may have to connect both computers to both projects for a time.
>
> Thank you Bruno G. Olsen, thank you John McLeod VII!
>
> Example: One user have a
)
> Example: One user have a two computers - one for CPDN and another - for
> Einstein@Home.
> Both accounts created with using same e-mail address, but absolutely
> separately. First computer only for CPDN, and another computer - only for
> Einstein. What "say" the statistic systems about this situation?
>
There will be two separate CPIDs as there is no path from project server to client to project server that covers all project servers.
BOINC WIKI
you could always make sure
)
you could always make sure that a computer for which the "real" cpid is known is attached to a new project until you're sure the cpid is syncronized for your new project account - and then dettach it again if you want. At least that's how I'd do it. I have a primary computer that currently runs all projects I participate in, but some day that computer can't handle any more projects. Then I'll branch out a bit, but always attach the primary computer to any new projects first, and make sure the correct cpid is registered on my new project account.
> you could always make sure
)
> you could always make sure that a computer for which the "real" cpid is known
> is attached to a new project until you're sure the cpid is syncronized for
> your new project account - and then dettach it again if you want. At least
> that's how I'd do it. I have a primary computer that currently runs all
> projects I participate in, but some day that computer can't handle any more
> projects. Then I'll branch out a bit, but always attach the primary computer
> to any new projects first, and make sure the correct cpid is registered on my
> new project account.
>
The latest debelopment version of BOINC does its best to meet deadlines, and honor your resource shares. However in doing this, it may not keep all of the projects that you have signed up for on your computer at all times. It may also not crunch in a round robin all of the time. However, it maintains a debt ofer a long term, and crunches the nearest deadline result when it has to.
BOINC WIKI
Two questions: 1) If
)
Two questions:
1) If participant joins to other project for synchronize cpid, he must download all units with data? Or after two seconds of participating, he can detach from project?
2) What we should make, if participant already have two separate computers that crunching data from different projects? Attaching for second project from "main computer", and update project from another?
Thank you Bruno G. Olsen, thank you John McLeod VII!
Hi The result must
)
Hi
The result must returned by the same machine it was downloaded with.
You can´t transferring results between puters.
greetz Mike
> Two questions: > > 1) If
)
> Two questions:
>
> 1) If participant joins to other project for synchronize cpid, he must
> download all units with data? Or after two seconds of participating, he can
> detach from project?
It would take some time and connections for the cpid to get sync'd. Personally I would attach to the second project on the main computer, let it download the client and the first (batch of) wu(s), then turn of requests for more work at that computer for that project, and let the wu(s) finish and get reported before dettaching again. This way I wouldn't be the course of a slowdown of the project progress and I would be more certain that the cpid would have been sync'd ;)
> 2) What we should make, if participant already have two separate computers
> that crunching data from different projects? Attaching for second project from
> "main computer", and update project from another?
hmm. guess some of this was answered above :) As mentioned, cpid sync can take some time, but given that time this would be the approach, yes.
> Hi > > The result must
)
> Hi
>
> The result must returned by the same machine it was downloaded with.
> You can´t transferring results between puters.
True. On another board someone asked if it was possible to download wu's to a shared folder in a lan, and then have whatever computer on that lan he was logged onto continue where another left of (possible in seti classic), and that would not be possible with boinc
> Two questions: > > 1) If
)
> Two questions:
>
> 1) If participant joins to other project for synchronize cpid, he must
> download all units with data? Or after two seconds of participating, he can
> detach from project?
You will probably get some work whild synchronizing the CPIDs. If you use 4.25 and BOINC View you can request no more work for a project and crunch it down after the initial download. With 4.32? 4.35? you should b3e able to attach each computer to as many projects as you like and almost all of the work will get in on time.
>
> 2) What we should make, if participant already have two separate computers
> that crunching data from different projects? Attaching for second project from
> "main computer", and update project from another?
It sort of depends on which version of BOINC you are running. In 4.19, this will work. In 4.25 and later, you may have to connect both computers to both projects for a time.
>
> Thank you Bruno G. Olsen, thank you John McLeod VII!
>
BOINC WIKI