The warning is benign. It is not related to the size of a panorama, but to the location of the tentative seam-line after Simulated Annealing.
Use `--visualize' to check if there is a connection between the seam line and the supposed artifacts. For a more detailed look at the optimizer's job try `--parameter=debug-path'. You will want to divert this output to a log-file. Probably any of the optimizers' (S/A and Dijkstra) parameters that can be set at the Enblend commandline may influence the occurrence of the warning. So, you could run some experiments along this line, too. If you really want to jump into the source, "postoptimizer.h" and "path.h" are your starting points. Though I doubt whether one can improve on the situation, I'll be happy to accept your patches. TIA! ** Changed in: enblend Status: New => Opinion ** Changed in: enblend Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Enblend. https://bugs.launchpad.net/bugs/1633354 Title: "enblend: warning: unable to run Dijkstra optimizer" for large panorama Status in Enblend: Opinion Bug description: Reported for Hugin on Windows (32-bit version of Hugin): https://bugs.launchpad.net/hugin/+bug/1633352 I suspect it's an enblend bug. I'm no expert on enblend, so I could use some help how to diagnose, isolate and fix the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/enblend/+bug/1633354/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp