PToptimizer dies on being fed a Hugin PTO file
Feed a Hugin PTO file to PToptimizer and it will choke on the 'p' line (E/R/S parameters) and on the 'i' lines (Eev parameter).
I have not tested if other parameters are affected as well.
At the minimum it would be nice if the parser could at least extract the information it needs while abstracting from the extra / redundant information; and assume that the specs are being expanded.
Better would be if the two sets of tools (Hugin and Panotools) could share (again?) a common specification and maybe even a common extension-proof parser and bring back together the dialect scripts that have grown apart.