I usually just let BOINC do what ever it wants and look in on it from time to time (looking for Error Messages). If it will help, I will continue to closely monitor Einstein.
Is the bad data from the project's side while building the results, or while creating the datapack, or is it being trashed while downloading, or is it still too early to tell?
Good questions. Too early to tell, I think. As it looks now, it could be:
a) corruption at Einstein.
b) memory corruption on the host.
c) disk corruption on the host.
But I am guessing the corruption takes place at Einstein, as it affects some datapacks and not others. So if you can fool Einstein's resend work unit scheme and get a whole new one, it may well take care of the problem for the length of that work unit.
I usually just let BOINC do
)
I usually just let BOINC do what ever it wants and look in on it from time to time (looking for Error Messages). If it will help, I will continue to closely monitor Einstein.
RE: Is the bad data from
)
Good questions. Too early to tell, I think. As it looks now, it could be:
a) corruption at Einstein.
b) memory corruption on the host.
c) disk corruption on the host.
But I am guessing the corruption takes place at Einstein, as it affects some datapacks and not others. So if you can fool Einstein's resend work unit scheme and get a whole new one, it may well take care of the problem for the length of that work unit.