Posts by Mikie Tim T

1) Message boards : Number crunching : BOINC 5.4.9 new recomended version released (Message 13581) Posted 12 May 2006 by Mikie Tim T Post: Get it while it's hot!!! And risk getting burned? Burned by what? I think MikeW's referring to the last round of 5.2.* clients, when there was a new recommended client every other day to fix firewall issues and the like.
2) Message boards : Number crunching : WUs starting from beginning at each start of BOINC (Message 6390) Posted 5 Mar 2005 by Mikie Tim T Post: > Real drag though, in an hour, the workunit gets to about 90-94% completion > when LHC swaps out, if the computer (or sixtrack) was just a snick faster, I'd > manage to get that sucker done. Instead I find out 4 hours later that it > restarted back at 0 again. > > Unless someone has a different solution, I'm going to have to detach LHC from > BOINC. I hate to spend the effort on something that is just wasting resources > that could be used to analyse the other 3 programs I'm running on BOINC. Another thing you could consider doing, at least until they get this issue figured out, is to set the "Switch Between Applications Every xx Minutes" setting in your profile to something greater than what it is currently set to. That should let you finish the workunit you're working on, unless it's a really long running one. You may want to consider at least doubling what you currently have it set to.
3) Questions and Answers : Wish list : Results and pending credit links (Message 5854) Posted 22 Feb 2005 by Mikie Tim T Post: Does anyone have any idea what the plan is to turn the Results and Pending Credit links back on that are currently temporarily disabled? I know that the project just started back up and the admins have undoubtedly been swamped with issues popping up with all of the sudden activity, but the new hardware should be able to support querying this information now that things have settled down a bit if the new system was spec'd properly.
4) Message boards : LHC@home Science : Predictor Back Online (kind of) (Message 5521) Posted 24 Dec 2004 by Mikie Tim T Post: > From their site (http://predictor.scripps.edu/): > > Status > Predictor@Home has been upgraded! We are in the process of bringing it online. > NOTE: Over the Christmas Holiday we will not be submiting work units due to a > database problem. > > News > 12/22/04 > There are a number of things happening at P@H. P@H is now running on our new > dual Intel(R) Xeon(TM) CPU 3.40GHz servers with 4 gigabytes memory each! We > are in the process of updating the P@H web site with current information. > Please Stay tuned...... > > 12/21/04 > We're Back! P@H should be on-line before the new year. > > I can't access their website at all. I've been waiting for this project to reactivate to sign up and join in, but they've had the new account signup disabled for many months now. Has that now changed as well?
5) Message boards : Number crunching : LHC official status report (Message 4961) Posted 6 Nov 2004 by Mikie Tim T Post: > since it doesn't have many users and runs out of work as well > =========== > > And thats the way it will probably always be since the Dev's have already > stated they have to examine the Work before releasing any new WU's... > > And why would they reset the credits, they didn't after they went live because > they found the work valuable, now after a few months later they wouldn't find > the work valuable ... > > To me it would be a slap in the face to have everybody run this many WU's > & then reset the Credits on them ... > > The good part of the reengineering of the backend systems is that they are replacing the job management and analysis systems, so even if they must continue to analyze our results before submitting a new batch, the delay should be much shorter than we've experienced in the past. If that is the case, then we'll be even happier with the second cut of LHC@Home. I wish them luck on procurring as competent a team as put together the first cut.
6) Questions and Answers : Windows : Boinc/sixtrack failure to correctly allocate multitasking of WU�s (Message 4745) Posted 1 Nov 2004 by Mikie Tim T Post: > With Boinc v4.09 used on a HT PC and the last WU is crunched, Boinc eats 50% > of CPU power. > This problem has been fixed with Boinc v4.13. You can download that version <a> href="http://setiweb.ssl.berkeley.edu/download.php">here[/url]. > > LHC works fine with that version. I have also experienced this in the past when I was down to a single workunit, but on a 2-processor system, so it wasn't just specific to HT processors. I haven't had any issues with this occurring since 4.13, but I also have made sure that I always have enough work across CPDN, Seti, and LHC to keep both busy at all times.
7) Message boards : Number crunching : Linux 64-bit (Message 4530) Posted 28 Oct 2004 by Mikie Tim T Post: > I would not mind doing some 64 bit benchmarks / test units to see if there is > a large difference in the results. > > If however the results are more accurate it would be nice to know about it in > advance so people that have 64 bit capable machines can give more accurate > readings. It would not be nice if an atom would hit the wall because of a miss > calculation by a 32 bit machine. > > If 64 bit would be more accurate it can also be used to validate 32 bit > results and give a higher change of success. > Does the SixTrack software use integer calculations for the simulations? I figured that it would use floating point calculations, but please correct me if I assume incorrectly. If it uses the FPU, then it would be using 80 bit precision even on 32 bit integer cores and has since at least the i387 coprocessor days.
8) Questions and Answers : Windows : Scheduler seems to be having some issues this morning (Message 3148) Posted 3 Oct 2004 by Mikie Tim T Post: After selecting Update in the GUI, the log started logging this: LHC@home - 2004-10-03 02:25:29 - Sending request to scheduler: http://lhcathome-sched1.cern.ch/scheduler/cgi LHC@home - 2004-10-03 02:30:40 - Scheduler RPC to http://lhcathome-sched1.cern.ch/scheduler/cgi failed LHC@home - 2004-10-03 02:30:40 - No schedulers responded LHC@home - 2004-10-03 02:30:40 - Deferring communication with project for 1 minutes and 0 seconds LHC@home - 2004-10-03 02:31:40 - Sending request to scheduler: http://lhcathome-sched1.cern.ch/scheduler/cgi LHC@home - 2004-10-03 02:31:44 - Scheduler RPC to http://lhcathome-sched1.cern.ch/scheduler/cgi succeeded LHC@home - 2004-10-03 02:31:44 - SCHEDULER_REPLY::parse(): bad first tag Content-type: text/plain LHC@home - 2004-10-03 02:31:44 - Can't parse scheduler reply LHC@home - 2004-10-03 02:31:44 - Deferring communication with project for 1 minutes and 0 seconds Does this indicate an issue with something on the client, or a bad response from the scheduler when it actually does finally succeed in responding?

LHC@home