12/12/2016 4:12:50 AM | Einstein@Home | No work is available for Multi-Directed Continuous Gravitational Wave search CV
There is enough work for O1MD1CV available. As far as I can see your computers don't request work for CPU's so the server is not giving you any. Maybe there is another project on your computer that is hogging all the CPU cycles? If you have a lot of FGRPB1 CPU work you can simply abort that and then try to get O1MD1CV work.
Christian you are correct on two computers I run Einstein on my GPUs and Seti on my CPUs. The 3rd computer runs a 50/50 balance between Seti and gravity waves on it's cpu.
P.S.
For some reason i also can not get any GW work too. while server status page says about 10 000 WUs ready to send
12/12/2016 13:06:14 | Einstein@Home | No work is available for Binary Radio Pulsar Search (Arecibo, GPU)
12/12/2016 13:06:14 | Einstein@Home | No work is available for Gamma-ray pulsar binary search #1 on GPUs
12/12/2016 13:06:14 | Einstein@Home | No work is available for Multi-Directed Continuous Gravitational Wave search CV
12/12/2016 13:06:14 | Einstein@Home | No work is available for Multi-Directed Continuous Gravitational Wave search G
I looked at the recent logs of all your hosts and all but one didn't request any CPU work so they didn't get any but the message says "No work available" which is misleading in that case (I'm not sure where this comes from). The one that requested CPU work got 6 O1MD1G tasks. So I think your hosts are fine with CPU work for now.
Thanks for the info. You are right - other hosts was loaded with a lot of CPU work from other BOINC projects at that moment. So requested only GPU work from E@H because GPU queue was empty while CPU queue full. After processing part of CPU queue they got Gravitational Wave WUs without any problem.
Just for extra clarity. With that do you mean only BRP for AMD and NVIDIA GPUs and BRP for ARMs, Androids and Intel GPU continues as before?
There are two separate science runs. BRP4G uses bundled tasks for the much faster discrete GPUs. BRP4 uses 'singles' for slower 'mobile' devices. Supply for the former runs out regularly whilst awaiting new data. An attempt is made to provide a continuous supply for the latter.
Well, actually the data is the same, and so is the "science", the separation is rather technical. Indeed we try to hold a couple of "beams" (of which processing is considered not that urgent) back to keep our our slow devices (Android, ARM/Linux etc.) fed. We process about 2 beams/d with these, compared to >100 bemas/d with GPUs, so the few hundred beams hold back would only last a few days for the GPUs.
When we get new data from Arecibo, this will (semi-) automatically be fed into the BRP4G pipeline and "work" for that application will become available again (so don't disable it yet). In that sense this "run" hasn't ended yet. However currently it's unclear to us when we will get new data from Arecibo, or even whether at all.
Betreger wrote:12/12/2016
)
There is enough work for O1MD1CV available. As far as I can see your computers don't request work for CPU's so the server is not giving you any. Maybe there is another project on your computer that is hogging all the CPU cycles? If you have a lot of FGRPB1 CPU work you can simply abort that and then try to get O1MD1CV work.
Christian you are correct on
)
Christian you are correct on two computers I run Einstein on my GPUs and Seti on my CPUs. The 3rd computer runs a 50/50 balance between Seti and gravity waves on it's cpu.
There're plenty of GPU wus
)
There're plenty of GPU wus available in gamma-ray pulsar search.
Arif Mert Kapicioglu
)
For windows?
Betreger wrote:Arif Mert
)
Sorry I've missed that detail:)
Christian Beer wrote:Mad_Max
)
Thanks for the info. You are right - other hosts was loaded with a lot of CPU work from other BOINC projects at that moment. So requested only GPU work from E@H because GPU queue was empty while CPU queue full. After processing part of CPU queue they got Gravitational Wave WUs without any problem.
Just misleading message.
Gary Roberts wrote:Juha_6
)
Well, actually the data is the same, and so is the "science", the separation is rather technical. Indeed we try to hold a couple of "beams" (of which processing is considered not that urgent) back to keep our our slow devices (Android, ARM/Linux etc.) fed. We process about 2 beams/d with these, compared to >100 bemas/d with GPUs, so the few hundred beams hold back would only last a few days for the GPUs.
When we get new data from Arecibo, this will (semi-) automatically be fed into the BRP4G pipeline and "work" for that application will become available again (so don't disable it yet). In that sense this "run" hasn't ended yet. However currently it's unclear to us when we will get new data from Arecibo, or even whether at all.
BM