Bernd told me some things.
He would like that we use the 4.10 version number for patched files, so you should rename your files and built an app_info.xml file in the future. The next patches will search einstein_S5R1_4.10_windows_intelx86.exe in their directory.
The other thing is that the validator doesn't drop out those results that have only a small difference in the values, like as S4 validation. So, there is possible to built ( a bit ) faster codes!
I thought we should report the version as 4.10 for the validator to be less agressive in action?
Bernd told me some things.
He would like that we use the 4.10 version number for patched files, so you should rename your files and built an app_info.xml file in the future. The next patches will search einstein_S5R1_4.10_windows_intelx86.exe in their directory.
I thought we should report the version as 4.10 for the validator to be less agressive in action?
Just checked on my HT machine that ive been running two units from seperate projects and is looking to be another hour faster,. Its on S5T0709. One unit einstien other seti. Standard app took 18+hours and is looking if lucky to take little over 14hours.
I've set to run out cache as per Ulrich advice.
4.10 works for me, because my cache is empty.
If you still have 4.02 wu's in cache they will be dropped!
Apart from Uli's issue over the empty cache, the effects the difference is likely to have (and someone who knows better may correct this) is that putting version 410 in the app_info file will accept work units for stock application level 4.02 up to 4.10, whenever these might appear, and will report all WUs back to the server as being completed by a 4.10 application. This may be what Bernd actually wants here, I don't know. Future versions of the stock application may not be compatible with the patched 4.02/4.10 application we have now.
To do this change, it would be necessary to set "no new work/task", run the cache down, report all completed work, stop BOINC, then change the number to 410, start BOINC and accept new work again. Leaving the version at 402 will prevent work being delivered if the project moves above 4.02 until the app_info file is adjusted, which is safe. There are risks either way!
Personally, I liked Akos' previous scheme without the app_info file, where if a new stock application appeared it automatically replaced the patched application, but you were at least running compatible code until Akos revealed whether the patches could be re-applied or had to be rebuilt. Mike
So many different Versions.
Bernd communicates us please like you app_info.xml introduces itself.
One Version for all please!
Do not let us move in the dark.
RE: Bernd told me some
)
I thought we should report the version as 4.10 for the validator to be less agressive in action?
Aloha, Uli
RE: RE: Bernd told me
)
hm yes if it works with 410 then i will try that.
I just now see the thread is called
Optomized S5 SSE3 ;)
4.10 works for me, because my
)
4.10 works for me, because my cache is empty.
If you still have 4.02 wu's in cache they will be dropped!
Aloha, Uli
Just checked on my HT machine
)
Just checked on my HT machine that ive been running two units from seperate projects and is looking to be another hour faster,. Its on S5T0709. One unit einstien other seti. Standard app took 18+hours and is looking if lucky to take little over 14hours.
I've set to run out cache as per Ulrich advice.
RE: 4.10 works for me,
)
With MRAO´s App_info.xml my 4.02er WU´s worked. Looks fine.
But i switched back to 0411 till someone reports his 0412er results.
Athlon
Stay tuned and keep crunching
It should work with 410, i
)
It should work with 410, i think, if you edit your client_state.xml file. In that there might be units assigned to 402.
So you would have to change the entries
einstein_S5R1
402
einstein_S5R1_4.02_windows_intelx86.exe
einstein_S5R1_4.02_windows_intelx86.pdb
einstein_S5R1_4.02_windows_intelx86.pdb
and all
h1_0544.0_S5R1__220_S5R1a
einstein_S5R1
402
[...]
Please correct me, if I'm wrong.
cu,
Michael
RE: 4.10 works for me,
)
Apart from Uli's issue over the empty cache, the effects the difference is likely to have (and someone who knows better may correct this) is that putting version 410 in the app_info file will accept work units for stock application level 4.02 up to 4.10, whenever these might appear, and will report all WUs back to the server as being completed by a 4.10 application. This may be what Bernd actually wants here, I don't know. Future versions of the stock application may not be compatible with the patched 4.02/4.10 application we have now.
To do this change, it would be necessary to set "no new work/task", run the cache down, report all completed work, stop BOINC, then change the number to 410, start BOINC and accept new work again. Leaving the version at 402 will prevent work being delivered if the project moves above 4.02 until the app_info file is adjusted, which is safe. There are risks either way!
Personally, I liked Akos' previous scheme without the app_info file, where if a new stock application appeared it automatically replaced the patched application, but you were at least running compatible code until Akos revealed whether the patches could be re-applied or had to be rebuilt. Mike
So many different
)
So many different Versions.
Bernd communicates us please like you app_info.xml introduces itself.
One Version for all please!
Do not let us move in the dark.
Athlon
Stay tuned and keep crunching
Now I finished my testing WU
)
Now I finished my testing WU by S5T0712, time is on about 76% of official app, and output is identical => results should be valided :)
Finished next WU. Last part
)
Finished next WU. Last part with 0712 http://einsteinathome.org/task/34792692 is valided.