The current beta App definitely has a problem with proper suspending. If you want to mix E@H with other projects, run the official App or wait for the next Beta version. Should be up soon.
No, I doon't see any sign of your computer being marked invalid. However I see that there are some results have been sent to you with deadline 9 July ("no reply") and two have been sent recently being "in progress". What exactly do the messages say?
2. The problem is that some things have changed between the 4.19 and the 4.43 client. The BOINC Manager found the 4.19 client running and tried to connect to it, but failed because of changes in the protocol that have been made.
3. The solution:
- Stop any clients and Managers
- If you give something on the Result that has already been started, move all the files and folders from the BOINC folder in your home directory into "/Library/Application Support/BOINC Data", overwriting what may already be there. Delete only the single file named "boinc" (the old client).
- Remove the BOINC folder (and all its contents if you skipped the previous step) from your home directory.
- Start the BOINC Manager again
4. The only thing that was wrong in some sense was that you apparently had the old client running when installing the new one. However I suspect that it's rather BOINCs fault for not telling you. I wrote to the BOINC developers about that, maybe the next installer will handle this case better.
A "Work unit" (WU) is just a "slice" of work that a project finds suitable to be crunched by a single machine. The "size" of this, i.e. the number of (usually floating-point) operations it requires, and thus the time it takes on a specific machine, may differ a lot between two projects, and even between two Workunits of the same project.
WUs of SETI and Predictor I found to be rather short (1-2h). Ours have been calculated to be roughly done one in a day on a modern machine that uses 50% of its time for processing Einstein@Home. CPDN has Workunits that take hundrets of hours, so actually months, to process.
Ok, I'll have another look at the "suspend" problem. I already have a clue what's going on, but this needs a bit more investigation.
Curently we received a bit more than a hundred results from the 0.05 Beta, quite some of them with a 4.44 client, no client errors and none being invalid.
Thanks, C! Am I understanding that you upgraded to Einstein .05 while you still had Einstein .02 WUs crunching and they didn't get fracked?!
This is correct. If you leave the previous .02 executable in place AND use our new app_info.xml file, the jobs that were 'married' to the .02 app will run with that app. Look in app_info.xml and you'll see why: it's because the latest app_info.xml file lists BOTH the .02 and the .05 app.
I think we've sorted out the pausing problem. This is a bug in the BOINC API library, which we have been able to fix. I expect that Bernd will have a new executable available fairly soon.
Bernd has just finished building a new test app for OS X which fixes the suspend/resume bug. Please go to the usual location to try it out, and report your experiences to this thread.
The current beta App
)
The current beta App definitely has a problem with proper suspending. If you want to mix E@H with other projects, run the official App or wait for the next Beta version. Should be up soon.
BM
BM
No, I doon't see any sign of
)
No, I doon't see any sign of your computer being marked invalid. However I see that there are some results have been sent to you with deadline 9 July ("no reply") and two have been sent recently being "in progress". What exactly do the messages say?
BM
BM
I've just posted a
)
I've just posted a [url=http://einstein.phys.uwm.edu/app_test.php]new test version (0.05) of the Einstein@Home app for Mac OS X. This should fix the suspend/resume problem.
Please read the installation instructions carefully.
Please post success/failure reports to this thread.
Cheers,
Bruce
Good to know, thanks! BM
)
Good to know, thanks!
BM
BM
1. You are doing nothing
)
1. You are doing nothing wrong.
2. The problem is that some things have changed between the 4.19 and the 4.43 client. The BOINC Manager found the 4.19 client running and tried to connect to it, but failed because of changes in the protocol that have been made.
3. The solution:
- Stop any clients and Managers
- If you give something on the Result that has already been started, move all the files and folders from the BOINC folder in your home directory into "/Library/Application Support/BOINC Data", overwriting what may already be there. Delete only the single file named "boinc" (the old client).
- Remove the BOINC folder (and all its contents if you skipped the previous step) from your home directory.
- Start the BOINC Manager again
4. The only thing that was wrong in some sense was that you apparently had the old client running when installing the new one. However I suspect that it's rather BOINCs fault for not telling you. I wrote to the BOINC developers about that, maybe the next installer will handle this case better.
BM
BM
A "Work unit" (WU) is just a
)
A "Work unit" (WU) is just a "slice" of work that a project finds suitable to be crunched by a single machine. The "size" of this, i.e. the number of (usually floating-point) operations it requires, and thus the time it takes on a specific machine, may differ a lot between two projects, and even between two Workunits of the same project.
WUs of SETI and Predictor I found to be rather short (1-2h). Ours have been calculated to be roughly done one in a day on a modern machine that uses 50% of its time for processing Einstein@Home. CPDN has Workunits that take hundrets of hours, so actually months, to process.
BM
BM
Ok, I'll have another look at
)
Ok, I'll have another look at the "suspend" problem. I already have a clue what's going on, but this needs a bit more investigation.
Curently we received a bit more than a hundred results from the 0.05 Beta, quite some of them with a 4.44 client, no client errors and none being invalid.
BM
BM
RE: Thanks, C! Am I
)
This is correct. If you leave the previous .02 executable in place AND use our new app_info.xml file, the jobs that were 'married' to the .02 app will run with that app. Look in app_info.xml and you'll see why: it's because the latest app_info.xml file lists BOTH the .02 and the .05 app.
Bruce
I think we've sorted out the
)
I think we've sorted out the pausing problem. This is a bug in the BOINC API library, which we have been able to fix. I expect that Bernd will have a new executable available fairly soon.
Bruce
Bernd has just finished
)
Bernd has just finished building a new test app for OS X which fixes the suspend/resume bug. Please go to the usual location to try it out, and report your experiences to this thread.