MacOS X Intel S5R3 App 4.10 available for Beta Test

peanut
peanut
Joined: 4 May 07
Posts: 162
Credit: 9644812
RAC: 0

RE: Thanks for the link.

Message 74944 in response to message 74943

Quote:


Thanks for the link. Is it the same for Leopard, or is this a Tiger-only issue?

CU
H-B


I don't know for sure. I have not upgraded to leopard yet.

Benjamin Knispel
Benjamin Knispel
Joined: 1 Jun 06
Posts: 148
Credit: 4981579
RAC: 0

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

rbpeake
rbpeake
Joined: 18 Jan 05
Posts: 266
Credit: 967920389
RAC: 1204384

RE: I started using the

Message 74946 in response to message 74945

Quote:

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?

Thanks!

Brian Silvers
Brian Silvers
Joined: 26 Aug 05
Posts: 772
Credit: 282700
RAC: 0

RE: Slightly off topic,

Message 74947 in response to message 74946

Quote:

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).

anders n
anders n
Joined: 29 Aug 05
Posts: 123
Credit: 1656300
RAC: 0

Got my first error with this

Got my first error with this app.

Anders n

Brian Silvers
Brian Silvers
Joined: 26 Aug 05
Posts: 772
Credit: 282700
RAC: 0

RE: Got my first error with

Message 74949 in response to message 74948

Quote:

Got my first error with this app.

Anders n

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 Machenschalk
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4266
Credit: 244924081
RAC: 16749

RE: @Bernd - unless you

Message 74950 in response to message 74949

Quote:
@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

BM

anders n
anders n
Joined: 29 Aug 05
Posts: 123
Credit: 1656300
RAC: 0

RE: ...... Hmmm... In

Message 74951 in response to message 74949

Quote:
......
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.

Anders n

Bernd Machenschalk
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4266
Credit: 244924081
RAC: 16749

RE: Got my first error with

Message 74952 in response to message 74948

Quote:
Got my first error with this app.


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

Brian Silvers
Brian Silvers
Joined: 26 Aug 05
Posts: 772
Credit: 282700
RAC: 0

RE: RE: @Bernd - unless

Message 74953 in response to message 74950

Quote:
Quote:
@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.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.