This year we have some additions this year - in case there are students
interested in projecting on large 3D displays.
<http://panospace.wordpress.com/2009/03/19/bliss-and-a-lot-of-work-coming-up/>
prokoudine wrote:
> Feel free to tell us about your own ideas and don't hesitate to send
> us patches to tell us you are serious about participating ;-) I'm
> pretty sure that Yuv will write a separate mail with all the fine
> details the we he always does as soon as he's back from his short
> trip.
tonight I'm quite tired. Baby, wife, parents are all asleep, and it
won't be long until I follow.
> Let's rock again!
This will be another great summer!
Yuv
Congratulations that Panotools did it again and well I'm interested in taking part of GSoC 2009 and I would like to work again with FreePV, I want to make its integration with VLC this summer. Two months ago I was checking VLC code and I just compiled it from source code... not big deal... but I tried to understand the code and it will be a challenge for me... I think I should apply to both organizations, but probably in this case a mentor familiarized with VLC would be more helpful... anyway I hope to get a slot this summer.
1. Making deghosting act more like as a library. This probably would
ease integration to enfuse. The second part would be adding algorithm
described in [1] or adding support for deghosting to enfuse. The
problem of this is that I think I'd not be able to do the math of the
algorithm without help (there are some things I've never seen before).
If I would decide to integrate it to enfuse instead of implementing
mentioned algorihtm the problem would be in fact that both khan and
this algorithm are intended for use with HDR.
Anyway, even if I would choose one of these goals I'd like to
implement also the second one but I think it would be quite
problematic to do the both during summer so the second one wouldn't
have so high priority.
2. Add support for selecting different projections for parts of
images. This would need to calculate some function which would make
transition between parts with different projections smooth. I thing
that it could be done by selecting some discrete points from functions
describing both projections and then describe them by using bezier
curves. The problems are that I don't have any idea how the
projections are described so this approach may be impossible and (it
may be a bigger problem) that I would have to create some GUI for it
(I don't know creating GUI using wxWidgets and overall I hate creating
any GUI).
[1] http://www.ee.oulu.fi/mvg/files/pdf/cpgr_paper-1.pdf
Lukáš Jirkovský
Ok, I wrote something on the wiki:
http://wiki.panotools.org/SoC_2009_idea#Simple_mask_editing
Everyone else, now is a good time to mention all those good ideas
for hugin features.
--
Bruno
I have added this to the list of projects. this should be done
primarily in panotools.
I think that it is highly related to allowing shift in the camera's location,
so those two projects should be combined.
I am probably the potential mentor for this (panotools particularly).
--
--dmg
---
Daniel M. German
http://turingmachine.org
Please, the first act should be reorganization of knowledge and concepts.
It is 3 years I'm lost to hugin, I've no clue on how to do things out of
basic ones cause I can't access knowledge base on my own...
I hope I'm not the only one, cause means my stupidity is growing with age.
dmg ha scritto:
--
IUAV università degli studi, Venezia
Dr. Luca Vascon
tel . (+39) 041.2571262, e-mail vas...@iuav.it
laboratorio multimedia Facoltà di Design e Arti, DADI
Magazzino 7 ex Ligabue, Dorsoduro 1827 30123 Venezia
> Date: Sun, 22 Mar 2009 17:07:18 +0100
> From: vas...@iuav.it> Subject: [hugin-ptx] Re: GSoC2009
>
>> Please, I think the BASIC thing hugin needs is an updated website.
> The first problem is that when somebody wants to install it, even on
> windows, he steps on old unupdated versions, when luckyly find the
> compiled exes.
> Ubuntu debian self installing thing seems old.
> It completely lacks clear instructions on how to install what.
> Never seen the new updated interface. Does it exist?
> How is integration of old things?
>
> Please, the first act should be reorganization of knowledge and concepts.
> It is 3 years I'm lost to hugin, I've no clue on how to do things out of
> basic ones cause I can't access knowledge base on my own...
> I hope I'm not the only one, cause means my stupidity is growing with age.
When you say that "masking to put one object in-front of another is
never going to be done in hugin, this is a job for an image
editor" ... I'm thinking that this would actually be a great feature
to be included in hugin, because it would allow to do everything
(quickly) in pre-processing instead of post-processing, and still have
the benefit of the blending step.
Just to make sure we are talking about the same thing, I understand
this "mask editing" topic is all (and only) about what should be
included or not included in image seams.
Now maybe I'm missing something, but if the steps performed once you
press the "stitch now" button are:
- remapping images
- remapping masks
- applying masks to remapped images
- blending masked remapped images
.. then for the two cases you mentioned:
1. masking out objects that you don't want to appear in the scene.
=> the mask is applied to one image only (the one from which you want
to mask out the objects)
2. masking to put one object in-front of another.
=> the mask is applied to all images but one (the one from which you
want to keep the objects)
Cheers,
Adrien
When you say that "masking to put one object in-front of another is
never going to be done in hugin, this is a job for an image
editor" ... I'm thinking that this would actually be a great feature
to be included in hugin, because it would allow to do everything
(quickly) in pre-processing instead of post-processing, and still have
the benefit of the blending step.
Just to make sure we are talking about the same thing, I understand
this topic is all about what should be included or not included in
image seams.
Now maybe I'm missing something, but if the steps performed once you
press the "stitch now" button are :
- remapping images
- remapping masks
- applying masks to remapped images
- blending remapped images
... then for the two cases you mentioned :
1. masking out objects that you don't want to appear in the scene.
=> the mask is applied to one image only (the one from which you want
to mask out the objects)
2. masking to put one object in-front of another.
=> the mask is applied to all images but one (the one from which you
want to keep the objects)
Cheers,
Adrien
On Mar 19, 8:13 pm, Bruno Postle <br...@postle.net> wrote:
I'm a Msc CS student in the inter disciplinary center in Herzliya,
Israel.
My main interests are image processing, 2nd graphics and computational
photography.
from the short description in the GSoC site about this project it
seems that I will be able to contribute to it, and would actually be
happy to do so :)
unfortunately I cannot see the wiki of the project since it has been
down for almost all day long, and cannot see what are the suggested
projects Ideas.
are the projects that you are looking for are mainly environment (like
phyton bindings etc,) and gui, or are you interested in students to
implement all kinds of advanced computational algorithms?
Thank you!
Irena
The ubuntu instructions are really for people who _want_ to compile
their own. The way it should work for everyone else is that the
distribution provides the binaries - i.e. hugin is part of ubuntu
and you don't need to download anything from the hugin website.
This situation isn't how it should be, we need more regular releases
of hugin and related tools, and Linux distributions should be
prompted to fix the stuff they do supply.
--
Bruno
Currently masks are applied in three possible ways:
1. the Crop tab lets you exclude edge areas, these pixels are simply
not sampled when remapping.
2. alpha channels in source photos are remapped in exactly the same
way as RGB colour channels, which leads to:
3. 100% transparent alpha channels in remapped images are treated as
hard image boundaries by enblend.
Note that enblend merges images by taking the entire overlap area
and feathering it (in a clever multiresolution way). This only
works when the overlap has a significant width and the two images
are similar.
>.. then for the two cases you mentioned:
>1. masking out objects that you don't want to appear in the scene.
>=> the mask is applied to one image only (the one from which you want
>to mask out the objects)
>2. masking to put one object in-front of another.
>=> the mask is applied to all images but one (the one from which you
>want to keep the objects)
Yes this works for forcing parts of images into the output, see the
'process-masks' tool in Panotools::Script for a way of doing this
with the current enblend and three different levels of alpha channel.
The problem with putting one object in front of another is that you
need an abrupt transition, the 'feather' between pictures is only a
pixel or two wide, not something enblend can do.
--
Bruno
Lukáš Jirkovský wrote:
> Hello,
> I'd really want to participate, but I've not yet decided what should
> be my application. think about two things:
>
> 1. Making deghosting act more like as a library. This probably would
> ease integration to enfuse. The second part would be adding algorithm
> described in [1] or adding support for deghosting to enfuse. The
> problem of this is that I think I'd not be able to do the math of the
> algorithm without help (there are some things I've never seen before).
While I won't be able to be a full time mentor this year, I'd be more
than happy to answer your questions about the algorithm in [1]. Don't
let the formulas scare you. From a quick look it seems to work quite
similar to the khan deghosting (whose paper also sounds more complicated
than it really is), but contains additional steps to further improve the
results.
> If I would decide to integrate it to enfuse instead of implementing
> mentioned algorihtm the problem would be in fact that both khan and
> this algorithm are intended for use with HDR.
Actually, both algorithms produce a weight values for each pixel in each
exposure. This weight value could be combined with the weight enfuse
computes for each pixel.
> Anyway, even if I would choose one of these goals I'd like to
> implement also the second one but I think it would be quite
> problematic to do the both during summer so the second one wouldn't
> have so high priority.
I don't think doing both is possible in a summer, especially when time
for learning how the algorithms really work is also needed.
ciao
Pablo
Dev Ghosh schrieb:
> Hello,
>
> I'd like to solve the problems I'm encountering as part of Summer of
> Code. Specifically, I'd like to introduce a mosaic mode to Hugin. This
> will require the development of the geometric framework to project from
> the mosaic image viewpoints to that of an orthographic view of the
> entire painting. I propose calculating the warp using a homography,
> applying the calculated mapping, and projecting the result to the
> orthographic viewpoint. A homography estimation algorithm developed in
> C by Lourakis will provide the required homography matrix calculations.
While the homest package by Lourakis is a nice piece of work, I think
that it would be better to stick with the physical model that panotools
uses, as that also handle lens distortions properly and would allow
using fisheye and cylindrical cameras, too. This would mean that one
"just" needs to implement the right transformation functions, and reuse
the exiting optimisation algorithms.
The only problem is that all current panotools transformations have not
been build with moving viewpoints in mind, so the panotools projections
code would probably need some reorganisation/rewrite to allow this cleanly.
Having a mode for properly mosaicing planar scenes would be an extremly
welcome addition to hugin.
ciao
Pablo
Irena wrote:
> unfortunately I cannot see the wiki of the project since it has been
> down for almost all day long, and cannot see what are the suggested
> projects Ideas.
it is currently quite slow here too, but it loads
<http://wiki.panotools.org/SoC_2009_idea>
> are the projects that you are looking for are mainly environment (like
> phyton bindings etc,) and gui, or are you interested in students to
> implement all kinds of advanced computational algorithms?
both. it depends on your interests and skill.
For a starter, may I suggest that you go about building and hacking
hugin and related tools?
<http://wiki.panotools.org/Development_of_Open_Source_tools>
Yuv
no need to be apologetic. We do not ignore potential contributors. We
also don't harass them. I won't grab you out of the dark corner you're
putting yourself in. I'll wait patiently for you to come out of there
and will welcome you to our community if you want to join.
There are plenty of interesting projects and capable mentors waiting for
you. But the application deadline is April 3. And you need a working set
of tools, as described in the wiki.
Don't make your life hard. Grab a simple Ubuntu or Windows, set yourself
up with the tools and let the fun begin.
Yuv