Exit BOINC.
Navigate to your BOINC\\projects\\einstein.phys.edu\\ directory and deleting the app_info.xml file and the Einstein executables.
Restart BOINC.
Reset Einstein@Home.
That will usually do it for you.
For anyone contemplating similar action (ie stopping the beta or power app and reverting to the official app) you need to give the matter a bit of thought.
In addition to what Jord said, you need to consider what you want to happen to work in progress on your machine. You may have already expended many hours on that work and don't want to waste it. You may also have a number of tasks in your cache of work that are "branded" with the beta app version number and which will be trashed as well if you just delete app_info.xml.
You can transition to a previous official app without loss but it is quite tricky and does require careful editing of app_info.xml. This is akin to ongoing manual management as you will need to continue managing app_info.xml for every subsequent app change that comes along.
If you are unsure about this and just wish to change without worry, you should
* set "No new work" (NNW) for the project,
* abort any unstarted work in your cache,
* allow the task(s) in progress to complete and report,
* then continue as Jord specified.
I don't know that you need to reset the project and I certainly wouldn't as all the data files will be replaced as well. Just deleting the app_info.xml file and the executables should be sufficient to force BOINC to get the official app files whilst allowing the use of the existing large data files you already have. There should be no need to download all that stuff again.
The main problem I had was that BOINC didn't download the official app once I'd removed all the files. I was getting work but didn't have an application to crunch it with.
If you already had some workunits downloaded they'll still use the old version.
Any new workunits you downloaded after you installed the new application should run with the new application.
At least that's how I understand it.
That's why it's important to drain the cache of WUs before switching back to the official app.
this new crunche times are, new crunches,from after the new,application.
things might have been changed,but it says that,its running the old 4.15
application,i might as well,delete the whole boinc-project and install again,
if things,do not work out,but i will wait a little time,maby somebody knows the
the problem and will see what the results are,after finishing the crunches.
this new crunche times are, new crunches,from after the new,application.
things might have been changed,but it says that,its running the old 4.15
application,i might as well,delete the whole boinc-project and install again,
if things,do not work out,but i will wait a little time,maby somebody knows the
the problem and will see what the results are,after finishing the crunches.
gr-rene holland.
This is normal behavior. The tasks you still have are crunched by the old application. Only newly downloaded work will be done with the new application.
----
Dit is normaal. Het werk dat je nog hebt wordt nog gedaan door de oude applicatie. Al het nieuwe werk dat je download zal worden gedaan door de nieuwe applicatie.
this new crunche times are, new crunches,from after the new,application.
things might have been changed,but it says that,its running the old 4.15
application,i might as well,delete the whole boinc-project and install again,
if things,do not work out,but i will wait a little time,maby somebody knows the
the problem and will see what the results are,after finishing the crunches.
gr-rene holland.
This is normal behavior. The tasks you still have are crunched by the old application. Only newly downloaded work will be done with the new application.
----
Dit is normaal. Het werk dat je nog hebt wordt nog gedaan door de oude applicatie. Al het nieuwe werk dat je download zal worden gedaan door de nieuwe applicatie.
No, this is not correct. The Old WUs have been labeled with the ID of the app in use when they were downloaded, but the app_info.xml file forces them to be crunched with the new app although they still retain the old label. Like Astro says, use taskmanager to verify what program is actually running.
this new crunche times are, new crunches,from after the new,application.
things might have been changed,but it says that,its running the old 4.15
application,i might as well,delete the whole boinc-project and install again,
if things,do not work out,but i will wait a little time,maby somebody knows the
the problem and will see what the results are,after finishing the crunches.
gr-rene holland.
This is normal behavior. The tasks you still have are crunched by the old application. Only newly downloaded work will be done with the new application.
----
Dit is normaal. Het werk dat je nog hebt wordt nog gedaan door de oude applicatie. Al het nieuwe werk dat je download zal worden gedaan door de nieuwe applicatie.
No, this is not correct. The Old WUs have been labeled with the ID of the app in use when they were downloaded, but the app_info.xml file forces them to be crunched with the new app although they still retain the old label. Like Astro says, use taskmanager to verify what program is actually running.
Well, it would be running the new ap while showing the old number in boincmgr if the installation was done right, but just without seeing the new ap number in taskinfo, or Process Explorer, or stderr out, one can't say it is working right.
Looking at your web task page, I see three results reported at 6 Mar 2008 19:54:23 UTC as the most recent reports.
Looking at the task page for each, in the stderr out section, I look for lines of this form:
There is one very near the beginning, and that tells what ap you first started work on the result with, On restarts there is a new such line, but scrolling to the end of these three all I see is 4.15.
So as of 6 Mar 2008 19:54:23 UTC I don't think your host had reported any results for which 4.36 did any of the work.
As to execution times, there does not seem to be any such shift as you report in recent times for reported tasks, and for a Q6600 running 4.15 at stock speed your times are entirely reasonable. Going straight from there to 4.36 should give you a nearly 2:1 speedup for results at a comparable point in the cycle.
The reports on your task page show about 10 CPU hours for completion using 4.15. If those are now taking 25 elapsed hours, it suggests that some other process than Einstein may be using a major amount of resource on your system. If you take a look in Task Manager to verify the version number, you might want to look at CPU time consumption by other processes.
Of course if you have results on your host which have completed but have not been reported it is possible they may have used 4.36 and possible that they may have used 25 CPU hours, but not the ones I can see.
this new crunche times are, new crunches,from after the new,application.
things might have been changed,but it says that,its running the old 4.15
application,i might as well,delete the whole boinc-project and install again,
if things,do not work out,but i will wait a little time,maby somebody knows the
the problem and will see what the results are,after finishing the crunches.
gr-rene holland.
This is normal behavior. The tasks you still have are crunched by the old application. Only newly downloaded work will be done with the new application.
----
Dit is normaal. Het werk dat je nog hebt wordt nog gedaan door de oude applicatie. Al het nieuwe werk dat je download zal worden gedaan door de nieuwe applicatie.
No, this is not correct. The Old WUs have been labeled with the ID of the app in use when they were downloaded, but the app_info.xml file forces them to be crunched with the new app although they still retain the old label. Like Astro says, use taskmanager to verify what program is actually running.
Well, it would be running the new ap while showing the old number in boincmgr if the installation was done right, but just without seeing the new ap number in taskinfo, or Process Explorer, or stderr out, one can't say it is working right.
Looking at your web task page, I see three results reported at 6 Mar 2008 19:54:23 UTC as the most recent reports.
Looking at the task page for each, in the stderr out section, I look for lines of this form:
There is one very near the beginning, and that tells what ap you first started work on the result with, On restarts there is a new such line, but scrolling to the end of these three all I see is 4.15.
So as of 6 Mar 2008 19:54:23 UTC I don't think your host had reported any results for which 4.36 did any of the work.
As to execution times, there does not seem to be any such shift as you report in recent times for reported tasks, and for a Q6600 running 4.15 at stock speed your times are entirely reasonable. Going straight from there to 4.36 should give you a nearly 2:1 speedup for results at a comparable point in the cycle.
The reports on your task page show about 10 CPU hours for completion using 4.15. If those are now taking 25 elapsed hours, it suggests that some other process than Einstein may be using a major amount of resource on your system. If you take a look in Task Manager to verify the version number, you might want to look at CPU time consumption by other processes.
Of course if you have results on your host which have completed but have not been reported it is possible they may have used 4.36 and possible that they may have used 25 CPU hours, but not the ones I can see.
Sounds to me as if our friend did install the new 4.36 app and the new ap_info.xml, but forgot to restart boinc. Indeed, only after a restart the new info of the new app_info.xml will be read and so force the use of the new 4.36 app even for WUs that were started with older versions.
RE: RE: Just removing
)
For anyone contemplating similar action (ie stopping the beta or power app and reverting to the official app) you need to give the matter a bit of thought.
In addition to what Jord said, you need to consider what you want to happen to work in progress on your machine. You may have already expended many hours on that work and don't want to waste it. You may also have a number of tasks in your cache of work that are "branded" with the beta app version number and which will be trashed as well if you just delete app_info.xml.
You can transition to a previous official app without loss but it is quite tricky and does require careful editing of app_info.xml. This is akin to ongoing manual management as you will need to continue managing app_info.xml for every subsequent app change that comes along.
If you are unsure about this and just wish to change without worry, you should
* abort any unstarted work in your cache,
* allow the task(s) in progress to complete and report,
* then continue as Jord specified.
I don't know that you need to reset the project and I certainly wouldn't as all the data files will be replaced as well. Just deleting the app_info.xml file and the executables should be sufficient to force BOINC to get the official app files whilst allowing the use of the existing large data files you already have. There should be no need to download all that stuff again.
Cheers,
Gary.
The main problem I had was
)
The main problem I had was that BOINC didn't download the official app once I'd removed all the files. I was getting work but didn't have an application to crunch it with.
I had already emptied my cache of WU.
hello, i installed this
)
hello,
i installed this new 4.36 app, i might HAVE A PROBLEM ,
my new crunches are 25 hours instead of 10 hours,
i use to run the 4.15 app,the task bar still says,i have the 4.15 aplication,
running,does somebody recognize or know the problem.
rene holland
If you already had some
)
If you already had some workunits downloaded they'll still use the old version.
Any new workunits you downloaded after you installed the new application should run with the new application.
At least that's how I understand it.
That's why it's important to drain the cache of WUs before switching back to the official app.
this new crunche times are,
)
this new crunche times are, new crunches,from after the new,application.
things might have been changed,but it says that,its running the old 4.15
application,i might as well,delete the whole boinc-project and install again,
if things,do not work out,but i will wait a little time,maby somebody knows the
the problem and will see what the results are,after finishing the crunches.
gr-rene holland.
Bluegiant, why not use "task
)
Bluegiant, why not use "task manager" to see which app is actually running? right click on the task bar, select "taskmanager", and see.
RE: this new crunche
)
This is normal behavior. The tasks you still have are crunched by the old application. Only newly downloaded work will be done with the new application.
----
Dit is normaal. Het werk dat je nog hebt wordt nog gedaan door de oude applicatie. Al het nieuwe werk dat je download zal worden gedaan door de nieuwe applicatie.
RE: RE: this new
)
No, this is not correct. The Old WUs have been labeled with the ID of the app in use when they were downloaded, but the app_info.xml file forces them to be crunched with the new app although they still retain the old label. Like Astro says, use taskmanager to verify what program is actually running.
Seti Classic Final Total: 11446 WU.
RE: RE: RE: this new
)
Well, it would be running the new ap while showing the old number in boincmgr if the installation was done right, but just without seeing the new ap number in taskinfo, or Process Explorer, or stderr out, one can't say it is working right.
Looking at your web task page, I see three results reported at 6 Mar 2008 19:54:23 UTC as the most recent reports.
Looking at the task page for each, in the stderr out section, I look for lines of this form:
command line: projects/einstein.phys.uwm.edu/einstein_S5R3_4.15_windows_intelx86.exeThere is one very near the beginning, and that tells what ap you first started work on the result with, On restarts there is a new such line, but scrolling to the end of these three all I see is 4.15.
So as of 6 Mar 2008 19:54:23 UTC I don't think your host had reported any results for which 4.36 did any of the work.
As to execution times, there does not seem to be any such shift as you report in recent times for reported tasks, and for a Q6600 running 4.15 at stock speed your times are entirely reasonable. Going straight from there to 4.36 should give you a nearly 2:1 speedup for results at a comparable point in the cycle.
The reports on your task page show about 10 CPU hours for completion using 4.15. If those are now taking 25 elapsed hours, it suggests that some other process than Einstein may be using a major amount of resource on your system. If you take a look in Task Manager to verify the version number, you might want to look at CPU time consumption by other processes.
Of course if you have results on your host which have completed but have not been reported it is possible they may have used 4.36 and possible that they may have used 25 CPU hours, but not the ones I can see.
RE: RE: RE: RE:
)
Sounds to me as if our friend did install the new 4.36 app and the new ap_info.xml, but forgot to restart boinc. Indeed, only after a restart the new info of the new app_info.xml will be read and so force the use of the new 4.36 app even for WUs that were started with older versions.
Kind regards
Kind regards
Alain