Any news about the S5R5 run mentioned earlier in this thread?? it was supposed to begin soon, because of some kind of bug on the results of the S5R4...
Any news about the S5R5 run mentioned earlier in this thread?? it was supposed to begin soon, because of some kind of bug on the results of the S5R4...
Will definitely come. We're still testing and tweaking the setup. Some facts so far:
- slightly increased memory requirement
- larger "dwell time" per sky location. This is limiting the maximum checkpoint rate to about once per 3 min (on current average CPUs, longer on slower ones)
- workunits will run roughly half as long as S5R4 ones
Any news about the S5R5 run mentioned earlier in this thread?? it was supposed to begin soon, because of some kind of bug on the results of the S5R4...
Will definitely come. We're still testing and tweaking the setup. Some facts so far:
- slightly increased memory requirement
- larger "dwell time" per sky location. This is limiting the maximum checkpoint rate to about once per 3 min (on current average CPUs, longer on slower ones)
- workunits will run roughly half as long as S5R4 ones
BM
Hi Bernd,
Can we use the current (605) power app, or will we need a new app/app_info?
Any news about the S5R5 run mentioned earlier in this thread?? it was supposed to begin soon, because of some kind of bug on the results of the S5R4...
Will definitely come. We're still testing and tweaking the setup. Some facts so far:
- slightly increased memory requirement
- larger "dwell time" per sky location. This is limiting the maximum checkpoint rate to about once per 3 min (on current average CPUs, longer on slower ones)
- workunits will run roughly half as long as S5R4 ones
BM
Hi Bernd,
Can we use the current (605) power app, or will we need a new app/app_info?
S5R5 will require new binaries that are currently under test.
CU
Bikeman
S5R5 will require new binaries that are currently under test.
CU
Bikeman
I presume there will be a similar rundown of S5R4 and change over to S5R5 as there was for the start of the S5R4? Meaning those that want to initially stick to the S5R4 WUs can do so until these get scarce?
One driver will be the credit, and RAC, given between the R4 and R5. If similar then own choices, if the R5 is slightly better, then the run down of R4 may take longer than planned.
Shih-Tzu are clever, cuddly, playful and rule!! Jack Russell are feisty!
Also, the S5R5 run will work on the existing S5R4 datafiles, so the transition form S5R4 to S5R5 should be much smoother than the previous one from S5R3 to S5R4 where it was not possible to re-use downloaded datafiles from the previous run.
Also, the S5R5 run will work on the existing S5R4 datafiles, so the transition form S5R4 to S5R5 should be much smoother than the previous one from S5R3 to S5R4 where it was not possible to re-use downloaded datafiles from the previous run.
CU
Bikeman
That sounds good then!
Shih-Tzu are clever, cuddly, playful and rule!! Jack Russell are feisty!
If this run hits, what's the best way to get rid of the optimized application? Resetting the project is what I usually do, but there must be better ways
If this run hits, what's the best way to get rid of the optimized application? Resetting the project is what I usually do, but there must be better ways
Drain your queue (set no-new-work)
Report results when it's empty
Shutdown BOINC (make sure it's down all the way)
Remove app_info.xml file
Restart BOINC and enable new work
S5R5 plans
)
Will definitely come. We're still testing and tweaking the setup. Some facts so far:
- slightly increased memory requirement
- larger "dwell time" per sky location. This is limiting the maximum checkpoint rate to about once per 3 min (on current average CPUs, longer on slower ones)
- workunits will run roughly half as long as S5R4 ones
BM
BM
RE: RE: Any news about
)
Hi Bernd,
Can we use the current (605) power app, or will we need a new app/app_info?
BOINC blog
RE: RE: RE: Any news
)
S5R5 will require new binaries that are currently under test.
CU
Bikeman
RE: S5R5 will require new
)
I presume there will be a similar rundown of S5R4 and change over to S5R5 as there was for the start of the S5R4? Meaning those that want to initially stick to the S5R4 WUs can do so until these get scarce?
One driver will be the credit, and RAC, given between the R4 and R5. If similar then own choices, if the R5 is slightly better, then the run down of R4 may take longer than planned.
Shih-Tzu are clever, cuddly, playful and rule!! Jack Russell are feisty!
RE: Can we use the current
)
The S5R5 Windows App will feature the code that makes the S5R4 6.05 App as fast as it is.
There is no change in crediting targeted for S5R5.
BM
BM
Also, the S5R5 run will work
)
Also, the S5R5 run will work on the existing S5R4 datafiles, so the transition form S5R4 to S5R5 should be much smoother than the previous one from S5R3 to S5R4 where it was not possible to re-use downloaded datafiles from the previous run.
CU
Bikeman
RE: Also, the S5R5 run will
)
That sounds good then!
Shih-Tzu are clever, cuddly, playful and rule!! Jack Russell are feisty!
Partly on topic: If this
)
Partly on topic:
If this run hits, what's the best way to get rid of the optimized application? Resetting the project is what I usually do, but there must be better ways
RE: Partly on topic: If
)
Drain your queue (set no-new-work)
Report results when it's empty
Shutdown BOINC (make sure it's down all the way)
Remove app_info.xml file
Restart BOINC and enable new work
Seti Classic Final Total: 11446 WU.
So...the result of S5R4 would
)
So...the result of S5R4 would still make any sense? If not, I'd like to stop running this project until S5R5 comes out.
YG
Welcome To Team China!