That's a (desired) effect of the app_info.xml. Tasks that are interrupted and crunched halfway with an older App will keep the old number, only Tasks that have been ran completely with the new App will show up with the new version number.
Thanks Bernd. I should have read the original post on this thread a little more carefully. I guess I was too used to the "old way of doing things".
Akos, can you dig out the checksums from client_state.xml and check your data files? There's probably a simple too for Windows that does this (I usually use md5sum from Cygwin).
Probably I can't check it before tueasday, but i keep it on my mind.
So, the MD5 checksums are good, but I didn't find a h1 file in the project directory. Probably it was deleted automatically.
When I had downloaded App 4.28 and restarted BOINC it downloaded a new WU but still used the old app. 4.24. I have now manually removed 4.24 and waiting fore a now wu. to be downloaded, hopefully it will work now.
I have completed 11 results with the new app. The first four were partly crunched by the official app and then finished with the beta. One of the results has been granted credit while the others are waiting on their wingmen to complete the WU. Crunch time is nearly identical to the official app, with a possible decrease in time needed.
The host is Intel Core architecture, dual booted with Linux. I am currently testing the Linux beta app, and with 4 WU's at 70% complete, there is a noticeable loss in speed for the new Linux app. Once the WU's are complete I'll post the results in the Linux beta test thread.
There are 10^11 stars in the galaxy. That used to be a huge number. But it's only a hundred billion. It's less than the national deficit! We used to call them astronomical numbers. Now we should call them economical numbers. - Richard Feynman
I have swiched a total of 9 hosts to the beta app, 5 of which are running the Windows version. Three of the Windows boxes are Athlon XPs, one is a P4 (Northwood) and one is a PIII (Tualatin Celeron).
The Athlon XPs have all submitted results - 7 in total, without problems, 6 of which have validated. The crunching time seems to have increased very slightly - about 1% so hard to tell from the normal variation.
The P4 is a laptop and has only completed one entirely with the new app. The result has validated and it appears to be about 10% faster but machine does show time variations due to heat related CPU throttling. I'll get a better idea when the next result completes.
The PIII has not yet completed a result. The box has locked up and refuses to post so I've switched the HDD to an identical box (identical mobo (ASUS TUSI-M), CPU, RAM), so it has now restarted the crunching after losing about a day before I noticed it. I noticed a couple of slightly swollen caps on the faulty mobo so I should be able to replace those OK.
Three of the 4 Linux boxes are PIIIs and one is an Athlon XP. This one shows about a 20% time penalty in line with what others are reporting. The PIIIs also show a time penalty but it's much smaller - about 5%. Because of the speed of the PIIIs very few results have been done but those that have are all looking good. I'll report further in the Linux thread when more results are done. I hope the reason for the slowness of the AMD/Linux combo can be identified quickly.
RE: That's a (desired)
)
Thanks Bernd. I should have read the original post on this thread a little more carefully. I guess I was too used to the "old way of doing things".
@ Gary - I have now taken "a closer look".
RE: RE: Akos, can you dig
)
So, the MD5 checksums are good, but I didn't find a h1 file in the project directory. Probably it was deleted automatically.
When I had downloaded App
)
When I had downloaded App 4.28 and restarted BOINC it downloaded a new WU but still used the old app. 4.24. I have now manually removed 4.24 and waiting fore a now wu. to be downloaded, hopefully it will work now.
So, first WU completly
)
So, first WU completly crunched with 4.28 and validated:
http://einsteinathome.org/task/85769960
Seems all to be okay up to now. Okay, the app could be a little more faster... :)
Crunched with release and
)
Crunched with release and beta apps and validated.
Kathryn :o)
Einstein@Home Moderator
Thank you! Any noticeable
)
Thank you!
Any noticeable difference in speed from the official App?
BM
BM
Sorry, can´t compare WUs. I
)
Sorry, can´t compare WUs. I started with a new file as I switched to 4.28. But in my viewing I can say, the app runs stable.
Transition went smoothly on
)
Transition went smoothly on my XP/Intel box. Lets see how the app does in action.
I have completed 11 results
)
I have completed 11 results with the new app. The first four were partly crunched by the official app and then finished with the beta. One of the results has been granted credit while the others are waiting on their wingmen to complete the WU. Crunch time is nearly identical to the official app, with a possible decrease in time needed.
The host is Intel Core architecture, dual booted with Linux. I am currently testing the Linux beta app, and with 4 WU's at 70% complete, there is a noticeable loss in speed for the new Linux app. Once the WU's are complete I'll post the results in the Linux beta test thread.
There are 10^11 stars in the galaxy. That used to be a huge number. But it's only a hundred billion. It's less than the national deficit! We used to call them astronomical numbers. Now we should call them economical numbers. - Richard Feynman
I have swiched a total of 9
)
I have swiched a total of 9 hosts to the beta app, 5 of which are running the Windows version. Three of the Windows boxes are Athlon XPs, one is a P4 (Northwood) and one is a PIII (Tualatin Celeron).
The Athlon XPs have all submitted results - 7 in total, without problems, 6 of which have validated. The crunching time seems to have increased very slightly - about 1% so hard to tell from the normal variation.
The P4 is a laptop and has only completed one entirely with the new app. The result has validated and it appears to be about 10% faster but machine does show time variations due to heat related CPU throttling. I'll get a better idea when the next result completes.
The PIII has not yet completed a result. The box has locked up and refuses to post so I've switched the HDD to an identical box (identical mobo (ASUS TUSI-M), CPU, RAM), so it has now restarted the crunching after losing about a day before I noticed it. I noticed a couple of slightly swollen caps on the faulty mobo so I should be able to replace those OK.
Three of the 4 Linux boxes are PIIIs and one is an Athlon XP. This one shows about a 20% time penalty in line with what others are reporting. The PIIIs also show a time penalty but it's much smaller - about 5%. Because of the speed of the PIIIs very few results have been done but those that have are all looking good. I'll report further in the Linux thread when more results are done. I hope the reason for the slowness of the AMD/Linux combo can be identified quickly.
Cheers,
Gary.