Manual adjustment for incorrectly preprocessed corner marks (Feature #390)

Added by Stefan Reinsberg about 9 years ago. Updated about 9 years ago.

Status:New Start date:11/03/2015
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:-
Target version:-

Description

Could you lay out what would need to happen to implement a manual correction of the preprocessing step:
I somehow don't seem to be able to get my students not to draw in the corners and hence they upset the recognition of the corner marks. I have tried pleading and threats but they really like to scribble there.

I am hoping I could develop an interactive method to adjust the corner positions. I imagine this would have to happen at the stage where one reviews the improperly recognized scans. A window pops up and shows the preprocessing results and reveals if the square made up by the four corner marks is, in fact, not square. After the manual intervention one would have to reinitiate the running of the recognition and page mark reading as well.

I can probably find where the relevant code is but is there some ideal approach to this?

History

#1
Updated by Alexis Bienvenüe about 9 years ago

I somehow don't seem to be able to get my students not to draw in the corners

I have no such problems. I charge the students 20% of the points for manual data capture if the problem comes from them, and this seems to be effective.

I am hoping I could develop an interactive method to adjust the corner positions.

That would be great!

How I would imagine it:
  • add some options to AMC-analyse to skip corner marks detection and give corner marks positions manually.
  • from the unrecognized scans window (opened with the Data capture/Diagnosis/Look at scans button), add a button to open another modal window to set and edit the 4 (only 3 may also work, but is less precise) corner marks centers (with a circle-shaped pointer that has approximately the same size as the corner marks), and then process again the scan calling AMC-analyse this new options.
  • after this processing, update the window and list of the unrecognized scans window (maybe the scan is again unrecognized, but pre-processing is different. Maybe the scan is now well-recognized so we have to remove it from the list and go to the next one).

#2
Updated by Alexis Bienvenüe about 9 years ago

  • Tracker changed from Bug to Feature

Also available in: Atom PDF