Why does Hugin's command-line stitching fail with a missing celeste.model file and invalid HFOV?
Asked 1/22/2012
61 views
2 answers
0
I'm trying to stitch a panorama with Hugin from the command line. I created control points with autopano-sift-c, then ran celeste_standalone -i project.pto -o project.pto, but I get: Couldn't open SVM model file celeste.model.
I also see an HFOV value is invalid error when running autooptimiser.
What causes these errors, and how can I fix them when using Hugin's command-line tools?
Originally by Photography Stack Exchange contributor. Source · Licensed CC BY-SA 4.0
Photography Stack Exchange contributor
14y ago
2 Answers
5
The command line you typed for celeste should work. What I would look into next is:
- Confirm that the file celeste.model is in the same folder as celeste_standalone.exe
- Look from what path you are calling it, and possibly adding the hugin\bin folder in the path for your command line 'SET PATH=%PATH%;c:\huginFolder\bin' Having it in the bin saved me from trouble a few times.
As for the HFOV value is invalid, your command line seems ok. Here is one I know works 'autooptimiser.exe -a -o "output.pto" "input.pto"'
Can you add more info, specifically the first few lines of your input PTO file, something like:
p f2 w3000 h1500 v360 n"JPEG q90"
m g1 i0
i w3168 h4752 f0 a0 b-0.01 c0 d0 e0 p0 r0 v180 y0 u10 n"IMG_2415.tif"
i w3168 h4752 f0 a=0 b=0 c=0 d0 e0 p0 r0 v=0 y0 u10 n"IMG_2416.tif"
Originally by user5782. Source · Licensed CC BY-SA 4.0
user5782
14y ago
0
Generated from our catalog & community — verify before relying on it.
The celeste.model error usually means celeste_standalone can’t find its required model file. Make sure celeste.model is installed where Hugin expects it, commonly alongside celeste_standalone.exe or in Hugin’s data path, and run the command from a shell where Hugin’s bin folder is on your PATH.
For example, adding the Hugin bin directory to PATH often fixes missing-file issues.
The HFOV value is invalid message is less likely to be caused by your autooptimiser command itself. A simpler command such as:
autooptimiser -a -o output.pto input.pto
should work if the input .pto file is valid.
That error usually points to a problem in the generated PTO file, especially the panorama/header lines or image entries where the field of view (v) should be defined correctly. Check the first few lines of project.pto and confirm the images and panorama settings were written properly by the earlier step.
In short: fix the celeste.model search path first, then inspect the PTO file if autooptimiser still reports invalid HFOV.
Recommended products
UniqueBot
AI14y ago
Your Answer
Related Questions
No related questions yet.