Posts by floyd

1) Message boards : Number crunching : 100% (Message 1035) Posted 12 Jun 2021 by floyd Post: May be we catch the bug. :) Are you talking about this commit? Well I'm no C++ programmer but to me that does not look like a proper fix. Has it been tested?
2) Message boards : News : Release CmDock v 0.1.3 (Message 1019) Posted 6 Jun 2021 by floyd Post: 06/06/2021 07:47 27,361 docking_log 06/05/2021 17:55 22 docking_out.chk 06/06/2021 07:47 57,754 docking_out.log 06/05/2021 18:03 12 docking_out.progress 06/05/2021 17:55 8 docking_out.sd docking_out.chk and docking_out.progress are kept open during the run, maybe that prevents the timestamps from being updated. You should check the contents of those files to see if they're really not written to.
3) Message boards : News : Release CmDock v 0.1.3 (Message 983) Posted 29 May 2021 by floyd Post: I'm running the first task with the new application version now. Early observations: - The segfaults I observed with the previous version seem to be gone. (Edit: Sorry, I looked in the wrong place. They are still there.) - The progress display looks much more realistic now. However there is a difference between the progress displayed in BOINC Manager and that in the log file. The Manager is several % ahead. Both are going slightly faster than expected. - There is a little bug in progress file generation. Apparently only the beginning of docking_out.progress is overwritten with a new number and a line feed, occasionally leaving a remnant of the previous number: root@zaphod:/var/lib/boinc-client/slots/7# xxd docking_out.progress 00000000: 302e 3235 0a36 3134 0a0a 0.25.614.. root@zaphod:/var/lib/boinc-client/slots/7# xxd docking_out.progress 00000000: 302e 3238 3138 0a31 0a0a 0.2818.1.. The Manager then displays 100% progress until the next step.
4) Message boards : News : Release CmDock v 0.1.2 (Message 972) Posted 26 May 2021 by floyd Post: Results of ligands docking modeling stored in file docking_out.sd. For current target most of results empty, if you see this - don't worry. :) Now that does worry me somewhat. It seems to mean that the result of the computation is simplified to a yes / no answer, or rather yes / not yes, by the client, with no way for you to judge the validity. You completely rely on the wingman to give the same simple answer and after your comment we can even predict that answer. In my opinion you trust both the client and the person operating it too much.
5) Message boards : News : Release CmDock v 0.1.2 (Message 961) Posted 25 May 2021 by floyd Post: Hello! If you see in docking_log file information of completion of all ligands - result is correct. :) Thanks for the confirmation. The log files (?) look complete as long as I can see them - while the computation is still in progress. However out of curiosity I wanted to have a look at the actual result and I can't find any. Where is it stored and what should it look like?
6) Message boards : News : Release CmDock v 0.1.2 (Message 958) Posted 24 May 2021 by floyd Post: New version for Linux - 2.4 released. :) I see many segfaults. AIUI the wrapper crashes when a task is stopped, not suspended. That doesn't seem to affect the result though, all my results are validated. I hope this is correct. :-/
7) Message boards : Number crunching : MD5 check failed for ABU-DHABI.png (Message 838) Posted 28 Apr 2021 by floyd Post: I can't confirm that. Looked through some of my hosts and always found the correct checksum both in client_state.xml and sched_reply_www.sidock.si_sidock.xml. What catches the eye is A) The expected value is not a md5sum. B) You quoted the same message twice. I guess something interfered with the communication. Is the expected value reproducible?
8) Message boards : News : Half a year, the BOINC Workshop and a move to the new server (Message 819) Posted 24 Apr 2021 by floyd Post: I think that we can guarantee a fair challenge. Just by reducing the deadline. :) The project seems to be running smoothly now. Please don't put that at risk to accommodate people who only come here to play games.