http://albert.phys.uwm.edu/results.php?userid=43613&offset=0&show_names=0&state=4&appid=
I have a lot of wu's that show 'validation error' or 'can't validate'.
It's not on one machine only, so there seems to be a problem with the app.
If this helps the project and the app can be improved I will continue, otherwise it's a waste af time and power.
So I would really appreciate to get an answer.

---

http://albert.phys.uwm.edu/results.php?userid=43613&offset=0&show_names=0&state=4&appid=

You can't use a link to your results like this because only you have permission to access your own account. You need to select the host showing the problem and then link to the results for that host - like this. Note that all of these results are for the S6LV1 app currently being tested. There is an active thread in the news section for this app and if you read there you can see others reporting similar problems. You should join the discussion there.

I have a lot of wu's that show 'validation error' or 'can't validate'.
It's not on one machine only, so there seems to be a problem with the app.

In the above link for your host (id=1767), you can see the bottom set of results were for the previous app v1.02. I guess when the problem with that app was identified, the outstanding tasks for that version were all pulled, causing the "can't validate" message. There is obviously a validation problem showing up with the new version so you should expect further announcements from Bernd - probably in the other thread.

If this helps the project and the app can be improved I will continue, otherwise it's a waste af time and power.

Of course it helps the project by having a small, select group of volunteers discover the problems before inflicting them on the whole community. That latter scenario would really be a waste of time and power!! It also helps the time strapped Devs if the volunteers can keep up with the active thread. Welcome to the joys of alpha testing :-). We were all fully warned :-).

By participating this way, you are performing a valuable (and much appreciated) service. I hope you will continue helping. As problems continue to get solved, new app versions may be released at any time. If that happens and you are paying attention, you can limit the waste on your machines by simply aborting all remaining tasks for the deprecated version and replacing them with 'new version' tasks. You can also limit the waste by keeping your cache of work on hand quite small.

Thanks for your continuing support.

---

Cheers,
Gary.

Gary, are you shure that everything runs correct here?
The validation errors decreased, but ...

State: All (81) | In progress (3) | Pending (36) | Valid (11) | Invalid (2) | Error (29)
Application: All (81) | Binary Radio Pulsar Search (14) | Gravitational Wave S6 LineVeto search (67)

now most of them are reported as errors.

---

Gary, are you shure that everything runs correct here?

I can't find where I said that!! :-).

In fact, quite the opposite. I said there was obviously a problem with the 1.02 LV1 app and that there now seemed to be an issue with the 1.03 version as well. I also tried to explain the reason for "can't validate" that you saw with your 1.02 LV1 tasks.

I wouldn't say everything runs correct here. I would say that things are likely to fall over from time to time - exactly what you should expect from an alpha test project.

For example, take a look at this quorum in which your host is participating. Forgetting about the errors, there are already 3 successfully completed tasks which can't seem to agree with each other and so there is now a new task to try to break the deadlock. This is exactly the sort of information the Devs need to work out the bugs. Even though you seem to regard it as a waste, you are performing a valuable service and I'm sure it's necessary and appreciated.

---

Cheers,
Gary.