Moved from the other thread: T.Modes* "But you repeat often the same phrases: assumes options or implies options means in this context that the corresponding option *[was?] *automatically activated/set and does not need to *[be?] *set manually."*
That's because you haven't clearly explained them before. Those phrases are *meaningless* on their own. I continue to ask for the documentation to be clarified so that anyone else reading it will be clear about what is meant - without having to discover and read through this whole thread. There might be exceptions, but English usually needs an explanatory phrase after "assumes" or "implies", or it doesn't make sense. Certainly in this case they do. For example Implies *that* x *has been done*. Assumes *that* z *will be done*. In fact I can't see how either "implies" or "assumes" can be used in this context. Alternatively "This option will also set/activate/turn-on X" uses simple English and the meaning is quite clear. Why are you reluctant to alter the original phrases? Were they written by someone with high status within the Panotools heirarchy who you do not wish to offend by criticising his/her English? I saw mention on one documentation page of an author with a name that suggested that he was a French speaker, and you are a German speaker. With respect, as a native speaker of English, I think my grasp of the English language is naturally going to be deeper than yours. I have no axes to grind over this, I just wish to make this amazing software more accessible to ordinary users by ensuring that its functions are clearly exlained. On Wednesday, April 17, 2024 at 7:16:09 AM UTC+1 Chris wrote: > This comes from the other thread as it probably belongs here: > > > > *-S Assume stereo images - allow horizontal shift of control points. Adds > all control points as "horizontal lines".-A Align stereo window - assumes > -S. Adds one "normal" control point that is the nearest point, so that > everything will appear behind the display plane.-P Align stereo window with > pop-out effect - assumes -S. Adds one "normal" control point that is the > nearest point from the border areas, so that the center of the image may > appear in front of the display plane.* > > The language is a little ambiguous here - “assumes -S “ Does this mean > > - “Assumes you have also used the –-S parameter?” If not what would > happen? > > Or > > - “This will also set/activate/turn-on the -S option.” > > On Saturday, April 13, 2024 at 9:53:47 AM UTC+1 Chris wrote: > >> *--align-to-first* >> >> …This *implies* also the --use-given-order option. >> >> To me as a native English speaker this is ambiguous but probably means: >> >> “*This means **you **must **also use **the **–use-given-order **option* >> *.”* >> >> If so, what would happen if you hadn’t? >> >> But I suspect the intended meaning might have been >> >> “*This also set**s**/activate**s**/turn**s**-on the --use-given-order >> option.”* >> >> Looks like an option best avoided due to uncertainty about what it does. >> >> ------------------------------------------------ >> >> *--**distortion* Hopefully if there is no distortion information or it’s >> invalid, this process is not performed – rather than the program going into >> an endless loop or aborting. >> >> I won’t use this option as I don’t want to risk the program hanging or >> aborting. >> >> ------------------------------------------------ >> >> *-g gsize* >> >> Break image into a rectangular grid (gsize x gsize) and attempt to find >> *num* control points in each section (default: 5 [5x5 grid+) >> >> Should I assume that the value of *num* comes from *-c num *if that >> option is used, otherwise it is the default of *8* mentioned under -*c?* >> >> I won’t use this option as I don’t want to risk the program hanging or >> aborting if my assumptions about *num* are incorrect. >> >> ------------------------------------------------ >> >> *Optimisation phase* >> >> I assume x means adjustment along the horizontal pitch axis, y to >> adjustment on the vertical yaw axis and z to adjustment on the “out of the >> window” roll axis. >> >> Shouldn’t it be “Optimize *correction** of *radial distortion”? >> >> ------------------------------------------------ >> >> *--**gpu *Since there is no information about what might happen if the >> GPU was unsuitable or missing (I have a GPU so can’t test that), I won’t >> use this option as I don’t want to risk the program hanging or aborting. >> That's it with the questions :)/ >> >> On Thursday, April 11, 2024 at 6:41:37 PM UTC+1 T. Modes wrote: >> >>> Chris schrieb am Donnerstag, 11. April 2024 um 10:20:43 UTC+2: >>> >>> *Great! The webpage is far more informative now, putting it into >>> sections helps a lot. * >>> >>> I’m only interested in 3D image processing, but I’ve had a look at all >>> the options in case they might be relevant and I hope my further questions >>> might help someone else. I'll look at the 3D ones later. >>> >>> >>> *--align-to-first* >>> >>> *...This implies also the --use-given-order option. * >>> >>> The -use-given-order is automatically activated. (But adding it manually >>> makes no difference.) >>> >>> *-f HFOV* *...use if EXIF info not complete* >>> >>> >>> If neither is available what happens? >>> >>> It will use a sensible default value - see output of the program. >>> >>> *-l* *Assume linear input files are in linera colour space.* >>> >>> Is the default gamma colour space? >>> >>> Yes. >>> >>> >>> *Optimisation phase* >>> >>> How do “(yaw, pitch and roll) “ relate to x, y,z? >>> >>> They all together describe the position and direction of the camera in >>> space. >>> See coordinate system of panotools. >>> >>> *-**m -d -i -x -y -z **Optimize field of view* >>> >>> I assume one might as well always set all of -m -d -i -x -y -z in order >>> to optimise everything . >>> >>> No, that' s totally wrong. The more parameter you try to optimize the >>> more precise and better distributed control points you need. >>> Especially optimization of x/y/z can often be fragile and should only be >>> added when really needed. >>> Instead of the command line the best would be to start with the pto file >>> and optimize then in the GUI. First start with only the basic parameters >>> and then add one parameter after the other and after each optimization run >>> check the result in the preview window. >>> >>> >> -- 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 hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/882ad5b3-8df8-424a-b5a9-44f4b59ed9b5n%40googlegroups.com.
