hugin_executor scripting fails to find remapped image

[tduell]

Testing hugin-2015.1.0 hugin_executor scripting, using the supplied "normal_enblend.executor" script, which fails due to enblend looking for %prefix%0000.TIF, but %prefix%0000.tif has been generated, script output as follows...

Stitching using "Normal panorama with enblend"

Remapping images

Blending with enblend
enblend: failed to open "hgex0000.TIF": No such file or directory

The file hgex0000.tif exists in the project dir.

I also note that hugin_executor requires the full pathname for the script file. I have packaged the supplied script files in /usr/share/hugin/data/ (Fedora 22) which, I think, has been the preferred dir but hugin is not looking here for executor scripts. Is the requirement for full pathname for the script the expected behaviour?

Cheers,
Terry

[tduell (tduell-iinet)]

OK, a bit of further testing illuminates the first issue (enblend: failed to open "hgex0000.TIF": No such file or directory).
Editing the supplied 'normal_enblend.executor' script to ...

[General]
Description=Normal panorama with enblend
StepCount=3
IntermediateImageType=tif

solves the problem, when using linux.

Cheers,
Terry

[tmodes (tmodes)]

Thanks for finding.
Fixed in changeset 6c690feb9965. I also updated the documentation for the executor file format.

[tmodes (tmodes)]

Hi Terry,

concerning the full path: yes, it is intended.

1.) When using from the GUI the file selection dialog should start in in data directory or in the last used directory for executor files. So in this case the full path has no disadvantage.
2.) Command line usage: here the advance user has to specify the full path. Or he is even using an own executor file, which can be in the same folder as the image file. Then he can specify this file.

[tmodes (tmodes)]

Hi Terry,

I thought about this and added in changeset cd6b614aa1b1 a fallback. It looks now first in the current path. If no matching file is found and no path specified it looks also in the data dir for the executor file.

[tduell (tduell-iinet)]

Hello Thomas,
I think that is a good solution.
Thanks.

Cheers,
Terry