I can rotate the sphere with the mouse, but I am unable to zoom (i.e. change the distance between view point and center of the sphere).
Press the Ctrl key, press the mouse button (without releasing the key) and move the mouse up and down while keeping both pressed. On a trackpad I use the left hand to press the key and the button and a finger of the right hand on the pad. Well, this feature was originally designed for a two- or three-button mouse.
I tried this, using the trackpad, but it does not work with Einstein 0.02
Really weird, works perfeclty for me, with 0.02 on 10.3.9 and 10.4.1. One last thought - are you using an uncommon keymap? Or maybe a hotkey tool? Anyone else seen this or has an idea?
Quote:
Let us not get too excited about this detail{/quote]
Well, this is a real puzzle. it might not be important for you, but it may not be limited to your machine and may point to a deeper problem.
Another, even less important detail: after update (and change) of my "Credit", the graphics and screen saver still show the old "Credit" (at least temporarily).
This takes two server contacts from the client side to update. Depending on your preference settings this may need quite a bit patience, but should finally correct itself.
I actually saw the partially completed unit resume, with zero CPU time.
Does the setting of "remove from memory when suspended" make a difference to that?
BM
Doesn't seem to. I've tried it both ways. I think there is a problem with the BOINC Manager.
I suspect it is a problem in the BOINC App API library not in the BOINC Manager. Could you please see if the client_state.xml file contains the correct CPU time?
I tried to reproduce your problem. Running einstein only I couldn't see anything unusual, so I attached to SETI as well. I found that neither einstein nor SETI took any suspension, both were (more or less happily) sharing the CPU time, regardless of what the client tells them to do, either because of the normal scheduling or because I manually told him to suspend a project or result. Very strange. There's definitely some bug left in the boinc (App) lib. Asymmetries (like you see with Predictor and Einstein) are probably caused by the different library version the Apps are using.
Do I need to delete something before I start einstein up again?
No. You may want to delete the old 4.78 App if you are short on diskspace, but it's not necessary.
The H1... file btw. is the file that actually contains the real data from the detector, all other files ther are just support files.
We've found a small problem, however it is minor enough that users should continue to use this Mac test app. The problem is that sometimes, when reporting an event candidate near the North celestial pole, this code reports delta slightly LARGER than pi/2 and alpha increased by pi over the value it would have if delta were slightly less than pi/2.
When compared with the result from one of the previous (Win/Linux/Mac) apps the validator does not recognize that these two points are only a tiny distance apart on the sphere, and marks one of the results as incorrect. The correct solution is for us to fix the validator to recognize that this points are close to within numerical precision, which we'll do in the coming days.
Meanwhile, be warned that approximately 4% of the results produced by this new app will be incorrectly marked as invalid! The results will reported as successful, will be uploaded to the server, and will then be marked 'invalid' by the validator and denied credit.
For the project the new app is still a big net improvement because the Altivec code it contains is about twice as fast as the code in the previous app. So our advice is that users should continue to use this new test app in spite of this issue.
Now I did read something about 4% being no good. But I am at over 71% being crap and not even being turned down. They are just crap from the start. Before the upload. My Boinc is saying they are crap.
The 4% are Results that finish successful, but are marked as invalid (thus granted no credit) because of a problem with the validation. This has nothing to do with Results that crash during computation with a "client error".
In the two Results with client errors I've seen from your machines the core client version is reported as 4.44. Where did you get that from? The one that's on our download page and we tested the App with is still 4.43.
I just found a problem in the boinc library that I think is responsible for the "not properly suspending" issue. If I'm right, this at least is not a problem of the client, but of the App.
RE: I can rotate the sphere
)
Press the Ctrl key, press the mouse button (without releasing the key) and move the mouse up and down while keeping both pressed. On a trackpad I use the left hand to press the key and the button and a finger of the right hand on the pad. Well, this feature was originally designed for a two- or three-button mouse.
BM
BM
RE: I tried this, using the
)
Really weird, works perfeclty for me, with 0.02 on 10.3.9 and 10.4.1. One last thought - are you using an uncommon keymap? Or maybe a hotkey tool? Anyone else seen this or has an idea?
BM
RE: I actually saw the
)
Does the setting of "remove from memory when suspended" make a difference to that?
BM
BM
RE: Another, even less
)
This takes two server contacts from the client side to update. Depending on your preference settings this may need quite a bit patience, but should finally correct itself.
BM
BM
RE: RE: RE: I actually
)
I suspect it is a problem in the BOINC App API library not in the BOINC Manager. Could you please see if the client_state.xml file contains the correct CPU time?
Shaktai, I tried to
)
Shaktai,
I tried to reproduce your problem. Running einstein only I couldn't see anything unusual, so I attached to SETI as well. I found that neither einstein nor SETI took any suspension, both were (more or less happily) sharing the CPU time, regardless of what the client tells them to do, either because of the normal scheduling or because I manually told him to suspend a project or result. Very strange. There's definitely some bug left in the boinc (App) lib. Asymmetries (like you see with Predictor and Einstein) are probably caused by the different library version the Apps are using.
BM
BM
RE: Is this
)
Yes.
No. You may want to delete the old 4.78 App if you are short on diskspace, but it's not necessary.
The H1... file btw. is the file that actually contains the real data from the detector, all other files ther are just support files.
BM
BM
We've found a small problem,
)
We've found a small problem, however it is minor enough that users should continue to use this Mac test app. The problem is that sometimes, when reporting an event candidate near the North celestial pole, this code reports delta slightly LARGER than pi/2 and alpha increased by pi over the value it would have if delta were slightly less than pi/2.
When compared with the result from one of the previous (Win/Linux/Mac) apps the validator does not recognize that these two points are only a tiny distance apart on the sphere, and marks one of the results as incorrect. The correct solution is for us to fix the validator to recognize that this points are close to within numerical precision, which we'll do in the coming days.
Meanwhile, be warned that approximately 4% of the results produced by this new app will be incorrectly marked as invalid! The results will reported as successful, will be uploaded to the server, and will then be marked 'invalid' by the validator and denied credit.
For the project the new app is still a big net improvement because the Altivec code it contains is about twice as fast as the code in the previous app. So our advice is that users should continue to use this new test app in spite of this issue.
Bruce
RE: Now I did read
)
The 4% are Results that finish successful, but are marked as invalid (thus granted no credit) because of a problem with the validation. This has nothing to do with Results that crash during computation with a "client error".
In the two Results with client errors I've seen from your machines the core client version is reported as 4.44. Where did you get that from? The one that's on our download page and we tested the App with is still 4.43.
BM
BM
I just found a problem in the
)
I just found a problem in the boinc library that I think is responsible for the "not properly suspending" issue. If I'm right, this at least is not a problem of the client, but of the App.
BM
BM