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 - mmnb

Pages: [1] 2 3 ... 5
Lately I've found it pretty easy to create starmasks with MLT (I used to have a really hard time with the star mask tool, trying to get the noise threshold just right). My typical workflow has been to create a small star mask with MLT, a big star mask with range selection, take the max of those to make a final star mask.  I then take the lightness channel, lo pass filter it, stretch, paint out rings from bright stars and then subtract the star mask to make the nebulosity mask.  In some nebulas I will use the red channel instead of lightness to get a better nebula "shape".

This linear M17 image (Hyperstar C14, EOS 60Da ~20 exposures) has been processed up to PCC. I am having a lot of trouble getting a good starmask....making the threshold low picks up nebulosity (there are some really bright regions in there....I am honestly not sure if they are poorly resolved stars?).  Is the right solution to clone paint that stuff away?  Or am I just not making star masks competently?

Catalina 10.15.1
Late 2013 macbook

*** PCL Unix Signal Handler: Critical signal caught (11): Segmentation violation

PixInsight 1.8.8-3 - Critical Signal Backtrace
Received signal 11 (SIGSEGV)
Module: 0   PixInsight                          0x0000000107edff4e InitializePixInsightModule + 1849342
 45: 1   libsystem_platform.dylib            0x00007fff63e4fb1d _sigtramp + 29
 44: 2   ???                                 0x0000000000000a80 0x0 + 2688
 43: 3   PixInsight                          0x0000000107ca21a2 PixInsight + 14520738
 42: 4   QtWidgets                           0x0000000110b7d979 _ZN7QWidget5eventEP6QEvent + 1161
 41: 5   QtWidgets                           0x0000000110b42c20 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 272
 40: 6   QtWidgets                           0x0000000110b43fd5 _ZN12QApplication6notifyEP7QObjectP6QEvent + 581
 39: 7   PixInsight                          0x00000001070010e4 PixInsight + 1278180
 38: 8   QtCore                              0x0000000111a82094 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent + 212
 37: 9   QtWidgets                           0x0000000110b7c71d _ZN14QWidgetPrivate11show_helperEv + 413
 36: 10  QtWidgets                           0x0000000110b7d32c _ZN14QWidgetPrivate10setVisibleEb + 828
 35: 11  PixInsight                          0x00000001072e7a0b PixInsight + 4319755
 34: 12  PixInsight                          0x00000001072e8e9b PixInsight + 4325019
 33: 13  QtWidgets                           0x0000000110b7d896 _ZN7QWidget5eventEP6QEvent + 934
 32: 14  QtWidgets                           0x0000000110b42c20 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 272
 31: 15  QtWidgets                           0x0000000110b43fd5 _ZN12QApplication6notifyEP7QObjectP6QEvent + 581
 30: 16  PixInsight                          0x00000001070010e4 PixInsight + 1278180
 29: 17  QtCore                              0x0000000111a82094 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent + 212
 28: 18  QtWidgets                           0x0000000110b4274a _ZN19QApplicationPrivate18dispatchEnterLeaveEP7QWidgetS1_RK7QPointF + 1674
 27: 19  QtWidgets                           0x0000000110b43501 _ZN19QApplicationPrivate14sendMouseEventEP7QWidgetP11QMouseEventS1_S1_PS1_R8QPointerIS0_Ebb + 833
 26: 20  QtWidgets                           0x0000000110b9c91f _ZN14QDesktopWidget11qt_metacallEN11QMetaObject4CallEiPPv + 9087
 25: 21  QtWidgets                           0x0000000110b9b66a _ZN14QDesktopWidget11qt_metacallEN11QMetaObject4CallEiPPv + 4298
 24: 22  QtWidgets                           0x0000000110b42c20 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 272
 23: 23  QtWidgets                           0x0000000110b43fd5 _ZN12QApplication6notifyEP7QObjectP6QEvent + 581
 22: 24  PixInsight                          0x00000001070010e4 PixInsight + 1278180
 21: 25  QtCore                              0x0000000111a82094 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent + 212
 20: 26  QtGui                               0x000000011113ae61 _ZN22QGuiApplicationPrivate17processMouseEventEPN29QWindowSystemInterfacePrivate10MouseEventE + 3441
 19: 27  QtGui                               0x00000001111224bb _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop

PCL and PJSR Development / Telea inpainting
« on: 2019 December 05 21:27:04 »
Coming back from  J-P Metsavainio's talk at AIC, I really liked the idea of separating stars and working on nebulosity.  Adam Block was also talking about his star shrinking method which involves removing stars and then MMT to "inpaint".

I was just playing with OpenCV's inpainting using PI to create the star subtracted image and star mask (created with MLT and some dilation):

It seems that opencv's Telea method does a pretty good job (takes a ridiculously long time though, several hours on my pokey 2015 mac airbook for a 2x drizzled image (originally 10k x 7k pixels) .  Nothing great about the m31 image (just the last thing I took/processed), but the star traces seem a touch better with open cv...I think the larger stars need masks that are a bit bigger (they leave bigger traces in the bg).   I'm no expert here, just wondering if anyone might be interested in having this in PI.  Masking the bigger stars with bigger masks for inpainting would improve thing a bit more I think.

(big pngs)

Starnet (default params):

OpenCV inpaint:

EDIT: zooming in, Telea sure does leave very "radial' patterns....from far away, the filled in patterns look lower contrast to me though...

