Posts by robertmiles

21) Message boards : RALPH@home bug list : Rosetta 4.12+ (Message 6678) Posted 5 Apr 2020 by robertmiles Post: Starting to see some rosetta 4.13 work on one of my Ubuntu servers since this afternoon. So far all showing success. I'm guessing 4.12 did not make it to prod then. Rosetta work seems to have been depleted 4,12 made it over on Rosetta@home, even if it was not tested first on Ralph@home. New users over on Rosetta@home are trying to download more tasks much faster than new tasks are created. Work over there WILL be depleted until they work out ways to generate new tasks faster.
22) Message boards : RALPH@home bug list : Rosetta_beta 4.0+ (Message 6565) Posted 25 May 2018 by robertmiles Post: More Error while computing, for v4.07 windows_intelx86: http://ralph.bakerlab.org/result.php?resultid=4828008 Reason: Access Violation (0xc0000005) at address 0x00B1C0E8 write attempt to address 0x0FC2512C http://ralph.bakerlab.org/result.php?resultid=4834727 ERROR: HybridizeFoldtreeDynamic: failed to build fold tree from cuts and jumps http://ralph.bakerlab.org/result.php?resultid=4838682 ERROR: HybridizeFoldtreeDynamic: failed to build fold tree from cuts and jumps http://ralph.bakerlab.org/result.php?resultid=4839839 Reason: Access Violation (0xc0000005) at address 0x00B1C0E8 write attempt to address 0x1614B12C http://ralph.bakerlab.org/result.php?resultid=4839899 ERROR: HybridizeFoldtreeDynamic: failed to build fold tree from cuts and jumps http://ralph.bakerlab.org/result.php?resultid=4839875 ERROR: HybridizeFoldtreeDynamic: failed to build fold tree from cuts and jumps Also a few for v4.07 windows_x86_64: http://ralph.bakerlab.org/result.php?resultid=4837014 ERROR: HybridizeFoldtreeDynamic: failed to build fold tree from cuts and jumps http://ralph.bakerlab.org/result.php?resultid=4838794 ERROR: HybridizeFoldtreeDynamic: failed to build fold tree from cuts and jumps http://ralph.bakerlab.org/result.php?resultid=4838713 Reason: Access Violation (0xc0000005) at address 0x00007FF744AEA206 read attempt to address 0xFFFFFFFF http://ralph.bakerlab.org/result.php?resultid=4838711 Reason: Access Violation (0xc0000005) at address 0x000001F42FECB1C0 http://ralph.bakerlab.org/result.php?resultid=4841528 ERROR: HybridizeFoldtreeDynamic: failed to build fold tree from cuts and jumps And a v4.07 windows_x86_84 Validate error: http://ralph.bakerlab.org/result.php?resultid=4838714 ERROR: HybridizeFoldtreeDynamic: failed to build fold tree from cuts and jumps But some of these same error messages occur for tasks that are Completed and validated, for example: http://ralph.bakerlab.org/result.php?resultid=4838712 ERROR: HybridizeFoldtreeDynamic: failed to build fold tree from cuts and jumps http://ralph.bakerlab.org/result.php?resultid=4839930 ERROR: HybridizeFoldtreeDynamic: failed to build fold tree from cuts and jumps 64-bit Windows Microsoft Windows 10 Pro 10.0.17134 Build 17134
23) Message boards : RALPH@home bug list : Rosetta_beta 4.0+ (Message 6563) Posted 25 May 2018 by robertmiles Post: Looks like whoever wrote the message on 24/4/18 is still waiting for information on which versions of Windows were used for the 32 bit failures. If so, there's no point in complaining about lack of another message or fix until more people supply this information. I just had a failure for Rosetta v4.07 windows_intelx86 under 64-bit Windows. http://ralph.bakerlab.org/result.php?resultid=4826810 Microsoft Windows 10 Pro 10.0.17134 Build 17134
24) Message boards : RALPH@home bug list : Rosetta_beta 4.0+ (Message 6223) Posted 3 Nov 2017 by robertmiles Post: One of my computers ran a few tasks for rosetta_beta_4.05 under Windows 10. All failed in less than one minute each, with error messages suggesting that the application has problems reading something in one of the input files.
25) Message boards : Number crunching : Ralph support OpenCL ? (Message 6176) Posted 15 Apr 2017 by robertmiles Post: I'll consider starting to make some BOINC applications for OpenCL AFTER I find and take an online class in OpenCL that is intended for programming GPUs, not FPGAs. I cannot travel enough to use in-person classes instead. BOINC now supports use of CUDA and OpenCL; I've seen no information on whether it can also handle the various other ways of programming GPUs that have already been mentioned in this thread. I'd expect library compatibility problems to block use of some of them at least until future versions of BOINC build in replacements for the incompatible sections of the libraries.
26) Message boards : RALPH@home bug list : Rosetta mini beta and/or android 3.61-3.83 (Message 6063) Posted 19 Mar 2016 by robertmiles Post: These workunits gave a a computation error at about the same time that a workunit from another BOINC projects reached a point with a rather high memory demand - over a gigabyte. So they might be due to running out of memory, rather than anything else. http://ralph.bakerlab.org/result.php?resultid=3762275 http://ralph.bakerlab.org/result.php?resultid=3761810 http://ralph.bakerlab.org/result.php?resultid=3761801 http://ralph.bakerlab.org/result.php?resultid=3757576 http://ralph.bakerlab.org/result.php?resultid=3756003 However, my other computer running BOINC rarely runs out of memory, and gave a different error for some recent workunits. http://ralph.bakerlab.org/result.php?resultid=3757706 http://ralph.bakerlab.org/result.php?resultid=3753036 http://ralph.bakerlab.org/result.php?resultid=3752853 The application was shown as Rosetta Mini Beta, with no version number I could find after the workunits finished. The second computer shows three workunits that may be this type, still marked as version 3.72 while still on the computer. http://ralph.bakerlab.org/result.php?resultid=3763701 http://ralph.bakerlab.org/result.php?resultid=3762417 http://ralph.bakerlab.org/result.php?resultid=3763972 I've already looked into adding more memory for each of my computers that run BOINC. Their motherboards are not compatible with adding more.
27) Message boards : RALPH@home bug list : minirosetta beta 3.50-3.52 apps (Message 5815) Posted 26 Feb 2015 by robertmiles Post: Received this error on Task 3335547 ERROR: Error: can't read sequence! Use -in::file::fasta sequence.fasta or -in::file::native native.pdb! ERROR:: Exit from: src/protocols/abinitio/AbrelaxApplication.cc line: 488 std::cerr: Exception was thrown: [ERROR] EXCN_utility_exit has been thrown from: src/protocols/abinitio/AbrelaxApplication.cc line: 488 ERROR: Error: can't read sequence! Use -in::file::fasta sequence.fasta or -in::file::native native.pdb! Conan Same here. Got about a dozen or so WUs and they crap out faster than you can shake a stick at... :-( Ralf Similar problem here, but about 25 failed workunits so far, spread over two computers. The error message suggests that either an input file used by most of today's workunits is corrupted, or the command line that tells the application to use that file is defective.
28) Message boards : RALPH@home bug list : Minirosetta Beta 3.14 (Message 5407) Posted 1 Nov 2011 by robertmiles Post: Could be trying to track down a bug with 3.14 that I saw several times over on Rosetta@Home. If so, something to watch for: Shortly after a checkpoint, the workunit stops using any CPU time at all, WITHOUT telling BOINC it has encountered a problem so that some other workunit can be started instead. If so, the time limit checking cannot run, so the workunit can easily sit there looking like it's running, but not actually doing anything, for many times as long as you've selected for workunits to run.
29) Message boards : RALPH@home bug list : Rosetta mini 3.18 (Message 5406) Posted 1 Nov 2011 by robertmiles Post: These work units take a very long time to run (around 10 hours on a 6 hour preference) and return very poor credit for the effort (31 points) See WU 2305565 I have another two of these running at the moment and both are already over 9 hours and still going. I also have a 3.17 WU that is over 9 hours as well. Most only run 1 to 2 hours. Conan These could be looking for a bug I saw earlier in 3.14. If so, something it would be useful to watch for: The workunit stops using any CPU time at all, WITHOUT telling the BOINC manager that there is a problem so that another workunit can run instead. If that's the problem, the workunit can easily sit there not really running for days, since the time limit detection can't run either.
30) Message boards : RALPH@home bug list : Web site bugs (Message 5351) Posted 13 Jul 2011 by robertmiles Post: The server status on the home page hasn't been updated for the last several weeks. The separate server status web page is getting updates, though.
31) Message boards : Feedback : Freeze server status on home page (Message 5350) Posted 13 Jul 2011 by robertmiles Post: Still frozen, since June 1.
32) Message boards : RALPH@home bug list : Minirosetta Beta 3.14 (Message 5339) Posted 17 Jun 2011 by robertmiles Post: Thanks for replying.
33) Message boards : RALPH@home bug list : Minirosetta Beta 3.14 (Message 5336) Posted 16 Jun 2011 by robertmiles Post: Still more: I clicked on the workunit, then Show graphics. Another window, all black inside. I clicked on the X to close that window and got a windows error message for minirosetta_graphics_3.13_windows_x86_64.exe. Details too long to copy, but I used the snipping tool to capture pictures of it. If those details would be useful, how do I send the pictures? Windows Task Manager does not list any program with that name among the programs now running or suspended, and did not when I started this series of messages.
34) Message boards : RALPH@home bug list : Minirosetta Beta 3.14 (Message 5335) Posted 16 Jun 2011 by robertmiles Post: I decided to inspect the list of files in the slot for the failed workunit; it appears that the last file modified there was about 6 hours ago. I also inspected the files lists under minirosetta-database and found that the sections for metal ions do not appear to list aluminum, even though it is connected to the brain damage in one of the later stages of Alzheimer's, or copper, even though the human brain's natural defense against Alzheimer's uses a copper-binding protein. I assume that is not important for this workunit, but how important is it for Rosetta@Home workunits aimed at Alzheimer's?
35) Message boards : RALPH@home bug list : Minirosetta Beta 3.14 (Message 5334) Posted 16 Jun 2011 by robertmiles Post: I've now identified: Minirosetta Beta 3.14 - Windows Internet Explorer It was the browser window under which I entered the last few messages. CPU time at last checkpoint of the faulty workunit: 03:33:00 CPU time for the workunit: 03:33:15 Could this indicate a problem with resuming normal operation after checkpoints? I've forgotten just which BOINC project has often been showing workunits stopping any use of CPU time about that soon after a checkpoint lately. Would a separate thread used mainly for checking for such conditions be useful? I've added up the memory currently reported as in use by 32-bit programs. About 1.7 GB total, so I don't expect any problem from that.
36) Message boards : RALPH@home bug list : Minirosetta Beta 3.14 (Message 5333) Posted 16 Jun 2011 by robertmiles Post: I've now found something that might be the graphics application: Minirosetta Beta 3.14 - Windows Internet Explorer Listed under Applications under Windows Task Manager, not under Processes, and therefore shown without any task name. Have not found any way to show the resource usage of anything listed only as an application. Total disk usage by all programs about 1 MB per minute, and mainly by system programs. Total network usage about 1 MB per minute, mainly by boincmgr.exe and boinc.exe. BOINC 6.10.58 64-bit Vista SP2, with almost all updates offered except Internet Explorer 9 My other computer has already returned its 3.14 workunit hours sooner than its previous estimated time to completion; already marked as a success. Same versions of BOINC and Windows.
37) Message boards : RALPH@home bug list : Minirosetta Beta 3.14 (Message 5332) Posted 16 Jun 2011 by robertmiles Post: A few more details: The workunit not using CPU time had a 530 MB maximum working set size. Was running in 32-bit mode. Any plans to offer a 64-bit version of this application, even if its main advantage is to help computers like mine that seem to have a limit of around 4 GB on the maximum amount of memory that can be assigned to the entire set of 32-bit programs (BOINC or not) that are in memory at once? More memory is installed, but seems useful mainly for 64-bit programs. I haven't found a task name for the graphics app. What should I be looking for? My other computer also has a 3.14 workunit, running in high priority mode but at least still showing an increasing progress.
38) Message boards : RALPH@home bug list : Minirosetta Beta 3.14 (Message 5331) Posted 16 Jun 2011 by robertmiles Post: One where BOINC thinks the workunit is still running, but it's using no CPU time at all now: http://ralph.bakerlab.org/workunit.php?wuid=1802588 Elapsed 07:01:04 48.46% progress and no longer changing To completion 06:27:09 I normally don't have the graphics portion showing, but when I asked for it, it came up solid black. Anything special I need to do to send back useful information on why?
39) Message boards : Number crunching : Ralph support OpenCL ? (Message 5330) Posted 16 Jun 2011 by robertmiles Post: Now also POEM@home support OpenCL.... Correct, but for CPU workunits only so far. They appear likely to be waiting for the 6.14.* series of BOINC versions that should finally add a reasonable amount of support for OpenCL GPU workunits. No word yet on whether the new Rosetta Mini Beta 3.* workunits use any OpenCL or not. Milkyway@Home is offering both CPU and GPU OpenCL workunits, but watch for a few restrictions on the GPU workunits: 1. If your computer has more than one GPU, you must make Milkyway@Home the only BOINC project using any of them, so they can use their own mapping from the GPU numbers BOINC uses to the ones OpenCL uses. However, if your computer has only one GPU, the fact the BOINC has told it to use a GPU is enough to insure that any GPU it can find is the right one, even if some other BOINC projects uses it at other times. 2. You'll need to expect many changes in the GPU workunits when the 6.14.* versions of BOINC start becoming available. 3. Unclear if their AMD/ATI workunits are ready to use OpenCL yet. 4. You MUST have a GPU capable of double precision to run their GPU workunits - a few of the high-end AMD/ATI-based graphics boards from the last few generations, a graphics board based on an Nvidia Fermi chip, a GTX 2xx series Nvidia-based board from GTX 260 up, or a few other high-end graphics boards. I would have expected more BOINC projects offering GPU workunits sooner if Nvidia and AMD/ATI had made it easier by offering ways to create programs partly in OpenCL and partly in their previous GPU computer languages, but that would have put AMD/ATI at a disadvantage since they had much less complete function libraries for their previous GPU computer language.
40) Message boards : RALPH@home bug list : Minirosetta Beta 3.06 (Message 5292) Posted 10 May 2011 by robertmiles Post: T0617_casp9_symm_cm_SAVE_ALL_OUT_IGNORE_THE _REST_control_15317_68 Another workunit that stopped using any CPU time at all shortly after a checkpoint, WITHOUT boinc.exe recognizing this. CPU time at last checkpoint 00:04:28 CPU time 00:04:30 Elapsed time 02:37:06 Still not clear if the Tthrottle extension I'm using to prevent the computer from overheating has anything to do with the problem. Hope you at least got enough debugging output to pin down the problem more.

Previous 20 · Next 20