On Monday, January 31, 2022 at 5:35:33 PM UTC-5 bruno...@gmail.com wrote:
>
> If not, then send me your sourceforge username. Note that sourceforge
> supports a fork/pull-request workflow (similar to github), so you can
> work on a separate personal repository just as easily as the main
>
On Monday, January 31, 2022 at 5:06:20 PM UTC-5 bruno...@gmail.com wrote:
> See the ptomorph proof of concept from ten(!) years ago here:
> https://groups.google.com/g/hugin-ptx/c/UripOuuYXCQ?pli=1
>
> This works incredibly well, with no need for low-priority control
> points, but I never
Hi John, I'm just catching up on my email, do you have access to the
Hugin repository yet?
If not, then send me your sourceforge username. Note that sourceforge
supports a fork/pull-request workflow (similar to github), so you can
work on a separate personal repository just as easily as the main
See the ptomorph proof of concept from ten(!) years ago here:
https://groups.google.com/g/hugin-ptx/c/UripOuuYXCQ?pli=1
This works incredibly well, with no need for low-priority control
points, but I never pursued it, and it needs some thought regarding
getting it to work with more than two
The most important use case for this idea would also depend on support for
low priority control points, which IIUC is in a fork of Hugin that I
haven't had time to look at yet.
Assume that control points are very accurately placed, but still don't
optimize very well. So the remapped images