Recognize error : empty alternatives in CSV

[pgaleas]

Hi,

I'm newbie with SDAPS. I define a latex based examination with 24 questions (choicequestion and textbox). I only got some warnings during the recognize process (see below), but some of the choicequestions had empty (cero) response in the CSV export, although they are clearly marked in the TIFF file.

Is it possible that the warnings are the source of the defective response?

`------------------------------------------------------------------------------

- SDAPS -- recognize

36 hojas WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 WARNING: /build/buildd/zbar-0.10+doc/zbar/decoder/code128.c:335: postprocess: Assertion "dcode->buf[dcode128->character - 1] == STOP_REV" failed. dir=1 buf[0007]=69 22 21 64 17 52 35 |################################################################| 100% 00:01:39 2.767788 segundos por hoja `

[benzea]

Nah, those warnings are harmless.

Maybe you are confusing the "fill to uncheck" option or the marking is simply rather thick?

[pgaleas]

Hi Benjamin, thank you for the swift response. I didn't change anything about the checkbox metrics in the configuration, so I think that I'm using the default option (checkcorrect). As you can see HERE, the marks in the exams seems to be OK.

Or not?

Best regards

[fndercole]

Hi, open GUI and verify if those pages are tagged as 'valid', if not indicate the page number and check the boxes manually. See http://sdaps.org/Documentation/GUI

Best

[pgaleas]

Hi fndercole, I verified the pages with the GUI as you recommended (see attachments). But I don't understand why in the same question block identical marks are in some cases not recognized (see question 2.3) Any idea?

[fndercole]

Hi, I don't know how sdaps do the heuristics (i'm only a user), but notice that this 'unrecognised' marks have a red square. Probably there's a way to change some parameter to force to tag as recognised.

Based on my experience, This behaviour is more frequent when the printing has poor quality, or when the marks are too heavy. If you are designing exams or quizzes for student or untrained respondent, then is convenient to set the font size to 12pt or larger, so squares has more white space and the recognition works better.

I can see that you understand spanish, so this is a fragment for the manual that I wrote for interviewers,

Bests

[pgaleas]

Favio, thank you very much for the information. I will test the next exams with a larger font set, and probably also include your text fragment with the exam instructions.

Best regards

[benzea]

Hmm, I think that those checkboxes should work fine. I would say we need to modify the thresholds, this looks way too aggressive in recognizing corrections.

[benzea]

The red outline means that the checkbox is considered a "bad" recognition which should be verified by a human.