Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - RickS

Pages: [1] 2 3 ... 83
1
Are you sure it's the .xdrz files that can't be found?  The .xdrz files reference the original data files prior to registration.  If you have deleted these files then you will get errors.

Cheers,
Rick.

2
General / Re: Help me understand overscan coordinates
« on: 2019 February 09 18:37:12 »
I didn't realize the overscan calibration needed to be done on each individual sub prior to combining for the masters

Glad you figured it out.

3
Gallery / Re: Gum15 aka RCW32
« on: 2019 February 09 13:50:01 »
Well captured and processed, Geoff!

4
General / Re: So I bought it :)
« on: 2019 February 09 13:45:48 »
I had a similar experience some years ago.  I watched the Harry's Astroshed videos and in less than a day I was getting better results than ever before.  It wasn't difficult at all.  Since then I have learned a lot and realised that my early images were pretty terrible but that's not the fault of PixInsight :)  Welcome to the club.

Cheers,
Rick.

5
General / Re: Help me understand overscan coordinates
« on: 2019 February 09 13:39:25 »
Nothing stands out that I can see.  My KAF-16803 camera has an overscan area to the right of the image and the parameters are:

Image region:0 0 4096 4096
Source: 4107 0 9 4096
Target: 0 0 4096 4096

So long as all frames are captured with overscan enabled everything just works as expected.

6
General / Re: LRGB vs RGB (again again ,) )
« on: 2019 February 09 13:18:12 »
Have you tried making L, R, G and B masters the normal way and then combining them with ImageIntegration? (no rejection.)

7
Hi Kevin, I only ever calculate SFS weights on unregistered subs on the basis that the interpolation done by registration is going to reduce the accuracy of FWHM calculations.  I haven't noticed any problems with noise evaluation in ImageIntegration being confused by rough edges but I have never looked closely at this.

Cheers,
Rick.

8
Whether there is a significant advantage depends on what you're trying to accomplish.  If you want optimal SNR then ImageIntegration noise weighting will provide that.  You can manage FWHM, Eccentricity, etc. to a limited degree by deciding which subs to include and exclude.  If you want greater control over the balance of SNR with other quality metrics then SFS weighting will allow you to achieve that.

You can't really do any harm by trying different options.  I normally do a simple noise weighted integration as well as at least one SFS weighted version.  I compare the results (also with SFS) and pick the version that gives me what I consider the best compromise.  Sometimes I'll do further tweaking of the weighting expression and/or make changes to the subs that I include in the integration.  I may even combine multiple integrations with PixelMath, e.g. blending the bright parts of a high FWHM integration and the dim areas of a maximum SNR integration.

Data is precious and hard to come by.  IMO, it's worth putting some effort into the preprocessing stage to maximize the value of what you have.

Cheers,
Rick.

9
Wish List / Re: Sensible presets for subframe selector
« on: 2019 January 31 16:31:38 »
The SubframeSelector process already supports min, max and other variables computed from the data.  Try FWHMMin, FWHMMax, FWHMSigma for example.

10
Are you bias calibrating the dark frames?  CMOS cameras like the ASI1600mm do weird stuff with short subs.  You may find that a very short bias frame has higher values than a longer dark frame.  This can cause the error you are seeing...

Cheers,
Rick.

11
New Scripts and Modules / Re: Debug Environment for Scripts?
« on: 2019 January 28 23:03:42 »
Console.writeln debug messages are good enough for me.  IMO, sophisticated debuggers just encourage tinkering instead of thinking about the problem :)

12
Tips & Tricks / Re: Incompatible image geometry
« on: 2019 January 27 02:19:43 »
Hi Bryan,

Without more details it's hard to hazard a guess as to what is going wrong but there are three things which determine the geometry of a sub - the width (pixels), height (pixels) and depth (number of channels.) I'd be checking to make sure that the bias, darks and flats are all compatible.

Cheers,
Rick.

13
General / Re: M42 - Processing Light Subs of Different Length
« on: 2019 January 27 00:09:15 »
Integrate as separate stacks and combine with HDRComposition.

14
Bug Reports / Re: error in subframe selector
« on: 2019 January 23 14:48:17 »
You have to uninstall the old version and then install the new one.

15
Bug Reports / Re: error in subframe selector
« on: 2019 January 10 01:45:32 »
There are several threads about this already.  It's a known intermittent problem and will be fixed in a new release coming soon...

Pages: [1] 2 3 ... 83