I started using the beta app last thursday. As it seems everything is working fine on my machine.
Crunching times are down from 33,000 - 40,000 seconds to 23,000 seconds - very nice speed-up! Quite a lot of results have been validated by now some more wating for other machines to catch up.
Absolutely no problems to report from my test of this very fast application.
I started using the beta app last thursday. As it seems everything is working fine on my machine.
Crunching times are down from 33,000 - 40,000 seconds to 23,000 seconds - very nice speed-up! Quite a lot of results have been validated by now some more wating for other machines to catch up.
Absolutely no problems to report from my test of this very fast application.
Slightly off topic, are there any plans to release a Windows beta in the near term future, or is Windows pretty much good to go with version 4.15 for awhile?
Slightly off topic, are there any plans to release a Windows beta in the near term future, or is Windows pretty much good to go with version 4.15 for awhile?
From what I've read, Bernd is working on trying to take care of the remaining bugs in the Linux app, look into the remaining DLL loading issues in Windows, and the porting the SSE optimization that was done in the Mac app into the other apps. I have no idea on what order they'll be done in, although I can say that I'd like to see the SSE optimization sometime soon. This will help out with deadline pressure and the grumbling complaints here and there about said deadline pressure (the, "I don't understand why SETI gives months to complete far less work than you do," type of complaining).
Hmmm... When "Validate Error" happens over at SETI, it has traditionally meant (at least lately) that the uploaded result file was not where it was expected to be at when the validator checked for it, thus it is a "Validate Error". In the cases at SETI, they have a script that they run every so often that goes out and "fixes" these issues. I'm not sure what the script does exactly. I would guess that they wouldn't issue credit if the user never uploaded a result, but I don't know for sure. In any case, as for this error on SETI, it is not considered to be an application problem but a BOINC backend problem. Reporting a result very quickly after it was uploaded is an irritant. Make sure you have a Connect Interval as something higher than either immediate or only a few seconds.
@Bernd - unless you know that your validate errors are different than SETI's, you might want to contact Eric Korpela at SETI for his script and/or advice on what they are doing...
@Bernd - unless you know that your validate errors are different than SETI's, you might want to contact Eric Korpela at SETI for his script and/or advice on what they are doing...
A "validate error" means that the invalidity of a result can be determined from the result itself without comparison to other results of the same WU. This can be a technical problem such a as a missing result file, but also happens if the file can't be unzipped or (in Einstein@home case) contains unreasonable values (e.g. NaNs). I'll see when I'll find the time to look into this particular case.
......
Hmmm... In any case, as for this error on SETI, it is not considered to be an application problem but a BOINC backend problem. Reporting a result very quickly after it was uploaded is an irritant. Make sure you have a Connect Interval as something higher than either immediate or only a few seconds.
I have my connect interval set to 0,001 about 1,5 min It should be ok.
This is really an interesting one. It's not your fault, and not that of the BOINC backend. It requires a bit more digging through the code than I have time for right now, but it looks like some problem that was fixed a while ago in the Windows and Linux Apps. I should make a new MacOS Intel App that incorporates these fixes, but I doubt I'll come to it the next two weeks.
@Bernd - unless you know that your validate errors are different than SETI's, you might want to contact Eric Korpela at SETI for his script and/or advice on what they are doing...
A "validate error" means that the invalidity of a result can be determined from the result itself without comparison to other results of the same WU. This can be a technical problem such a as a missing result file, but also happens if the file can't be unzipped or (in Einstein@home case) contains unreasonable values (e.g. NaNs). I'll see when I'll find the time to look into this particular case.
BM
Chalk this up to me being really tired when I said what I said, but SETI's issues are not a BOINC backend problem either. It is REALLY an issue with the server infrastructure at SETI. They have some network and/or database and/or NFS issues that rear their ugly heads from time to time.
RE: Thanks for the link.
)
I don't know for sure. I have not upgraded to leopard yet.
I started using the beta app
)
I started using the beta app last thursday. As it seems everything is working fine on my machine.
Crunching times are down from 33,000 - 40,000 seconds to 23,000 seconds - very nice speed-up! Quite a lot of results have been validated by now some more wating for other machines to catch up.
Absolutely no problems to report from my test of this very fast application.
Einstein@Home Project
RE: I started using the
)
Slightly off topic, are there any plans to release a Windows beta in the near term future, or is Windows pretty much good to go with version 4.15 for awhile?
Thanks!
RE: Slightly off topic,
)
From what I've read, Bernd is working on trying to take care of the remaining bugs in the Linux app, look into the remaining DLL loading issues in Windows, and the porting the SSE optimization that was done in the Mac app into the other apps. I have no idea on what order they'll be done in, although I can say that I'd like to see the SSE optimization sometime soon. This will help out with deadline pressure and the grumbling complaints here and there about said deadline pressure (the, "I don't understand why SETI gives months to complete far less work than you do," type of complaining).
Got my first error with this
)
Got my first error with this app.
Anders n
RE: Got my first error with
)
Hmmm... When "Validate Error" happens over at SETI, it has traditionally meant (at least lately) that the uploaded result file was not where it was expected to be at when the validator checked for it, thus it is a "Validate Error". In the cases at SETI, they have a script that they run every so often that goes out and "fixes" these issues. I'm not sure what the script does exactly. I would guess that they wouldn't issue credit if the user never uploaded a result, but I don't know for sure. In any case, as for this error on SETI, it is not considered to be an application problem but a BOINC backend problem. Reporting a result very quickly after it was uploaded is an irritant. Make sure you have a Connect Interval as something higher than either immediate or only a few seconds.
@Bernd - unless you know that your validate errors are different than SETI's, you might want to contact Eric Korpela at SETI for his script and/or advice on what they are doing...
RE: @Bernd - unless you
)
A "validate error" means that the invalidity of a result can be determined from the result itself without comparison to other results of the same WU. This can be a technical problem such a as a missing result file, but also happens if the file can't be unzipped or (in Einstein@home case) contains unreasonable values (e.g. NaNs). I'll see when I'll find the time to look into this particular case.
BM
BM
RE: ...... Hmmm... In
)
I have my connect interval set to 0,001 about 1,5 min It should be ok.
Anders n
RE: Got my first error with
)
This is really an interesting one. It's not your fault, and not that of the BOINC backend. It requires a bit more digging through the code than I have time for right now, but it looks like some problem that was fixed a while ago in the Windows and Linux Apps. I should make a new MacOS Intel App that incorporates these fixes, but I doubt I'll come to it the next two weeks.
BM
BM
RE: RE: @Bernd - unless
)
Chalk this up to me being really tired when I said what I said, but SETI's issues are not a BOINC backend problem either. It is REALLY an issue with the server infrastructure at SETI. They have some network and/or database and/or NFS issues that rear their ugly heads from time to time.