@mauricetoet,

I am working on your data and I am testing a new algorithm. But, I clearly see some problems with the data, probably arising due to applying “dynamic distortion correction” already on the single panel integrations.

There are 2  workflows, that will probably give better results. Can you try any of these 2 if you have spare time, or…[Read more]

@mauricetoet,

I am working on the registration engine.

In the next version you can now select the scale on which pattern recognition is done.

For regular (not mosaic) stacks, only scales of  1-5 are needed to get optimal registration.

Internally, I had this fixed to scales of 1 to 8.

For the mosaicing, it will be much more efficient to use…[Read more]

Yeah, you’re right. I was exploring to many settings at a time.

It would be great if you can find a problem and fix it. 7% overlap is indeed pretty low though.

@mauricetoet, I am studying your data.

First of all, I again notice an instability in the complex model, which causes it to run for quite some time. This is the complex model for

– Multiple View, not”same camera and optics” with “dynamic distortion correction” on

This is fixed, now.

Secondly, I have lokated the two problem panels. I notice…[Read more]

What would be the minimum required overlap as a %-age of frame width/height?

I would say, that APP needs about 10% of frame width/height for most cases but it strongly depends on several factors.

– the amount of detected stars at the borders of the frames, the more stars detected, the less % it needs.

– the pattern recognition engine creates…[Read more]

Too little overlap between the panels might cause the issue. “Hollandse zuinigheid” ;-) I’ll send you all (6) panels.

Hi @mauricetoet,

Looks like this seam has very little overlap for the two adjacent frames. This could be the reason this seam isn’t registered like it should. You could try triangles instead of the quadrilaterals for this in the pattern recognition, but registering the mosaic while take quite a bit longer.

I think I need an addition in the…[Read more]

Thank you very much @bula. I did some further experimenting with your suggested settings, especially for analysing stars (3). Still need to tweak / further experiment with the settings. Whats happens is that at one of the seams I get double stars; see attachment. In the end I cheated and mixed two versions (with double stars at different postions)…[Read more]

Hi @mauricetoet,

I would recommend for the mosaic registration to use:

4) Register

use “dynamic distortion correction”

disable “same camera and optics” (the panels were created by APP, so APP is the camera now, and this camera normally is slightly different for all panels)

mosaic mode

( 5) normalize, you can experiment with advanced…[Read more]

I’m experimenting to get a properly aligned (registered) mosaic in APP version 1.037. Still some minor flaws, though. Maybe they’re caused by edge of field distortions (coma, miscollimation).

@bula: what settings do you recommend under 4) register & 6) integrate?

Technical details:
6 pane mosaic with Tak Epsilon-180ED, Atik 11000. Data acquired…[Read more]

Great @mauricetoet, let me know if you need assistance with the mosaic integration in any way ;-)

Thank you, Mabula. As soon as time permits, I’ll continue working on the mosaic with the latest beta version of APP.

Hi @mauricetoet,

I have found the cause of this regression instability and I have fixed this for both settings (on/off) of “same camera and optics” while using “dynamic distortion correction”.St-avg-7200.0s-NR-x_1.0_LZ3-full-eq-add-sc_BWMV_nor-AA-RL-noMBB-St

Hi @mauricetoet,

The error is fixed, from all available frames left, APP will automatically choose a new reference frame using the frame quality estimate after star analysis.

I have also checked if all goes well if you were to start 5) Normalize after having removed the reference after 4) Register. This is working without problems as well.

For…[Read more]

@mauricetoet,

I can replicate the sphere as well, it happens with the following registration settings:

– “same camera and optics” on and “dynamic distortion correction” on

If I turn “”same camera and optics”  off, the result is even worse. (first image)

I’ll try to isolate the cause to fix this exception. This dataset clearly triggers…[Read more]

Hi @mauricetoet,

Indeed, I can confirm that the error is the deletion of the reference frame. I’ll fix this!

Mabula

Indeed, excellent @mauricetoet ;-)

You can either do:

[light – n * dark] / [m * (flat – masterbias)]

or

[(light – masterbias) – n * (dark – masterbias)] / [m * (flat – masterbias)]

where:

n * dark = a masterdark with the bias offset
n * (dark – masterbias) = a masterdark without the bias offset

I was just typing my previous message when you replied. So yes, I can confirm it happens after enabling dynamic distortion correction. I’ll send you the data set so you can test it.

This sphere issue occurs after enabling “use dynamic distortion correction”. I’ll check what happens with the next set of data (3rd panel of the mosaic).