...The effect of this would be that for some days there will be both S5R2 and S5R3 workunits in the database of which no task has even been sent to a host yet. The transition will be rather smooth and long.
BM
When will you switch the regular application to version 4.40 (or to another version?)? I am using the beta 4.40, and want to continue to use it rather than revert back to 4.38 by removing the beta app_info.xml file too prematurely.
I don't want to remove the beta app_info.xml file until the new regular application for S5R3 is available for download! ;)
...If you have an outdated beta app with a app_info.xml file installed, the automatic app software update mechanism is suspended and you won't get a new app. But any outdated beta app will not have the extra feature Bernd mentioned that is used in S5R3 so you won't get S5R3 tasks once the new run begins, which will happen rather sooner than later as S5R2 is 95% complete now.
CU
H-BE
Do you know if one can remove the app_info.xml file in the middle of processing a workunit and have the workunit proceed to completion? Or does it trash the workunit?
Do you know if one can remove the app_info.xml file in the middle of processing a workunit and have the workunit proceed to completion? Or does it trash the workunit?
That specific sequence trashes not only the in-process result, but any already downloaded results. However, I think things are somehow smart enough to re-assign you the not yet processed ones, at least in some cases.
This differs from the more favorable situation in which you _add_ an app_info.xml where there was none (or a different one) before.
Turning off downloading and working off your entire queue before removing it is safest.
Alternatively, choosing a moment when the in-process work has little CPU time invested would avoid most wastage.
...That specific sequence trashes not only the in-process result, but any already downloaded results. However, I think things are somehow smart enough to re-assign you the not yet processed ones, at least in some cases.
This differs from the more favorable situation in which you _add_ an app_info.xml where there was none (or a different one) before.
Turning off downloading and working off your entire queue before removing it is safest.
Alternatively, choosing a moment when the in-process work has little CPU time invested would avoid most wastage.
Thanks!
I guess I can afford to wait awhile before I do anything, since the beta 4.40 version will work with the new S5R3 workunits.
The amount of data necessary for a workunit will raise to 35-55 MB (depending on the base frequency). For the lower frequency bands we will use the same data files than we did for S5R2, so we intend to switch off deletion of the S5R2 data files on your machines at some point and you don't have to download a whole completely new set of data files again, just the ones you don't already have left over from S5R2.
Done.
Quote:
The plan is that at some time at the end of this week we'll force the S5R2 workunits generator to write all remaining S5R2 workunits into the database (which will make it stop), and then start the workunit generator for S5R3.
We've generated the remaining S5R2 workunits and put them into the database. You'll find the S5R2 work generator isn't running anymore (Server Status page). This allows us to start the Work generator for S5R3 soon.
...We've generated the remaining S5R2 workunits and put them into the database. You'll find the S5R2 work generator isn't running anymore (Server Status page). This allows us to start the Work generator for S5R3 soon.
BM
Thanks for the exciting news! E@h moving on to a new phase is very exciting, as we close in on the search for the elusive gravity waves!
...We've generated the remaining S5R2 workunits and put them into the database. You'll find the S5R2 work generator isn't running anymore (Server Status page). This allows us to start the Work generator for S5R3 soon.
BM
Thanks for the exciting news! E@h moving on to a new phase is very exciting, as we close in on the search for the elusive gravity waves!
I've always had the question: How do we crunchers surf the wave once we find it? Gravity boards are expensive, no? Please advise on this important topic. Good to get ahead of everyone else once the rush to surf starts! :-)
Lol Gerry... I might have to learn to surf first. Not that many waves here in Western Germany, so the only thing I ever "surf" are websites... maybe I should hurry up learning in case we get successful with S5R3. And maybe we'll meet someone while we're surfing... the SETI guys would never live that one down XD finding ET while going gravity wave surfing.
@Bernd: Great news indeed. What do we have to expect in terms of performance? Will the new science app be more efficient, or roughly the same?
@all: We should open a new thread to see whoever gets one of the new WUs first...
RE: ...The effect of this
)
When will you switch the regular application to version 4.40 (or to another version?)? I am using the beta 4.40, and want to continue to use it rather than revert back to 4.38 by removing the beta app_info.xml file too prematurely.
I don't want to remove the beta app_info.xml file until the new regular application for S5R3 is available for download! ;)
Thanks!
RE: ...If you have an
)
Do you know if one can remove the app_info.xml file in the middle of processing a workunit and have the workunit proceed to completion? Or does it trash the workunit?
Thanks!
RE: Do you know if one can
)
That specific sequence trashes not only the in-process result, but any already downloaded results. However, I think things are somehow smart enough to re-assign you the not yet processed ones, at least in some cases.
This differs from the more favorable situation in which you _add_ an app_info.xml where there was none (or a different one) before.
Turning off downloading and working off your entire queue before removing it is safest.
Alternatively, choosing a moment when the in-process work has little CPU time invested would avoid most wastage.
RE: ...That specific
)
Thanks!
I guess I can afford to wait awhile before I do anything, since the beta 4.40 version will work with the new S5R3 workunits.
RE: The amount of data
)
Done.
We've generated the remaining S5R2 workunits and put them into the database. You'll find the S5R2 work generator isn't running anymore (Server Status page). This allows us to start the Work generator for S5R3 soon.
BM
BM
RE: ...We've generated the
)
Thanks for the exciting news! E@h moving on to a new phase is very exciting, as we close in on the search for the elusive gravity waves!
RE: RE: ...We've
)
I've always had the question: How do we crunchers surf the wave once we find it? Gravity boards are expensive, no? Please advise on this important topic. Good to get ahead of everyone else once the rush to surf starts! :-)
(Click for detailed stats)
Lol Gerry... I might have to
)
Lol Gerry... I might have to learn to surf first. Not that many waves here in Western Germany, so the only thing I ever "surf" are websites... maybe I should hurry up learning in case we get successful with S5R3. And maybe we'll meet someone while we're surfing... the SETI guys would never live that one down XD finding ET while going gravity wave surfing.
@Bernd: Great news indeed. What do we have to expect in terms of performance? Will the new science app be more efficient, or roughly the same?
@all: We should open a new thread to see whoever gets one of the new WUs first...
Look at me! I have the same
)
Look at me! I have the same name as the guy who started this thread, and his profile links to mine!
MattDavis_2 wrote:Look at
)
Do you mean that you are not the thread starter and it was falsely attributed to you?