right, that's no problem.
But which is with the other users how get the same wus like i.
I reported 410 and the other 402. That's not okay for the validating, i think.
Now my WU cash is empty just waiting for someone who knows how the app_info.xml should look like to post it hear or perhaps aksof could put it in the thread where he tells us which is the latest stable version, so many alternatives here so I don´t know which one is correct and tell me what patch I should use with that. Einstein is put at don´t get new work until this little problen is solved.
sounds to me like if you have a large cache and can't feasibly wait for it to clear, your kind of out of luck with the newest patches.
I'd say figure out which of the patches was the fastest that was available BEFORE all this 402 410 switching came up.......S5S0007 or S5T0709........maybe S5T0711, not sure, I'm not using it yet........I'm waiting for things to cool down and sticking with S5S0007 without messing with all the 402-410 business yet.
Looks like the app patches after maybe S5T0711 require the more forgiving validation achievable by reporting the app as 4.10, hence the need to change the files if running these new patches......
So, either stick with an app patch that passed validation reporting as 402, or figure out how to modify all those units to be reported as 4.10 and use the newest app......but I don't have a clue how to do that.
just my thoughts..........trying to keep it all straight myself.
I'd say figure out which of the patches was the fastest that was available BEFORE all this 402 410 switching came up.......S5S0007 or S5T0709........maybe S5T0711 I'm not using it yet........I'm waiting for things to cool down and sticking with S5S0007 without messing with all the 402-410 business yet.
you can use the S5T0711 without changing anything else, its fast and stable. 0712 is the first where you have to change other things, so i recommend S5T0711 for people who are confused now :)
Editing the client_state.xml file killed all my WUs, so watch out.
cu,
Michael
THX!
so the only way to use the new opt. clients is to drop my 120 WUs and download new 410 wus! WOW, thats a so good idea....
You can take it in stages to burn up the existing 120 WUs. Set "no new work/tasks" on einstein so you don't get any more for now, and exit BOINC. Rename the 4.02 S5R1 application as the 4.10 application and apply the app_info.xml file here with [version_num]402 in it to the einstein project directory, and restart BOINC to run the existing WUs out as 4.02 application version units. You can use Akos patches for the 410 application at this stage if you want. When all the WU's are crunched and reported, exit from BOINC again and change the app_info.xml file so it reads "[version_num]410" instead of 402, start BOINC and allow new work/tasks again. Now all units will download, crunch and report fully as 410. Safer than fiddling with the client_stat.xml file IMHO, you can lose all your projects that way as well as all your WUs. Mike
I'd say figure out which of the patches was the fastest that was available BEFORE all this 402 410 switching came up.......S5S0007 or S5T0709........maybe S5T0711 I'm not using it yet........I'm waiting for things to cool down and sticking with S5S0007 without messing with all the 402-410 business yet.
you can use the S5T0711 without changing anything else, its fast and stable. 0712 is the first where you have to change other things, so i recommend S5T0711 for people who are confused now :)
I have a 0712 result reported as 4.02 and it is validated.
right, that's no problem. But
)
right, that's no problem.
But which is with the other users how get the same wus like i.
I reported 410 and the other 402. That's not okay for the validating, i think.
Now my WU cash is empty just
)
Now my WU cash is empty just waiting for someone who knows how the app_info.xml should look like to post it hear or perhaps aksof could put it in the thread where he tells us which is the latest stable version, so many alternatives here so I don´t know which one is correct and tell me what patch I should use with that. Einstein is put at don´t get new work until this little problen is solved.
RE: Editing the
)
THX!
so the only way to use the new opt. clients is to drop my 120 WUs and download new 410 wus! WOW, thats a so good idea....
geez, this is getting
)
geez, this is getting confusing!!!!!!!!
sounds to me like if you have a large cache and can't feasibly wait for it to clear, your kind of out of luck with the newest patches.
I'd say figure out which of the patches was the fastest that was available BEFORE all this 402 410 switching came up.......S5S0007 or S5T0709........maybe S5T0711, not sure, I'm not using it yet........I'm waiting for things to cool down and sticking with S5S0007 without messing with all the 402-410 business yet.
Looks like the app patches after maybe S5T0711 require the more forgiving validation achievable by reporting the app as 4.10, hence the need to change the files if running these new patches......
So, either stick with an app patch that passed validation reporting as 402, or figure out how to modify all those units to be reported as 4.10 and use the newest app......but I don't have a clue how to do that.
just my thoughts..........trying to keep it all straight myself.
RE: geez, this is getting
)
you can use the S5T0711 without changing anything else, its fast and stable. 0712 is the first where you have to change other things, so i recommend S5T0711 for people who are confused now :)
Thanks!!!! will
)
Thanks!!!! will do......
now, where in the heck was that 0711 link!!!!!!!! aaaaaaaahhhhhh.............>
RE: RE: Editing the
)
You can take it in stages to burn up the existing 120 WUs. Set "no new work/tasks" on einstein so you don't get any more for now, and exit BOINC. Rename the 4.02 S5R1 application as the 4.10 application and apply the app_info.xml file here with [version_num]402 in it to the einstein project directory, and restart BOINC to run the existing WUs out as 4.02 application version units. You can use Akos patches for the 410 application at this stage if you want. When all the WU's are crunched and reported, exit from BOINC again and change the app_info.xml file so it reads "[version_num]410" instead of 402, start BOINC and allow new work/tasks again. Now all units will download, crunch and report fully as 410. Safer than fiddling with the client_stat.xml file IMHO, you can lose all your projects that way as well as all your WUs. Mike
RE: RE: Editing the
)
You can crunch them with S5T0711.dat without any app_info.xml file. As Akos wrote:
"In the future...".
cu,
Michael
RE: RE: geez, this is
)
I have a 0712 result reported as 4.02 and it is validated.
RE: I have a 0712 result
)
right, until S5T0713 the validator need the app_info and the results must reporting as 410.
@MRAO: its funny, because until S5T0713 you'll have the same problems like me ;)