Hmm, give that link another try -- I haven't used google drive in that way, and I think I needed to change the access so anyone with the link can get it.
Answering your final question -- yes, full sky replacement will replace all pixels that are likely to be sky. Internally, a very sophisticated model of the sky has been built. It is usually a very, very good model in simple situations like this example. But even the best model will not be good enough to prevent a noticeable edge at repair points, unless some sort of blending is employed. Full sky replacement gets around this problem by replacing all pixels -- that are determined to be likely sky pixels. By replacing all likely sky pixels, no spatial blending is required. Full sky replacement uses probability of sky as a blending function at the pixel level. Something like: sky_prob = a value from 0 to 1. It is how close the pixel color is to the modelled sky color at that x,y location. It is a nonlinear function. final_pixel_color = (1.-sky_prob)*original_pixel_color + (sky_prob)*modelled_sky_color On Saturday, March 5, 2022 at 8:30:15 AM UTC-8 [email protected] wrote: > Thankyou. > > On Saturday, March 5, 2022 at 11:01:24 AM UTC-5 [email protected] wrote: > >> >> https://drive.google.com/drive/folders/1ds5QHI4qNYqXOLNexS0Ov6Ll14HnhkSV?usp=sharing >> >> Hopefully you can see those files. >> > > Not yet. I clicked on the "request access" button. > > >> I retract my advice to use darktable's retouch tool -- there is a lot >> of sensor dust. >> > > You are right. I thought I had used masks and the overlap between images > to get rid of most of that. But I did something wrong and lots ended up in > the panorama. > > >> I used the full sky replacement option (-fsr), which basically examines >> every pixel in the detected sky and assigns a probability that the pixel >> should be considered true sky. If the probability is large enough it will >> be overwritten -- so magically all the sensor dust disappears. That one >> spot near the horizon on the right where there is a black mask leaves some >> artifacts, because of some feathering at the edge of the mask where pixels >> were not completely black. >> > > I still haven't found time to figure out where the black came from or > where the feathering of the black came from. None of that was in the > original images. That should have been just another gap in the final image. > >> >> I will better document the -fsr option in the next tutorial for skyfill. >> > > Does it replace all of the sky that was already good? Or does it detect > what should be sky but isn't? > >> >> -- 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/224f01cb-8c00-4458-9590-9148861c1b3bn%40googlegroups.com.
