Posts by m.somers

21) Message boards : : Number crunching : Valid WUs claim 0 credits
Posted 1048 days ago by m.somers
H'mmm, I have no explanation for this yet; usually the client 'claims' a certain amount of credit and this amount together with the result is compared to another run. If they both match, you are granted the credit. So that seems to indicate that if your client somehow asks '0' credit, yet the output is just fine, there is something with the BOINC client code?

Having had a look at the results of this computer in the DB; you do get the credits you claim somehow?


22) Message boards : : Leiden Classical : Bad Glitch in Mac Version
Posted 1144 days ago by m.somers

at the moment I do not have access to Mac Power / Mac Intel hardware to recompile the code without any graphics. I have ported the code already recently to not use graphics, and successfully compiled it for Linux, BSD and Windows, but not for Macs.

So in short only one option left as a fix; abandon the Mac (and BSD due to other maintenance issues) support and introduce the 'anonymous' platform. In this way Mac users and BSD users can compile the code themselves and support LC. This is not so ideal I realize, if not only because of the use of Homogeneous Redundancy of this project.

The alternative is accepting the issue for some Mac users for the time being and hoping that at some point *soon* I am able to access (at least) Mac Intel hardware to compile the code without graphics.


23) Message boards : : Leiden Classical : Computation Error
Posted 1154 days ago by m.somers

have you made sure all graphical libs are available?

24) Message boards : : Number crunching : Problem Downloading Project Executables
Posted 1172 days ago by m.somers
That is strange; I double checked all executables on the server here with off-line backups and the sha1sums all check:

sha1sum classical_5.56_windows_intelx86.exe:

dbe74e6b129e30501269ce15858c42fb91c61c26 classical_5.56_windows_intelx86.exe

You might try and see of your downloaded executable also has the above sha1sum.

if so, I think Avast is giving a false positive because I personally compiled those binaries from sources on a virtual windows XP system used only for compiling boinc that is regularly scanned with the Kaspersky rescue CD scanner.

if not, you do not somehow have the correctly signed binary and the boinc client should also refuse to run it.


25) Questions and answers : General issues : Web site : Wrong link for Server Status on Mainpage
Posted 1271 days ago by m.somers
Just tested it; it works correctly; the
is cached a bit better and uses less resources than but more or less shows the same.

26) Questions and answers : Platform-specific problems : Unix/Linux : Client error
Posted 1358 days ago by m.somers
Tried this?


27) Message boards : : Number crunching : Workunit twice to the same computer
Posted 1381 days ago by m.somers

this has to do with 'homogenous redundancy'. This project allows for sending the two WUs to the same computer, but not within the period; you can get the sequentially. This 'relaxed' option allows for more throughput of WUs for a project that really needs that 'homogenous redundancy'.


28) Message boards : : Leiden Classical : Work units failing with error missing
Posted 1381 days ago by m.somers

is on the main page....

29) Questions and answers : Platform-specific problems : Unix/Linux : error
Posted 1419 days ago by m.somers
See; you probably need to install the 64 bit versions of MESA / freeglut.


30) Message boards : : Leiden Classical : Scheduler request failed: HTTP file not found
Posted 1509 days ago by m.somers
Well, you'd be suprised; all WU and result enries in the data base are reganerated from one single original one. That one contains spaces. Attempts to modify that (aka removing spaces) will result in a signature mismatch => download error. Removing this means stopping the workflow (stop automatically generating WUs) which means drying the project. This affects many (ALL) users. The error we are dealing with only affects 1% or less of the users/volunteers. All in all the xml parsing error is within the client and having spaces there is not invalid xml as such. So... the situation; there is a bug in the clients XML parsing that affects less than 1% of the volunteers and the assumed workarround (not sure and surely not tested) is stopping a project and all outstanding work for that? See my point?


Next 10 posts

Return to Leiden Classical main page

Copyright © 2016 Leiden University - Leiden Institute of Chemistry - Theoretical Chemistry Department