[Hugin-devs] [Bug 1633352] Re: "enblend: warning: unable to run Dijkstra optimizer" for large panorama
** Changed in: hugin Status: New => Invalid -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1633352 Title: "enblend: warning: unable to run Dijkstra optimizer" for large panorama Status in Hugin: Invalid Bug description: I have a panorama with 14 TIFF images with 16 bit per color (in summary about 200 megapixel). The images fit rather nicely and there is no warning before conversion. But when converting these warnings appear: enblend: info: loading next image: 2749-27620005.tif 1/1 enblend: warning: unable to run Dijkstra optimizer enblend: note: seam-line end point outside of cost-image enblend: note: contour #2 of 2, segment #1 of 1, vertex #2716 of 2717 enblend: info: loading next image: 2749-27620006.tif 1/1 It's hard to find out from these texts where the actual problem is and how to fix it. I have a slight suspect that the 32-bit version might have a memory problem with such a huge (28152x3284) panorama. Up to recently I was running the 64-bit version of the 2015 edition, and I never saw such problems before, but I use 16-bit TIFF as source rather rarely. Anyway: In the resulting panorama you can clearly see two artefacts; one at the to of the panorama, the other one at the bottom. I'm attaching the relevant part of the preview to relate the position of the artefact to the images. I extracted a part of the resulting panorama, scaled it down, and I'm attaching it as part of the data for this bug. Unfortunately the material is too huge for an attaching. I tried to make a smaller test case using JPEG images, but the the problem did not exist. When trying 16bit TIFFs that were downscaled, the problem even occurred twice (using a different set of control points). To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1633352/+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
[Hugin-devs] [Bug 1633354] Re: "enblend: warning: unable to run Dijkstra optimizer" for large panorama
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
[Hugin-devs] [Bug 1633352] Re: "enblend: warning: unable to run Dijkstra optimizer" for large panorama
I also posted a bug report for enblend: https://bugs.launchpad.net/enblend/+bug/1633354 -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1633352 Title: "enblend: warning: unable to run Dijkstra optimizer" for large panorama Status in Hugin: New Bug description: I have a panorama with 14 TIFF images with 16 bit per color (in summary about 200 megapixel). The images fit rather nicely and there is no warning before conversion. But when converting these warnings appear: enblend: info: loading next image: 2749-27620005.tif 1/1 enblend: warning: unable to run Dijkstra optimizer enblend: note: seam-line end point outside of cost-image enblend: note: contour #2 of 2, segment #1 of 1, vertex #2716 of 2717 enblend: info: loading next image: 2749-27620006.tif 1/1 It's hard to find out from these texts where the actual problem is and how to fix it. I have a slight suspect that the 32-bit version might have a memory problem with such a huge (28152x3284) panorama. Up to recently I was running the 64-bit version of the 2015 edition, and I never saw such problems before, but I use 16-bit TIFF as source rather rarely. Anyway: In the resulting panorama you can clearly see two artefacts; one at the to of the panorama, the other one at the bottom. I'm attaching the relevant part of the preview to relate the position of the artefact to the images. I extracted a part of the resulting panorama, scaled it down, and I'm attaching it as part of the data for this bug. Unfortunately the material is too huge for an attaching. I tried to make a smaller test case using JPEG images, but the the problem did not exist. When trying 16bit TIFFs that were downscaled, the problem even occurred twice (using a different set of control points). To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1633352/+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
[Hugin-devs] [Bug 1633354] [NEW] "enblend: warning: unable to run Dijkstra optimizer" for large panorama
Public bug reported: 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. ** Affects: enblend Importance: Undecided Status: New -- 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: New 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
[Hugin-devs] [Bug 1633352] [NEW] "enblend: warning: unable to run Dijkstra optimizer" for large panorama
Public bug reported: I have a panorama with 14 TIFF images with 16 bit per color (in summary about 200 megapixel). The images fit rather nicely and there is no warning before conversion. But when converting these warnings appear: enblend: info: loading next image: 2749-27620005.tif 1/1 enblend: warning: unable to run Dijkstra optimizer enblend: note: seam-line end point outside of cost-image enblend: note: contour #2 of 2, segment #1 of 1, vertex #2716 of 2717 enblend: info: loading next image: 2749-27620006.tif 1/1 It's hard to find out from these texts where the actual problem is and how to fix it. I have a slight suspect that the 32-bit version might have a memory problem with such a huge (28152x3284) panorama. Up to recently I was running the 64-bit version of the 2015 edition, and I never saw such problems before, but I use 16-bit TIFF as source rather rarely. Anyway: In the resulting panorama you can clearly see two artefacts; one at the to of the panorama, the other one at the bottom. I'm attaching the relevant part of the preview to relate the position of the artefact to the images. I extracted a part of the resulting panorama, scaled it down, and I'm attaching it as part of the data for this bug. Unfortunately the material is too huge for an attaching. I tried to make a smaller test case using JPEG images, but the the problem did not exist. When trying 16bit TIFFs that were downscaled, the problem even occurred twice (using a different set of control points). ** Affects: hugin Importance: Undecided Status: New ** Tags: enblend ** Attachment added: "ZIP archive with project file, artefact image, log file, preview" https://bugs.launchpad.net/bugs/1633352/+attachment/4760776/+files/2749-2762-bug.zip -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/1633352 Title: "enblend: warning: unable to run Dijkstra optimizer" for large panorama Status in Hugin: New Bug description: I have a panorama with 14 TIFF images with 16 bit per color (in summary about 200 megapixel). The images fit rather nicely and there is no warning before conversion. But when converting these warnings appear: enblend: info: loading next image: 2749-27620005.tif 1/1 enblend: warning: unable to run Dijkstra optimizer enblend: note: seam-line end point outside of cost-image enblend: note: contour #2 of 2, segment #1 of 1, vertex #2716 of 2717 enblend: info: loading next image: 2749-27620006.tif 1/1 It's hard to find out from these texts where the actual problem is and how to fix it. I have a slight suspect that the 32-bit version might have a memory problem with such a huge (28152x3284) panorama. Up to recently I was running the 64-bit version of the 2015 edition, and I never saw such problems before, but I use 16-bit TIFF as source rather rarely. Anyway: In the resulting panorama you can clearly see two artefacts; one at the to of the panorama, the other one at the bottom. I'm attaching the relevant part of the preview to relate the position of the artefact to the images. I extracted a part of the resulting panorama, scaled it down, and I'm attaching it as part of the data for this bug. Unfortunately the material is too huge for an attaching. I tried to make a smaller test case using JPEG images, but the the problem did not exist. When trying 16bit TIFFs that were downscaled, the problem even occurred twice (using a different set of control points). To manage notifications about this bug go to: https://bugs.launchpad.net/hugin/+bug/1633352/+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
