I just tried reinstalling ("repairing") BOINC 4.45, and that worked! However, it looks like Einstein 0.03 trashed the workunits I was working in under Einstein 4.79, which was unfortunate because I was close to finishing a WU!
Big deal...they're only 6 hours on my PC. Unless you're running a slow PC it shouldn't be a problem to lose 2 WU's.
Can we edit the app_info.xml file so that the beta application will crunch the Einstein WU's already in our cache?
No. The info in the app_info file is needed to help us track the outcome of the beta test apps. As far as I know the client will trash the first result when you switch to using the test app, but all the other results in you que should run fine.
I just installed the beta test version (just after finishing a WU). I suspended the task - and got a new WU (of course) ;-)
I 'stopped' the project ('no new work') and then suspended the second WU and the stopped the client.
After starting version 0.03 I got the following messages for *BOTH* WUs:
2005-06-21 09:14:24 [Einstein@Home] WU refers to nonexistent app_version: einstein 479
2005-06-21 09:14:24 [Einstein@Home] Can't link workunit in state file
--> all your WUs with a different version are cancelled!
Can we edit the app_info.xml file so that the beta application will crunch the Einstein WU's already in our cache?
No. The info in the app_info file is needed to help us track the outcome of the beta test apps. As far as I know the client will trash the first result when you switch to using the test app, but all the other results in you que should run fine.
I just installed the beta test version (just after finishing a WU). I suspended the task - and got a new WU (of course) ;-)
I 'stopped' the project ('no new work') and then suspended the second WU and the stopped the client.
After starting version 0.03 I got the following messages for *BOTH* WUs:
2005-06-21 09:14:24 [Einstein@Home] WU refers to nonexistent app_version: einstein 479
2005-06-21 09:14:24 [Einstein@Home] Can't link workunit in state file
--> all your WUs with a different version are cancelled!
...just another info...
the cancelled WUs are still active in the database (but no longer available on my computer)...
so they will time out in 7 days!
Is there any possibility to mark these WUs as no longer active?
Looks like this new test application took me about 11% longer to crunch than the standard version.
Sounds strange. Neither the copiler options nor the "science code" that is used for the current Workunits has changed. Is this measured or estimated time you are referring to? CPU time or real time? Anything else changed on this machine?
Looks like this new test application took me about 11% longer to crunch than the standard version.
Sounds strange. Neither the copiler options nor the "science code" that is used for the current Workunits has changed. Is this measured or estimated time you are referring to? CPU time or real time? Anything else changed on this machine?
Did anyone else see this?
BM
while the code may not have changed, it comes with a pdb. i assume it is debug code which would expalin the longer crunch time (though i have not checked if the 4.79 was debug or release code). cannot comment on the actual time it takes but the estimated time went up a bit.
while the code may not have changed, it comes with a pdb. i assume it is debug code which would expalin the longer crunch time (though i have not checked if the 4.79 was debug or release code). cannot comment on the actual time it takes but the estimated time went up a bit.
The "official" App downloads a pdb, too. It contains information for boincs Stackwalker, but no code that is executed. There have been some additions to the science code, so the code is not precisely the same, but these additions are not used or triggered by the current Workunits.
I just installed the beta test version (just after finishing a WU). I suspended the task - and got a new WU (of course) ;-)
I 'stopped' the project ('no new work') and then suspended the second WU and the stopped the client.
After starting version 0.03 I got the following messages for *BOTH* WUs:
2005-06-21 09:14:24 [Einstein@Home] WU refers to nonexistent app_version: einstein 479
2005-06-21 09:14:24 [Einstein@Home] Can't link workunit in state file
--> all your WUs with a different version are cancelled!
Pitty. But "stopping" the project is a good idea if you are running a newer client - try to get "no new work" for Einstein@Home, finish and report the Results you already got, then install the test App and resume the project - this should make you switch to a new App without losing a single Result.
RE: I just tried
)
Big deal...they're only 6 hours on my PC. Unless you're running a slow PC it shouldn't be a problem to lose 2 WU's.
RE: RE: Can we edit the
)
I just installed the beta test version (just after finishing a WU). I suspended the task - and got a new WU (of course) ;-)
I 'stopped' the project ('no new work') and then suspended the second WU and the stopped the client.
After starting version 0.03 I got the following messages for *BOTH* WUs:
2005-06-21 09:14:24 [Einstein@Home] WU refers to nonexistent app_version: einstein 479
2005-06-21 09:14:24 [Einstein@Home] Can't link workunit in state file
--> all your WUs with a different version are cancelled!
Udo
Looks like this new test
)
Looks like this new test application took me about 11% longer to crunch than the standard version.
RE: Looks like this new
)
Well am using an Intel P4 2GHz only, but the prediction is nearly the same as the last results (11:50h with v0.03 against approx. 12:00h with v4.79)
Udo
RE: RE: RE: Can we edit
)
...just another info...
the cancelled WUs are still active in the database (but no longer available on my computer)...
so they will time out in 7 days!
Is there any possibility to mark these WUs as no longer active?
Udo
RE: Looks like this new
)
Sounds strange. Neither the copiler options nor the "science code" that is used for the current Workunits has changed. Is this measured or estimated time you are referring to? CPU time or real time? Anything else changed on this machine?
Did anyone else see this?
BM
BM
RE: RE: Looks like this
)
while the code may not have changed, it comes with a pdb. i assume it is debug code which would expalin the longer crunch time (though i have not checked if the 4.79 was debug or release code). cannot comment on the actual time it takes but the estimated time went up a bit.
Florian
www.domplatz1.de
RE: while the code may not
)
The "official" App downloads a pdb, too. It contains information for boincs Stackwalker, but no code that is executed. There have been some additions to the science code, so the code is not precisely the same, but these additions are not used or triggered by the current Workunits.
BM
BM
I'm up and running without
)
I'm up and running without any problems and my ATI graphics are working again. Est completion time has not changed for me.
Gregg
RE: I just installed the
)
Pitty. But "stopping" the project is a good idea if you are running a newer client - try to get "no new work" for Einstein@Home, finish and report the Results you already got, then install the test App and resume the project - this should make you switch to a new App without losing a single Result.
BM
BM