Discussion Thread for the Continuous GW Search known as O2MD1 (now O2MDF - GPUs only)
Language
Copyright © 2024 Einstein@Home. All rights reserved.
Copyright © 2024 Einstein@Home. All rights reserved.
This validate error problem
)
This validate error problem probably will keep Bernd busy when he goes to work Monday.
I'm also getting a bunch of
)
I'm also getting a bunch of validate errors, on my 2 hosts:
https://einsteinathome.org/host/12256783
https://einsteinathome.org/host/7330531
I'm very interested to know if these "invalid" results, might be due to an OpenCL problem in NVIDIA drivers versions 436.02 through 440.97.
We are currently tracking that issue, for some of SETI's OpenCL tasks, here:
https://setiathome.berkeley.edu/forum_thread.php?id=84694
https://setiathome.berkeley.edu/forum_thread.php?id=84780
Thoughts?
I don't think so in my
)
I don't think so in my case.
NVIDIA GeForce GTX 1060 3GB (3072MB) driver: 425.31
Jacob Klein
)
I've got a bunch of validate errors with AMD cards too. I don't think it could be solely a problem with Nvidia driver here at Einstein.
Probably just the way the
)
Probably just the way the task parameters were configured. Something is not quite right with the 2.02 app.
Okay. Thanks for replying,
)
Okay. Thanks for replying, fellow crunchers.
The same thing for v2.02 -
)
The same thing: v2.02 - only pending and validate errors, no valids.
The reason for the validate
)
The reason for the validate error issue and that it is now fixed has been announced in the Tech News thread.
Cheers,
Gary.
I've just checked the two
)
I've just checked the two hosts that I have running the V2.02 test app. I had suspended crunching of GW work on them (and allowed some FGRPB1G work) when the validate error problem was discovered. At that time there were a couple of validate errors and no valid results for GW tasks on each one.
When the small batch of FGRPB1G tasks finished on each, the GW work was restarted and at the present time (and just for the V2.02 app) one host has 8 valid, 41 pending and 1 validate error whilst the other has 9 valid, 46 pending and 0 validate errors. Everything looks pretty good. No invalid results on either machine.
It can probably be assumed that batches of validate error results, perhaps based on particular frequency bins are being fed back into the 'corrected' validator and so it will probably take some time for all these different frequencies to be processed fully. As far as I can see, the validate error problem is disappearing pretty fast.
Cheers,
Gary.
Three of these today from one
)
Three of these today from one host:
Outcome:Computation error Client state:Compute error Exit status:114 (0x00000072) Unknown error code
The target internal file identifier is incorrect. (0x72) - exit code 114 (0x72)</message>
https://einsteinathome.org/task/893410246 https://einsteinathome.org/task/893410247 https://einsteinathome.org/task/893441228
2 run less than a minute and 1 run more than two hours.