This does not sound like the same problem described in the recent post.
That's because this thread is about validation errors and you get "Error while computing". ;-)
Your ABP CUDA tasks all error out with
[20:44:54][6804][ERROR] Error acquiring "real" CUDA device!
------> The acquired device is a "Device Emulation (CPU)"
[20:44:54][6804][ERROR] Demodulation failed (error: 1014)!
Perhaps you should disable "Use NVIDIA GPU" in your Einstein@Home preferences until you have found the reason for that problem.
Did you reboot your computer recently? Sometimes that clears something "stuck" with the CUDA device.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
Can someone please tell me why this unit has not been sent back out to more pc's? My pc is the one pc that finished the unit, 2 other people did not and yet it has not been sent back out to anyone else yet!
Tnx Rob, it took 2 wingmen to process it but it did clear. It was passed on after 2 other wingmen gave up on it i think. lol.. anyway all is well and thank you.
(It did take alot of proc. time so mabey they dident want to wait that long?)
Can someone please tell me why this unit has not been sent back out to more pc's? My pc is the one pc that finished the unit, 2 other people did not and yet it has not been sent back out to anyone else yet!
There were a couple of workunits (ABP, around Oct 1) we need to mess around with manually, which could have had bad side effects on the "transition time" (next time the transitioner will look at them and may e.g. generate more tasks to be sent). In case of this workunit it was set to Nov 28th, at which time the problem should have cleared itself.
I now manually reset the transition time for this workunit, an a new task to be sent out was generated. Unfortunately I can't think of a way to automatically detect all such workunits that are stuck for a while and reset the transition time, normally we would simply have to wait.
RE: This does not sound
That's because this thread is about validation errors and you get "Error while computing". ;-)
Your ABP CUDA tasks all error out with
Perhaps you should disable "Use NVIDIA GPU" in your Einstein@Home preferences until you have found the reason for that problem.
Did you reboot your computer recently? Sometimes that clears something "stuck" with the CUDA device.
Gruß,
Gundolf
Computer sind nicht alles im Leben. (Kleiner Scherz)
Just one validate error to
Just one validate error to report:
http://einsteinathome.org/workunit/84466697
Claggy
Here are a couple which might
Here are a couple which might be worth re-validating:
http://einsteinathome.org/workunit/81836424
http://einsteinathome.org/workunit/84156120
Not an error exactly but this
Not an error exactly but this one has been ready for 10days now and due to expire in 3 days i think.
http://einsteinathome.org/task/201185024
Its rather old and all the others have been fine but that one.
tnx
oops .. better link
http://einsteinathome.org/workunit/85212429
RE: Not an error exactly
[Marked url as such]
When your wingman times out, a new one will be assigned automatically. You just have to have some patience.
Rob
RE: RE: Not an error
Ok thank you, its an old rev and quite large. I read other posts that some in that series have been a problem was all.
(Wingman, Heh i like that :) )
tnx
http://einstein.phys.uwm.edu/
http://einsteinathome.org/workunit/84037019
Can someone please tell me why this unit has not been sent back out to more pc's? My pc is the one pc that finished the unit, 2 other people did not and yet it has not been sent back out to anyone else yet!
Another Validate
Another Validate error:
http://einsteinathome.org/workunit/86007343
Claggy
Tnx Rob, it took 2 wingmen to
Tnx Rob, it took 2 wingmen to process it but it did clear. It was passed on after 2 other wingmen gave up on it i think. lol.. anyway all is well and thank you.
(It did take alot of proc. time so mabey they dident want to wait that long?)
So far all units have passed here FYI
RE: http://einstein.phys.uw
There were a couple of workunits (ABP, around Oct 1) we need to mess around with manually, which could have had bad side effects on the "transition time" (next time the transitioner will look at them and may e.g. generate more tasks to be sent). In case of this workunit it was set to Nov 28th, at which time the problem should have cleared itself.
I now manually reset the transition time for this workunit, an a new task to be sent out was generated. Unfortunately I can't think of a way to automatically detect all such workunits that are stuck for a while and reset the transition time, normally we would simply have to wait.
BM
BM