Some "not so important" observations, requests...
- AMC-regroupe has no man file. May I know what this command is for? Do you want me to write man file for this?
- AMC-annotate command uses "--project" for project directory but says "--projet" in man file. Correct?
- For AMC-annotate "--symbols 0-0:none,0-1:circle:red,1-0:mark:red,1-1:mark:blue" is a valid option, right?
But did not work. (AMC:1.2.2016.011501, all my comments)
- For AMC-* commands, when you give "--debug file.log", it does not work (may be it works, but puts file.log in /tmp/?).
However, "--debug ./file.log" puts the log file in current working directory.
Do the AMC-* commands religiously use current working directory? Should one give full path to files and directories when using AMC-* commands?
- For AMC-* commands, do you need to give trailing / like: "--scans scans/" or "--scans scans" is ok.
- Similar question as above for other commands which use files...
- Is the following too much trouble: Put into the log file the complete AMC-* command with all options used when you click a gui button
like Detect Layouts or Print Pages etc. That way some one who wants to use command-line AMC just has to see the log file and cut and paste!
- When AMC is used with photocopied subject: I see one severe restriction that the page has to be only one per student.
Do you like the proposal (I am sure many would have suggested): When scans are in pdf or any other multi-page format,
then pages 1, 2, ...k, will be treated as from one copy, pages k+1, k+2,....2k will be treated as from second copy etc.
Thanks for your feedback!
AMC-regroupeis deprecated, and left in the sources for backward compatibility only. The job is now done by
--projectis the right one. I corrected the man page.
AMC-gui) instead of
0-1:circle:red(man page). I don't know why, but changed this so that it accepts both conventions.
7. I think this is the case. You can look for
Command lines, folowed by
Unpacked args:, like in
[ 31821, 10.19] Command  : auto-multiple-choice annotate --xmlargs /tmp/AMC-PACK-0T5L33Yj.xml [ 31821, 10.19] Create progression pipe for <> up to 0 (progress bar side) [ 31875, 0.50] >> [ 31875, 0.50] Unpacked args: --cr /home/alexis/Projets-QCM/test-prerempli/cr --project /home/alexis/Projets-QCM/test-prerempli/ --projects /home/alexis/Projets-QCM/ --data /home/alexis/Projets-QCM/test-prerempli/data --subject /home/alexis/Projets-QCM/test-prerempli/DOC-sujet.pdf --corrected /home/alexis/Projets-QCM/test-prerempli/DOC-indiv-solution.pdf --filename-model --no-force-ascii --single-output --sort n --id-file /home/alexis/Projets-QCM/test-prerempli/selected-ids --debug /tmp/AMC-DEBUG-j3uOgFXy.log --progression-id annotate --progression 1 --line-width 2 --font-name Linux Libertine O 12 --symbols 0-0:none/#000000000000,0-1:circle/#ffff00000000,1-0:mark/#ffff00000000,1-1:mark/#00000000ffff --no-indicatives --position case --dist-to-box 5.5 --n-digits 4 --verdict Nom : %(nom) %(name)
The 'unpacked args' are those which have been passed to the command inside the
xmlfile given with
Thank you, Alexis for your answers.
I have uploaded a "user-friendly" front to AMC-* commands at the end of Using AMC in command line only
Dunno how useful it would be.
- what if two pages go together in the scanner feeder?
- what if a page is not well recognized by AMC?
- what if all subjects or answer sheets don't have the same number of pages?
You will have to spend some time to double-check that all went OK, and this seems very frustrating for me as in standard mode all is very smooth and robust.