Posts by meshmar

1) Message boards : Number crunching : Merging computers (Message 48158) Posted 30 Oct 2007 by meshmar Post: It would really be nice if R@H upgrade the Boinc Server Software, so more hosts could be merged ...
2) Message boards : Number crunching : Job Sizes (Message 37571) Posted 7 Mar 2007 by meshmar Post: Setting preferences affects how long the WU actually crunches. The fact that the estimated time is way off has a major impact on my downloaded queue for ALL my projects - not just Rosetta. If a Rosetta WU can't be acurately predicted by Boinc then it is a Rosetta issue - not a Boinc issue ... Boinc doesn't "predict" the run time; it doesn't know that you have chosen a run time of 4 hours or 24 hours until you run a few tasks at the preferred length and boinc learns it by adjusting the DCF accordingly. You can hasten the learning process by adjusting the DCF manually yourself, if you feel up to it. It is better to learn how the system is designed to work and accomodate it. I've had Rosetta running on the same boxes with no changes in settings for a long time. The predicted time changes every time a different type of WU is sent by Rosetta. Sometimes this can be a drastic change. Some of the recent WUs have been predicted for 24 hour run times! I should not be required to adjust the DCF every time Rosetta sends a different type of WU. If I have a preferred run time of 4 hours, then my predicted time should NEVER be more then 4 hours the first time a new type of WU is sent. If it is, then Rosetta and Boinc have issues that need to be fixed.
3) Message boards : Number crunching : Job Sizes (Message 37537) Posted 6 Mar 2007 by meshmar Post: Setting preferences affects how long the WU actually crunches. The fact that the estimated time is way off has a major impact on my downloaded queue for ALL my projects - not just Rosetta. If a Rosetta WU can't be acurately predicted by Boinc then it is a Rosetta issue - not a Boinc issue ...
4) Message boards : Number crunching : Problems with Rosetta version 5.46 (Message 36852) Posted 15 Feb 2007 by meshmar Post: Please report here for problems you have observed with Rosetta version 5.46. "Waiting for memory" I have never seen this message previously, but two Rosetta units, the final one in the queue from 5.45 and the first from 5.46, have both just now stopped, with the message "waiting for memory." This has not happened before. There are two new setting in your "General Preferences". They are "use at most X percent ram while active", and "use at most X percent of ram when not active". By default they are set to 50 and 90 respectively. Try increasing them. tony I was aware of the change in preferences, and had changed mine already. Only one of my 'crunchers' had a problem - and only with some of the Rosetta WUs. These WUs seem to grab a LOT more memory than others, and that leads to the problem with 'waiting for memory' ....
5) Message boards : Number crunching : Problems with Rosetta version 5.45 (Message 36075) Posted 4 Feb 2007 by meshmar Post: That's the one Feet1st. I tried resetting - and it did the same for a batch more wu ... so now that system is happily working on Malaria and Tampaku. No idea why it suddenly decided it didn't like Rosetta. Every other system is still working on them with no issues ...
6) Message boards : Number crunching : Problems with Rosetta version 5.45 (Message 36029) Posted 3 Feb 2007 by meshmar Post: I've started getting "Computation Error" for every Rosetta wu. the messages all show the same as the few below: 2/2/2007 6:20:28 PM\|rosetta@home\|Reason: Unrecoverable error for result 1who__BOINC_ABRELAX_NEWRELAXFLAGS_frags83__1521_4110_0 (No main program specified) 2/2/2007 6:20:30 PM\|rosetta@home\|Reason: Unrecoverable error for result 1louA_BOINC_ABRELAX_NEWRELAXFLAGS_frags83__1522_4982_0 (No main program specified) 2/2/2007 6:20:31 PM\|rosetta@home\|Reason: Unrecoverable error for result 1hz6A_BOINC_ABRELAX_NEWRELAXFLAGS_frags83__1521_4982_0 (No main program specified) 2/2/2007 6:20:32 PM\|rosetta@home\|Reason: Unrecoverable error for result 1acf__BOINC_ABRELAX_NEWRELAXFLAGS_frags83__1521_4983_0 (No main program specified) (No main program specified) ... Right now I have 37 of them on one system - which does neither you nor I any good at all.
7) Message boards : Number crunching : 40 points +/- on the same machine? (Message 29035) Posted 8 Oct 2006 by meshmar Post: It is time to get the garments ready: "optimized client" Again!!!!! YAwn!!!!! Optimized clients are NOT available for every OS/CPU/... therefore they are NOT the solution. Of course, you want the inflated numbers they generate and care less about the actual results they produce. Old credit system = grant based upon benchmarks (some of which were falsified) New credit system = grant based upon actual work produced (not hours ran, Stevea ... output) Was the old system fair - no Is the new system fair - no (but it's a lot closer than the old system)
8) Message boards : Number crunching : Forget credit for a moment and look at this. (Message 26816) Posted 15 Sep 2006 by meshmar Post: Now imagine another 2000 good machines running on this project. A shame that isn't happening anymore..such a shame..oh well.. edit: I said something like I'm disappointed about that he left but keeps dragging the project in the mud. My wording was a bit strong, so I moderated myself. ;-) It would be dragging the project in the mud if what he was saying were a lie: He is not saying a lie; he is stating a fact. Opinion is not fact - especially when it's a rather narrow-minded opinion. An opinion isn't necessarily a lie ... but it ISN'T fact.
9) Message boards : Number crunching : Report Problems with Rosetta Version 5.25 (Message 22556) Posted 16 Aug 2006 by meshmar Post: Hi, I'm having the same problems with Rosetta@Home "hanging" (it shows "running" but the CPU is at 0%). Usually it occurs within 23%~26% of processing the unit. The same thing happens with World Community Grid as well, but I know that's another project. ALL other projects work fine. I'm on a P4C 2.6 GHz, 512 MB RAM running Xubuntu. Nothing is overclocked. The workunits below I know are "stuck": FRA_t370_CASPR_hom001_6_t370_4_2a2jA_IGNORE_THE_REST_223_1078_61_0 FRA_t322_CASPR_hom001_6_t322_3_1u1zA_IGNORE_THE_REST_17_1079_65_1 There are a lot more that I've had to abort over the weeks, but my log only goes so far. FRA_t322_CASPR_hom001_6_t322_3_1u1zA_IGNORE_THE_REST_341_1079_74_0 did the same on one of my systems. 20.153% progress; running; cpu idle. Shutting down Boinc and then restarting it caused rosetta to start running a second WU and to show FRA_t322_CASPR_hom001_6_t322_3_1u1zA_IGNORE_THE_REST_341_1079_74_0 as preempted ... Running Boinc 5.4.11