• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

New Dpad Muon1 Client

What issues are arising?
Which thread(s) are you looking at?

Version history

A variety of features and bug fixes in this release, which is mainly for maintenance and bringing the code up to date. It includes a more accurate collision detection algorithm so simulations may take longer to complete but will also register more Mpts. Other new features:

1.The program will automatically prune the low-scoring results out of results.dat when it exceeds a certain size (this behaviour is configurable) so that the RAM requirements of Muon1 will not increase indefinitely.
2.By default the program will detect when it is being run on a laptop in battery mode and will sleep until the power is reconnected. In sleep mode it only polls for power every 30 seconds, so may not start up immediately.
3."CPU throttle" configuration switch, to run Muon1 at less than 100% load, either for sharing with other DC projects or to keep systems stable when they have insufficient cooling.
4.HTTP upload chunks increased in size so large results files should upload more quickly.
5.Queue files have different names (queuecli.txt, queuegfx.txt, queue.txt) for the different Muon1 variants (commandline, graphical, background) to avoid clashes.
6.Muon1 will print the final score out in the commandline version when quarantine has finished.
7.-singlethread commandline switch added (mostly for testing).
Bug fixes:

Leak of Windows file handles fixed.
The fixed random seeds used in some lattices worked differently in multithreaded mode than single threaded. This was tracked down to a problem setting the FPU precision in a new thread and has been fixed.
Identical genomes should not be run twice if possible (the algorithm will go back to generate another).
Screensaver now works at the lowered priority specified in config.txt, but interactive graphical mode is normal priority.
Screensaver also uses the correct config.txt, not generating one in the Windows directory!
Problems with clients stopping during lattice changearounds should be reduced.
Finally note that there is the new file muon1startup.exe for automatically putting a shortcut to the background-running Muon1 in the Startup folder.

Feature 1 is a welcome addition & 3&6 are cool 🙂

It includes a more accurate collision detection algorithm so simulations may take longer to complete but will also register more Mpts.

This means the benchmarking scores will likely change.
 
Fixed, via new lattices actually. There was an error in the lattices where I left the "AbsorptionLength" for the orange annulus unspecified. That meant particles went right through in v4.44, which looks for this parameter (4.43x just assumed everything was solid, I think).

There is currently one unresolved bug where clients start producing -2%/0Mpts results. I got it on my laptop once, but it goes away if you restart the program, I've not managed to replicate it, though a couple of others have had it.

^^ what the above means is that the "leaky particles" bug is fixed but the null-results one isn't. But the latter seems to only manifest itself under certain conditions, so you might be OK.
 
Thanks for the update Stephen:thumbsup:

I won't be running DPAD for a couple more weeks so I hope you would of fixed it by then😉
 
Well it's not entirely a repair job but I'm posting a version when I've got somewhere. Have fixed a few things but not the -2%/0Mpts bug, so 4.44b is taken down, with 4.44c coming some time this week, hopefully when I've replicated and fixed that bug.
 
The updates are coming thick & fast now 😀

Btw I tried v4.44a on my friends PC ,each time I tried to run it it would crash DPAD after about 5mins crunching😕 ,as a temp fix I switched it back to the old client......whichever that one was😱

Thanks for the info Stephen 🙂

When I switch back I plan to go full steam ahead for a while to try & catch that pesky Coolkid😉 ,so I hope it's fixed by then...
 
I found it's actually faster by maybe 10% on a Kentsfield, but someone else on the forum is saying it's slower by roughly the same amount. I'm not sure, but it will be the standard client soon for doing stuff with. Though there's also room for improvement in the speed.
 
I guess we'll get a better picture as people have time to observe their stats & re-benchmark.
Unfortunatley I won't be able to do an apple to apple comparision as I've since sold my E6420 (@3.2GHz) & I now have a Q6600 @3GHz 🙂 ,though I guess if I can o/c it to 3.2GHz & on a lower multiplier & just run 2 clients then that's close enough.

(Btw for those who don't know the Kentsfield is the Intel quad core Core 2 excluding the latest Penryn(sp?) ).
 
Originally posted by: Assimilator1
Unfortunatley I won't be able to do an apple to apple comparision as I've since sold my E6420 (@3.2GHz) & I now have a Q6600 @3GHz 🙂
Click to expand...
Yeah and I don't think apple use either of those chips atm.

though I guess if I can o/c it to 3.2GHz & on a lower multiplier & just run 2 clients then that's close enough.
Click to expand...
That's a surprisingly good idea, provided those are all 1-thread clients.

(Btw for those who don't know the Kentsfield is the Intel quad core Core 2 excluding the latest Penryn(sp?) ).
Click to expand...
Penryn is a dual core, Kentsfield was two Conroes (predecessor to Penryn) stuck on a die, and now the new two-Penryns-stuck to gether core is called Somethingelsefield. {Googles} Yorkfield, that's it.

I'm not sure anyone else really needs to know all this.

While I've still got 40 minutes left of the day, I thought I'd make sure I say happy birthday er I mean christmas everyone. Though I think everyone should have their birthday on the same day too, it would make remembering them and probably the census a lot easier too.

(Edit: I should probably lay off the festive parrot juice.)
 
lol ,yea I recon so😉

Re apples ,I meant the phrase not the computer😉
And yes I was thinking of 1 threaded clients ,though Im not sure how atm.

I mentioned Kentsfield as many people wouldn't know/remember what it is.
My bad on Penryn😱

A belated happy xmas 😉
 
It may just be my machines, but I am still having occasional crashes on my XP and Vista machines. Win2k runs the client fine, not a single crash there, so far. XP machine was so bad I reverted back to the 443d client there.
Just wondering if other people are having any issues?
 
My 2nd PCs DPAD client (v4.44c) crashed once about 1-2wks ago but has been OK since😕

I've had 4 clients running on my main PC for about 4-5 days & so far no problems 🙂 (other than the new client doesn't flush enough giving me stats withdrawal😛)

Btw OK how far ahead of me are ya?😀

Talking of stats ,I won't have time to do them tonight but I'll collect the data for tomorrow.
 
As Stephen mentioned in my stats thread v4.44d is now out 🙂

Get the patch or full download here

I'm going to switch now I think.

v4.44d updates

- - - [4.44d] - - -
This version is primarily for bug fixes, but I have also improved the load balancing on multi-CPU systems and allowed Muon1 to send in results more frequently on optimisations that have short genomes (50 results in results.txt triggers a send as well as hitting 100`000 bytes). Bugs fixed are:

Memory leak (actually two leaks) causing increasing RAM usage of up to 40MB/day.
Freezing (actually a very long sleep) when restoring a laptop from sleep mode and using the CPU throttle.
Initialisation after restoring an autosaved file was not complete, causing crashes in some installations.
Fixed glitch where it displayed processors detected even when just using the -version switch.

Stephen
Does a single client now load multi core rigs to 100%? & does it match performance of 1client/core? (or will I have to test that out?😉)
 
So guys is it safe to update my crunchers with the new client? This will take a lot of work , so I don't wanna redo it in a week..
 
Originally posted by: amdxborg
So guys is it safe to update my crunchers with the new client? This will take a lot of work , so I don't wanna redo it in a week..
Click to expand...

I'm assuming you're running 4.43 now, right Johan? If that's the case and I were you (I wish 😉) I'd stick with it until the issues are settled unless Stephan says otherwise. You produce too much science to have the problems whack your output.

-jim

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top