Gallery / m33
« on: 2019 November 22 23:09:17 »
EOS 60Da + C14 EdgeHD

Would love any critical comments.

General / filtering with MLT vs. starmask
« on: 2019 November 18 21:57:00 »
I've always really been struggling with StarMask, trying to tweak it exactly to not pick up too much noise, checking the mask over my image to make sure I am getting all the stars, trying to get the ones in front nebulosity etc. 

Adam Block demo'd his star removal technique and starts my constructing a star mask with MLT by simply removing the residual and the very smallest scale components.  Am I missing something or is this straightforward filtering this way much easier?  I just tried it and it seems that I got much better quality star mask with no effort relative to using the StarMask process.

I feel a little silly for such a simple question, but is there something that I am missing? Do others prefer making their star mask one way or the other?

Bug Reports / pixel trails that follow cursor?
« on: 2019 September 01 23:14:37 »
I have PI running on a newer MacBook Air (just fine) and an older MacBook Pro where I am running into an odd problem:

I've adjusted the UI settings a bit for accessibility and see rather annoying pixel trails that follow the mouse cursor on images (they disappear after a bit).  I don't see anything similar in the forum.  Some machine info:

15 inch (Late 2013)
Mojave 10.14.6
PixInsight Core

Image Processing Challenges / Re: m8 lagoon nebula
« on: 2019 August 14 18:04:49 »
Increased saturation a little.
EDIT: Added exp stretch to brighten a bit.

Image Processing Challenges / m8 lagoon nebula
« on: 2019 August 14 17:04:08 »
C14+hyperstar+ EOS 60Da

Found my darks before I thought I could get a hold of them and indeed including them in the calibration (as recommended here: by bulrichl) really did seem to make the thin dark lines disappear (that wasn't going away, despite dithering). I'll try to post some controlled comparisons on that since there seems to be some varying advice o how to deal with Canon dark current suppression.

Nothing fancy:
Up to PCC
Deconvolution (still hard to see the effects here, very easy to overdo)
Denoising dark
Sharpening nebulosity
Star shrinking (while linear, very light)
arcsinh stretch (I liked this stretch better than the masked stretch as I seemed to be getting smaller stars and better color although the outer nebulosity was dimmer)
HDMRT (no mask, brought out the internal dark areas to look more like masked stretch)
Small L and Sat curve adjustment.

Lots of nice images out there but it seems to be in the right ballpark but would love to hear any criticism.

XISF up to PCC:

Image Processing Challenges / Re: m106
« on: 2019 August 09 16:13:56 »
I certainly will try your suggestions when I get the chance but it will be a few weeks.

Image Processing Challenges / Re: m106
« on: 2019 August 09 13:18:01 »
No need to take offense. I've tried understanding appropriate handling for these Canon cameras and a few credible sources suggest not bothering with darks.

Just to put the main conflicting source inline:
"This, along with the dark current suppression built into the hardware, removes the need for dark frames."

I have no doubt your guide describes the *correct* way to handle dark frames for calibration, but it isn't clear to me that they are *needed*. What I am trying to reconcile across sources is "is the effect of dark frame calibration clear and visible?". I don't see the answer to that in your guide, perhaps I have missed it.

Image Processing Challenges / Re: m106
« on: 2019 August 09 01:32:44 »
To be sure, this is my current pre processing after noticing the dark current is suppressed in the Canon EOS 60Da:

Biases/Flats saved in 'RAW Monochrome' readout setting in maximDL.

Creation of master bias (using super bias).

In batch preprocessing (IIRC it won't run if you try using flats without bias or dark), supply the flats (not as master) and master bias with the lights and debayer here as well.

I believe this should be fine no (no dark frames, but biases needed to divide by flat)? This correction seems ok by eye.

Image Processing Challenges / Re: m106
« on: 2019 August 08 05:23:41 »
Indeed, this was something like 30x30s exposures with dithering.  Thanks for all the cannon specific advice.

EDIT: Should add that calibration is done without darks due to the way cannon works with 'dark suppression'.

Image Processing Challenges / m106
« on: 2019 August 07 13:39:33 »
C14 Edge HD + Hyperstar + EOS 60Da

Standard preprocessing up to deconvolution, masked stretch then HDRMT (masked to galaxies) and some saturation and curve nudging.  There is a line that shows up in the bottom 6th in all my frames, not sure what the cause is there; I might try and kicking it out in cosmetic correction.   Is collimation/focus error obvious here in the cropped frame (I can see the chromatic aberration in the stars when working on the image)?  I'm trying figure out to get it fixed, right now it seems that the error is position dependent.

EDIT: Link to xsif, linear image processed upto PCC:

Gallery / Re: North America Nebula Region
« on: 2019 July 29 21:51:31 »
Very nice!
Do you mind elaborating on reasoning behind to the two background reduction steps? I always only do 'subtract', now I've only just  heard of  Carlos' method (which I can't actually find now) where he does some sort of linearization of the bg model and then only subtraction.

Gallery / Re: ngc4236 C14 hyperstar + EOS 60Da
« on: 2019 July 24 11:26:08 »
Can you clarify? This image was processed only with pixinsight.
EDIT: Ah I suppose there was another piece of free software involved in the very last step in terms of cropping and curve adjustment.  These were very very trivial changes (easily done in PI) and only mentioned for accuracy.

Pages: [1] 2 3 ... 5