El lunes, 28 de junio de 2021 a las 21:37:44 UTC+2, [email protected] escribió:
> On Mon, 28 Jun 2021 at 12:08, Álvaro Huertas <[email protected]> > wrote: > > > > thanks you so much for the response! > > > > I tried your tips but with no results, hugin still modifying pixels in > the false color panorama. Since I'm working without interface (i'm > scripting in python through CLI commands) I found some issues: > > > > - Once I import any photo Er and Eb photometric parameters are set to 1 > automatically. If I try to set it up to 0 with pto_var then nona throw the > following exception: > > Sorry my mistake, yes the Er and Eb parameters should be set to 1. If > you are doing all this outside the Hugin GUI, then probably you only > need to reset the Ev photometric parameters. > > > - I'm using the nona '--seam=hard' option in the CLI so I think tip nº2 > its working fine. > > > > - About the interpolator choice: I can't select the interpolator in CLI > command of nona: > > The interpolator is set in the 'i' parameter of the 'm' line in the > PTO file, so you need to edit the line that looks something like this: > > m g1 i0 f0 m2 p0.00784314 > > ..and change i0 to i6 > > (the format is described in the nona.txt file: > https://sourceforge.net/p/hugin/hugin/ci/default/tree/doc/nona.txt ) > > > Even if I do this step in interface, pixels still beeing modified (maybe > because of the issue with step 1). > > -- > Bruno > > -- > Bruno Hi Bruno! I made a script to modify 'm' line for setting a custom interpolator and now I'm getting better results. The stitching is now working with an acceptable precision. I notified a odd behaviour in the treatment of the pixels by Hugin. I made a script to check if there is any modified pixel against the color palette I'm using and I've found that each stitching is modifying 1 to 5% of the total pixels of the panorama. No problem with this percentage of failure but the odd is that all of this pixels are the same hues: [image: 1.JPG] All pixels with 111 green channel are being modified! The 97649 pixels correspond to the same hue. I think Hugin is modifying the following pixels of the color palette: [image: 2.JPG] So *pixels in the second image are being turned to pixels in the first image* (RGB pixels). I don't know what is going on since the rest of the pixels in the image are being unmodified. Even with this affordable percentage of failure I think this issue can be solved easily or maybe there is something going wrong with Hugin functionality in this particular value. Thanks you so much Bruno! -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/f18dafeb-ad01-487e-bef8-76c6f12f3ce1n%40googlegroups.com.
