"TASKS FOR COMPUTER 13078400" (Sent 13 May 2023) Not Correct

CElliott
CElliott
Joined: 9 Feb 05
Posts: 28
Credit: 989299960
RAC: 163316
Topic 229517

I am trying to determine the source of the validation errors for the MeerKat workunits processed on a new computer with an AMD Ryzen 7 5800X 8-core CPU and Windows 11 Pro (version 13.2.0, 64-bit).  The system has two AMD Radeon R9 R390 series video cards, and all WUs were processed on them.

There were 125 workunits (WUs) sent to computer 13078400 on May 13, 2023.  The header on page "TASKS FOR COMPUTER 13078400" says In Progress (0), Pending (46), Valid (124).  However, paging through the Pending entries discloses 49 WUs sent 13 May 2023 listed.  Paging through the Valid entries sent 13 May gives 76 WUs, which is correct.

Paging through the All column, reveals 125 WUs sent 13 May 2023, which is correct.  Valid WUs are 76 (correct), 46 WUs are waiting for validation, and 3 WUs for which validation is inconclusive.  Hence the Pending header, which says only 46 WUs, is off by the 3 inconclusive validations.

Scrooge McDuck
Scrooge McDuck
Joined: 2 May 07
Posts: 1035
Credit: 17687943
RAC: 12702

I think your observation is

I think your observation is correct. The "pending" tasks didn't contain the inconclusive ones. They are somehow "hidden" and can only be listed within the "all" tasks column. Thereby the task count is 'wrong' by the number of inconclusives.

Gary Roberts
Gary Roberts
Moderator
Joined: 9 Feb 05
Posts: 5870
Credit: 116938015249
RAC: 36694381

CElliott wrote:...  Hence the

CElliott wrote:
...  Hence the Pending header, which says only 46 WUs, is off by the 3 inconclusive validations

You need to think of "Pending" as describing tasks yet to be presented to any validation check at all.  In other words, a pending task doesn't yet have a returned companion task.

There really should be a separate category for tasks that do have a companion but the two don't agree closely enough to be declared valid.  That condition is correctly described in the full list of tasks as "Completed, validation inconclusive".  So, for those dissecting their results on the website, it would be useful to have an extra label in the page header for "Inconclusive" results to go with the other categories.

This extra category has been requested from time to time over many years but has never been implemented at Einstein.  You have to calculate it manually if you want to know 'how many'.  Just use the formula:-

Inconclusive = All - (In_Progress + Pending + Valid + Invalid + Error)

I'm monitoring a couple of my hosts at the moment (running FGRPB1G tasks) that seemed to be getting quite a few inconclusives.  Here are the current values (collected earlier this morning) for one of them:-

All=1478  In_Progress=225  Pending=301  Valid=932  Invalid=4  Error=0

So that machine has 16 inconclusive results, waiting for a further validation attempt.  My concern was to make sure the machine wasn't putting out 'bad' results.  The data shows (and has done so for the last week while I've been monitoring) that most of the inconclusives do turn into valid results.  I feel reasonably confident that my machine is OK, particularly since the ratio of invalid to valid is so low.

Cheers,
Gary.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.