Discussion Thread for the Continuous GW Search known as O2MD1 (now O2MDF - GPUs only)

I gave up on GW altogether, not due to RAM, but due to my CPUs being rubbish at assisting.  I did have one combo which worked, but it requires running 2 GW on the GPU so the CPU can allocate 2 cores to help.  But now they're too big and go very slowly.  I build PCs from cheap parts and they run what they can run.  I like recycling.

Ah that makes sense, the initial count does look rather like a timer rather than actual progress, which would be less even.

Although, when I load several Theory tasks from LHC at once onto my 24 core computer without an SSD, it can take ages for them to start as the disk tries to catch up, and no counter appears.  Perhaps Boinc realises the disk is busy and doesn't get so impatient?

There is "pseudo-progess" code in the client for those projects that don't report % completed.

You can typically see the progress percentage climb quickly in small incremental jumps within the first minute or so of starting a task until the task writes out a checkpoint and then reports its actual progress.

DA put that piece of code in for some of the very long completion tasks on some projects. Trying to reduce the number of posts/complaints that people never see any task move towards a finish and they think the task is stalled out.

Don't know.  Probably not as there should be code that detects an actual stall.  I'd have to find the code again in the client where it got implemented.

Richard Haslegrove would know for sure and can probably find the code blob much quicker than I could.

is there a reason you keep wanting to run the beta app? seriously. is it faster? or was it an arbitrary decision?

_________________________________________________________________________