Hello Gus, To investigate a bit I would like to know if you can copy/paste: -your command line -the full log (In a text file, or on pastebin)
What version of OTB, and what OS do you have? Thanks, Rémi Le samedi 8 septembre 2018 18:07:56 UTC+2, Gus a écrit : > > Thanks, Rémi > > Your method works fairly well, the results are really good and visually > pleasant. In fact, I was able to use you app (from gui) for small subsets > of my data, which is a set of aerial pictures of the sea surface from which > the sunglint has been removed. > > [image: 2dc4d9d7-25da-4254-9cb5-31536801f461.jpg][image: > 54ed0802-e492-438f-9f4d-8dea3593a2b6.jpg] > > But, when I feed your program with the complete set (about 2500 pictures, > 30 Mb each approximately, 8 bit colour) it fails. Last thing I can check is > that the temporary distance maps have been correctly written, and that's > the last console output. while if Iskip the large feathering step, it seems > to work ok, as in next image using slim blending mode, but as for large > blending, it fails... > > [image: sea_1PNG.PNG] > > On Saturday, September 8, 2018 at 10:57:53 AM UTC+2, Rémi wrote: >> >> Hello Gus, >> >> The RAM parameter deals only with the memory footprint during mosaic >> compositing and statistics computation, both streamable pipelines (no >> limitation on images size). >> However, the distance map calculation (which is a temporary file, then >> used as an input of the streamed mosaicing compositing pipeline, just for >> feathering) is not a streamable process. Meaning that, for each input image >> to mosaic, the distance map will theoretically require the full image in >> memory to be processed. That's why there is the distancemap.sr (sampling >> ratio) parameter. This enables the subsampling of the input image, to >> compute the distance map with a smaller footprint. See README.md, section >> "Performance tuning: Distance map images sampling ratio". >> This is a current limitation of the application, I will add this >> explicitly in the application description. >> >> Your problem could also come from the fact that your input images have >> not the same projection reference (and leading to a near infinite image, >> e.g. if you mix degrees and meters units, or with wrong coordinate >> reference system), check this. >> >> Hope that helps, >> >> Rémi >> >> Le vendredi 7 septembre 2018 01:44:23 UTC+2, Gus a écrit : >>> >>> >>> Hello everyone. >>> >>> I don't clearly understand the process followed by the remote module >>> "mosaic". The memory occupied during some phase after distance maps >>> calculation for large blending with lab color space harmonization grows a >>> lot, so I obtain a huge page file and my computer reboots. I checked the >>> paper and peeked into the code a bit, but I'm not familiar with the >>> libraries. Is there any way of estimating the ram needed for the process? >>> Is there a way of overcoming this issue? (probably I will process it in >>> chunks anyway but that would simplify things quite a lot). >>> >>> Cheers >>> >>> Gus >>> >> -- -- Check the OTB FAQ at http://www.orfeo-toolbox.org/FAQ.html You received this message because you are subscribed to the Google Groups "otb-users" group. To post to this group, send email to otb-users@googlegroups.com To unsubscribe from this group, send email to otb-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/otb-users?hl=en --- You received this message because you are subscribed to the Google Groups "otb-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to otb-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
