Please, don't use any patched versions of Einstein@Home app.
The bad results caused some problems in the database.
Thanks!
edit: Probably these units will be send out again. ( about 5000 WUs at moment )
Hi Akos, how severe is this? Do we need to produce instructions for people to strip off all patches and get back to the 4.02 stock application? Will we be able to move forward with patches again later? Mike
Hi Akos, how severe is this? Do we need to produce instructions for
people to strip off all patches and get back to the 4.02 stock application? Will we be able to move forward with patches again later? Mike
Or is it possible to crunch with the stable versions?
Please, don't use any patched versions of Einstein@Home app.
The bad results caused some problems in the database.
Thanks!
edit: Probably these units will be send out again. ( about 5000 WUs at moment )
Hi Akos, how severe is this? Do we need to produce instructions for people to strip off all patches and get back to the 4.02 stock application? Will we be able to move forward with patches again later? Mike
I would think all you need to do is delete the app and/or app_info files and then update the project.
Alinator
PS: Of course if you had an app_info file you should abort any current work first.
Please, don't use any patched versions of Einstein@Home app.
The bad results caused some problems in the database.
Thanks!
edit: Probably these units will be send out again. ( about 5000 WUs at moment )
Hi Akos, how severe is this? Do we need to produce instructions for people to strip off all patches and get back to the 4.02 stock application? Will we be able to move forward with patches again later? Mike
I would think all you need to do is delete the app and/or app_info files and then update the project.
Alinator
I'm not sure it is quite that simple. If people have changed to reporting as a 4.10 application, they may need to set no new work, drain their cache or abort all WUs, stop BOINC, remove the app_info.xml file, start BOINC, reset the project etc, otherwise they may trash a load more WUs. A full set of instructions can be produced, but it is as much work going back safely as it was going to the patched application in the first place. There are a number of possible states people can be in. Mike
All, please see this. What
)
All, please see this. What is behind this I wonder. Mike
RE: All, please see this.
)
Should we stop crunching with every optimized app?! i'm using the last stable version (s5s0007)...
mfg bara
Hi people! Please, don't
)
Hi people!
Please, don't use any patched versions of Einstein@Home app.
The bad results caused some problems in the database.
Thanks!
edit: Probably these units will be send out again. ( about 5000 WUs at moment )
RE: Hi people! Please,
)
Hi Akos, how severe is this? Do we need to produce instructions for people to strip off all patches and get back to the 4.02 stock application? Will we be able to move forward with patches again later? Mike
RE: Hi people! Please,
)
I was wondering if the experimentals might cause a problem with the Initial Replication being reduced to two. Guess that answers the question. ;-)
Alinator
RE: Hi Akos, how severe is
)
Or is it possible to crunch with the stable versions?
akosf wrote: RE: Hi
)
akosf wrote:
What is so hard to understand?
- Please stop using it! -
Aloha, Uli
RE: RE: Hi
)
I would think all you need to do is delete the app and/or app_info files and then update the project.
Alinator
PS: Of course if you had an app_info file you should abort any current work first.
I don't understand how
)
I don't understand how results that pass validation can be bad.
Some more info please.
98SE XP2500+ @ 2.1 GHz Boinc v5.8.8
RE: RE: RE: Hi
)
I'm not sure it is quite that simple. If people have changed to reporting as a 4.10 application, they may need to set no new work, drain their cache or abort all WUs, stop BOINC, remove the app_info.xml file, start BOINC, reset the project etc, otherwise they may trash a load more WUs. A full set of instructions can be produced, but it is as much work going back safely as it was going to the patched application in the first place. There are a number of possible states people can be in. Mike