[hugin-ptx] Re: 2015.0 rc2 released

[Stefan Peter]

Am Sonntag, 5. Juli 2015 14:00:11 UTC+2 schrieb T. Modes:
>
> Hi all,
>
> Today we are releasing release candidate 2 of Hugin 2015.0
>
>
Hi All

Please find packages of hugin 2015.0 rc2 for Ubuntu 14.04 (Trusty),
14.10 (Utopic), 15.04 (Vivid) and 15.10 (Wily) in the Hugin PPA
Packagers "next Hugin Build" 
athttps://launchpad.net/~hugin/+archive/ubuntu/next/+packages 


As always these packages are based on the Debian PhotoTools Maintainers
work, namely Andreas Metzler: Thank you guys!

Installation instructions:
Open a terminal window and issue the following command:

sudo add-apt-repository ppa:hugin/next

The title of the PPA and the key used to sign it will be displayed. You
will have to confirm the inclusion of this PPA to the package sources of
you system by pressing enter.

Afterward, you can update you system using the commands

sudo apt-get update
sudo apt-get upgrade

or whatever other method you prefer to update your system.

The same is explained athttps://launchpad.net/~hugin/+archive/ubuntu/next/ 

when you click 'Read about installing' under the title "Adding this PPA
to your system"


As a side note, I recommend to add the "latest Hugin builds" PPA at the
same time because there you will eventually get the final release. The
command for this PPA is:

sudo add-apt-repository ppa:hugin/hugin-builds

If you run into a show stopper and need to go back to your old hugin
version, issue these commands in a terminal window:

sudo apt-get purge hugin
sudo add-apt-repository -r ppa:hugin/next
sudo apt-get install hugin


Please send bug reports to this list or 
usehttps://bugs.launchpad.net/hugin/+filebug
to report a bug.

Thank you very much for your participation.

Cheers

Stefan Peter


-- 
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/bc3ece33-0ea9-430a-a418-6c81c22e7fdb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[hugin-ptx] Re: Different approach from attempt to stitch (super-resolution?) night sky (late 2014)

[Matthew Petroff]

I would recommend looking at Astrometry.net [1], which does blind 
astrometric calibration of images of the night sky. This give you FITS 
World Coordinate System metadata for the images [2] that maps image pixels 
to celestial coordinates. However, it does have some issues with fisheye 
lenses, although there seem to be workarounds [3].

-Matthew

[1] http://astrometry.net/use.html
[2] http://fits.gsfc.nasa.gov/fits_wcs.html
[3] https://groups.google.com/forum/#!topic/astrometry/RumO4M7an0E

On Saturday, July 4, 2015 at 1:56:25 PM UTC-4, Benjamin Hill wrote:
>
> Super-resolution from highly overlapping photos seems hard.  Maybe 
> impossible?
>
> I have taken a series of night-sky images from a fixed camera over a 
> period of several hours.  I identified keypoints (stars) in the images, and 
> correlated the keypoints across frames.  This results in a file of ~1000 
> rows of 4 ints:
> int FRAME_A, int STAR_B, int PIXEL_X, int PIXEL_Y (and timestamp of the 
> frame if it would be helpful)
>
> The challenge is that it was taken with a wide-angle lens, and I don't 
> know the exact distortion parameters of the lens.  
>
> Goal: use the input file to either determine the lens model, or another 
> mathematical model (machine learning?), that will allow a very precise 
> function that maps a "true" night sky location to the coordinates in every 
> frame that covers that part of the sky.  It is ok if the model takes a long 
> time to train, but the final lookup should be fast.
>
> getAllOverlappingExactSourceLocations(x1, y1) -> 
> array of frames [{source_frame:frame_a, source_pixel_x:(float)x, 
> source_pixel_y:(float)y}, {source_frame:...]
>
> This may be easier to think of in the inverse: given a panoramic landscape 
> shot taken with a slowly moving motorized camera, and choosing any ray from 
> the camera's location, get the intersections with that ray and all the 
> photos that overlap that ray.
>
>
> It feels like this should be easy using Hugin or PTGUI: At the end of the 
> day, I've got very accurate keypoints, and I *should* be able to get an 
> accurate lens model from them... right?  And once I have an accurate lens 
> model, I should be able to get each frame's yaw/pitch/roll with sub-pixel 
> accuracy.  And then I... er... need help.  How do I use this model + a 
> frame's yaw/pitch/roll to get source pixel locations for the final frame, 
> that is pretty much what the final stitcher is doing, true?  So I'd need to 
> reimplement my own emblend?  Any easier way?
>

-- 
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/790aaa45-51b1-4dbb-9b2f-40086ab404c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.