Finished: Integrated Flux Nebula Image

Here's the image at quarter-scale:

1/4 Scale Image

Full-Scale image at AstroBin.

Where to even start with this? How about the data?

Originally there were 13.2 hours of data, but I came across a video in which someone explained how they use PixInsight's SubframeSelector process to cull bad frames. My approach to data culling has always been to keep all that aren't terribly bad, but for this project I thought I'd get tough. Using SFS led me to reject 3.6 hours of data!  To be fair, about a third of that was because of my penchant for starting data collection before the end of twilight. There were very few visibly bad frames as viewed in Blink, so I'm going to call this approach "2 sigma" aggressive, in that it basically culls any frame that has  FWHM, eccentricity, or median values more than two standard deviations above the mean. Note that those rejected frames might be perfectly fine in and of themselves, but relative to their cohort they are of significantly lesser quality. Frames with anomalously low star counts are also culled. An example of this is the set collected during the session that a smoke layer moved in and began obscuring stars in the late morning. Star count fell markedly and I removed frames.

Worth mentioning was the need to use WBPP's Grouping Keywords to make sure that light frames and their appropriate flats were processed together. This was the first time I used it, and it worked perfectly. 

Also, I no longer use dark flats, or "flat darks," if you prefer. Only dark, flat, and bias frames are used for calibration. (Flat and dark frames are now taken for granted at Astrobin, it seems; it no longer asks if you use them.)

Now about the calibration frames, specifically the flats. It seems that most of the time my flat illumination was asymmetric for reasons I don't understand, and this gave the background modelization processing some problems. That big bright Polaris didn't help, either, nor did the fact that most of the image was nebulosity. My first pass used GradientCorrection and that left the right side with a green cast. After playing with that for a while I moved on to DynamicBackgroundExtraction. That didn't clear it up, either. After thinking about it for a while I reverted to AutomaticBackgroundExtractor with a 5th-order function and that did the job. 

Next, those darn satellites. The first processing pass got most of them, but a few stuck around in weakened form. They should have been removed during light frame integration, so I looked at what WBPP was using for rejection and it was Generalized Extreme Studentized Deviate (ESD). Some hunting around took me to a PixInsight forum where it was noted that ESD (using its default settings) wasn't doing a great job with satellites. So I told WBPP to instead use Linear Fit Clipping and that seemed to work better. Not perfect, just better. I will need to find out what ESD settings work best since overall it's probably the scheme to use. It may be that satellites and an image full of nebulosity are always going to be a problem.

I also learned that my usual haphazard application of the XTerminator family has been wrong. It's a processing sin to use NoiseXT before BlurXT and NoiseXT before SPCC. For this image I only applied NXT after taking the image nonlinear.

Here's my workflow for this project with the ">" symbol meaning "creates":

WBPP  >  Cropped channel masters

ABE (color channels) > Backgrounded color channel masters

ChannelCombination > RGB master

ImageSolve > RGB master with astrometry 

SPCC > color-calibrated RGB master

ABE (luminance) > Backgrounded luminance master

BXT (luminance master and RGB master) > enhanced masters

STF and HT > nonlinear masters

NXT > de-noised masters

CurveTransformation (with gentle "S" curve) > enhanced masters

LRGBCombination > LRGB master

assorted tweaks (saturation, sharpness, contrast, etc.) > Finished image

Not shown is an additional DynamicCrop after the ABE of luminance because ABE was a little overaggressive at the left edge. Even with two crops, the final image lost only 4.2% off the short axis and 5.5% off the long axis for a 10% areal loss. The reproducibility of the image framing was impressive. Thank you, NINA. 

Another lesson learned was that the XTerminators could be sped up quite a bit. Normally the necessary files are installed by XTs, but on my old computer the install did not engage the GPU. My graphics card is an NVIDEA GeForce GTX 1050 Ti circa 2018. This post explains how to upgrade a computer to use the GPU for faster XT performance. In my case it sped up the XTs by a factor of 4. I may need to repeat this every time XT does an upgrade.

So how did the processing work out? Mostly I was concerned that the area around Polaris was darkened by background extraction and didn't represent reality. I searched AstroBin for an image I could use as a sort of "ground truth" for what I had done. I found just what I wanted in an image by captured_mom8nts (which I'm guessing is not their real name). It appears to have been taken at a much shorter focal length and so should have suffered much less Polaris bloom, keeping the area around the star reasonably pristine. A little crop/rotate/scale/stretch and it matched my image's scale and orientation:

Comparison: Mine (top), captured_mom8nts (bottom)

I think it fairly obvious that the dark areas on either side of  Polaris in my image match those in captured_mom8nt's image, even though mine is much deeper. I'm happy!

I'm also happy with the star color. Shooting only 90 s exposures may have been the key to that in that it kept stars from saturating. Next time I'll be shooting at f/2, but with a smaller objective so I may keep the exposure time as is. 

-----------------------------------------

All the components of my new Samyang 135 mm f/2 imaging system have arrived or are on their way. Next time I'll have a picture of it all assembled and possibly already taken on its first test drive!

Reprocessed IFN Using PixInsight's WBPP

The image in the last post was really not very well processed, with the culprit being me. I suspect I twice subtracted bias or something. It was so bad that I decided to reprocess immediately, adding in some color channel data I collected. The best way I could see to avoid messing up again was to plunge right into using PixInsight's popular Weighted Batch Preprocessing script (WBPP).

Was it easy to use? Yes! If you disagree, I suggest watching the series of WBPP tutorials by Adam Block.

Did it work well with all the default settings? Yes, it did for me. The only step I skipped was Cosmetic Correction. I'll have time to learn how to incorporate CC between now and when I need to process new data collected later this month. 

Was it fast? I fed it my 72 luminance frames, 36 color frames, 100 bias frames, 30 dark frames, and 100 channel flats. WBPP made master frames, calibrated my light frames, and registered and integrated the lights, and finished by doing a crop of all four channels. All that in 51 minutes. Wow!

I know there's some sort of WBPP Fast Integration thing that can reduce this even further, but I'm saving that for the future.

The WBPP result is so much better. Here is the master luminance after post-processing:

Polaris IFN as processed by PixInsight WBPP

The full scale image is on AstroBin. Because Astrometry.net as employed by AstroBin seems to have issues with this, I'll pass along ASTAP's solution:

ASTAP solve of above image.
North is up; the celestial pole is a little beyond the top edge

This is exactly the composition I want: Polaris sitting at top center and giving the illusion of shining its light down on the nebulosity. Which it probably isn't actually doing, but artistic license is allowed, right? 😏

Not only is that ugly vertical banding gone, the stars are better shaped. ASTAP puts the tilt at only 3% ("none") compared to the previous "moderate." I continue to be amazed that so much nebulosity can be captured with less that two hours of total exposure at a Bortle 4 site with a nasty high-in-the-sky first quarter moon.  

The color image was not adequate and you won't see it here. It looked as if the background flattening of the three channels had gone awry. I'll need to play with the color channels and see if I can do better.

The night I collected the color frames give me hope for my camping trip. PHD2 guiding was almost perfect. Of 36 frames, none were rejected. With dithering turned off there were no hiccups. I retrained PHD2 beforehand, this time with the correct focal length for the guide scope, and it seemed better behaved. 

Reacquiring the image area worked great. The evening was the third time I told NINA to go to the target. It seems to be doing this quite well: almost nothing has been lost due to mistargeting: 

Portion of full image removed by WBPP cropping (red)

Everything considered, it all worked as intended. That's a little scary; I have to wonder what mischief my hardware has planned for me when I take it to the dark-sky campground.

-------------------

While the tariff wars have devolved into confusion over what, when, and how much, the Rokinon 135 mm f/2 lens for Canon hangs in there at the same old $449. If you've been watching the astronomy gear dealerships, you've probably noticed that many items are no longer in stock. Buyers seem to be rushing their purchases to avoid the expected higher prices.

Integrated Flux Nebula Mini-Test Result

 Let's get right to the image:

Polaris IFN luminance trial

The total exposure was a scant 1.8 hours (72 x 90 s). NINA ran the acquisition and PixInsight handled the processing. Flat frames were used. The nonlinear stretch was the PI Screen Transfer function and no attempt was made to enhance contrast beyond what it provided.

This is so far beyond my expectations that I don't know what to write. It was a not-very-dark site, the moon was at first quarter high in the ecliptic between Cancer and Leo, and there was a thin layer of smoke aloft. I really didn't expect to get much if any nebulosity in the image. But there it is.

The night's goal was to fully test the imaging setup and perhaps answer a few questions:

• Would go-to compose the image reliably? I started it once, collected a dozen frames, shut it all down, parked the scope and did the entire startup again. Plate solving shows the center changed by 67.5 seconds in RA and 7 seconds in Dec. Translating the RA difference to arcseconds at the equator, it's actually more like 27 arc seconds. That's total shift of about 28 arcseconds. The difference in image axis rotation is also tiny, about 0.11 degrees. So the answer is Yes, go-to works very well!
• Would guiding work so close to the pole? I had made some changes in PHD2--activating multi-star guiding and predictive PEC, and using the calibration assistant to make sure that was done optimally. Through the evening it collected 72 light frames, and only one had to be rejected (when PHD2 timed out after a dither). Tracking was next to perfect. I'm nor sure the ASI 2600 benefits much from dithering, so I'll disable it.
• Some people have indicated issues with field rotation when guiding near a celestial pole. I saw no sign of that. Possibly the excellent polar alignment from PoleMaster should get credit for this.

I do like the composition of the image, with Polaris shifted off center northward and looking as if it's shining light down onto the nebulosity. It's nice to see that the offset doesn't produce any significant internal reflection.

There are issues with this image, though. Although ASTAP reports moderate tilt I don't see any evidence of it. (Maybe it's some sort of algorithmic issue?) There are a lot of vertical bands in this that snuck in during the processing. I'll have to find a way to make sure to avoid them. [EDIT 12 May: see the reprocessed image here.]

PHD2 was doing something that seemed odd. Every now and then it would make a too-large declination adjustment and then follow that with smaller corrections. This may also have been my fault as I had the wrong guide scope focal length entered. This has been corrected, so I'll see if that takes care of the issue. 

Tonight I'll be out again to test my RGB acquisition scheme. Basically, I'll try the good old 3:1:1:1 channel ratio, meaning 24 frames for each color channel. How will the colors turn out?

IFN Setup Passes Its First Tests (With Help From BlurXTerminator)

Last night was good for running some tests on my integrated flux nebula (IFN) imaging setup. I was able to take test frames at different exposures (60, 90, 120, 180 and 240 seconds) and test go-to and tracking. Everything came out well, or as well as could be expected and many questions were answered.

Did Polaris throw an internal reflection?

I stretched a 240 s exposure using PixInsight's Boosted Autostretch and there was no evidence of any internal reflections. It's possible something will show up in an image stack, but this suggests even if it does it will be faint.

Was the field suitably free of aberration? 

Here's a visual comparison of the corners and center in one of the 2 minute exposures (click for full scale). This is basically a raw frame; it's only been brute-force flatted and then delinearized with PI's default stretch.

Pretty awful, isn't it? My guess is that the aberration is coming from backfocus being significantly off. How much off, and in what sense? I'd use NINA's aberration inspector to find out, but this is a manual-focus lens. Sadly, my ability to change the backfocus is next to zero. Skip the following paragraph if talk about backfocus bores you :)

My required backfocus should be about 45 mm (44 for the lens plus1 for the filter), and I'm currently at 42.5 mm. The best I can do to increase this is by adding a 0.8 mm thin spacer or whatever the thinnest M42 spacer ring is (probably 5 mm?). Decreasing the backfocus would require a Canon-M42 adapter that's thinner than 10 mm or a filter drawer that's thinner than 20 mm and can be adapted to use 36 mm filters. Increasing the fun is that this lens is actually at heart a Tamron Adaptall lens circa 1980, fitted with a ring to make it compatible with OM-1 cameras. Both date back to the 1970s, so good luck finding things to take advantage of any of that. And yes, I looked into having a custom adapter built, both Canon to M42 and Olympus OM to M42, and they can't do it in a way that works for me (not to mention it would be $$$ if they could).

Fortunately the aberration can be adequately dealt with using BlurXTerminator (BXT). The corner diagram below shows how well BXT fixes things using the very non-aggressive settings of zero for both its "Sharpen Stars" and "Adjust Star Halos" parameters:

The improvement is almost miraculous. All the corners look sharp. So the lens passes this test thanks to processing with BXT.

Can the lens reach a decent focus?

The focus you see is the result of a few minutes of shooting test frames and making very tiny manual adjustments (just like in the old days before I had an electronic focusing motor). I think it's quite good. Yes, I'd love to have NINA do the focusing for me, but that's not going to happen.

I will need to stabilize the focus wheel to avoid accidental movement; a piece of tape should work.

Was there tilt?

A first look at tilt as calculated by ASTAP gave this.

It's not so much tilt around one axis as it is a sign of the aberration. ASTAP considers the tilt severe (see the small text along bottom of image). After BXT has been run the results confirm the improvement seen in the second corner diagram above: 

Star size outside the center is dramatically reduced and ASTAP now considers the tilt to be "almost none." This means I won't need to add the tilt plate or shims.

What about the mount and Go-To?

The mount slewed to Polaris and plate solved without fault. Manually correcting the rotation was simple and fast. The required rotation was only eight degrees, so the riser wasn't necessary and will be removed.

How was the tracking?

The center stars in the pre-BXTcorner diagram were nice and round so I'll assume tracking is close to perfect. The corner stars in the post-BXT are fine, too, so there's no appreciable field rotation in a 2 minute span.  I use PoleMaster for polar alignment, and it provides almost no visible rotation even over a multi-hour session, so I think that tracking should be more than adequate.

In other words, there's no need to add autoguiding or fiddle with PEC.

Were there any composition issues?

The amount of camera rotation required was only eight degrees from the filter wheel's long-axis up position, meaning that the riser wasn't needed. I'll remove it and the system will be a little sturdier.

Oddly NGC 188 was not quite where I wanted it. It's a touch close to an edge than I expected. I'll have to look at the instructions I gave NINA.

Summary

Everything worked better than expected with help from BXT! Basically, the system is ready for field use, although a little more work remains to get it set up for dew control. Because BXT removed the aberration using very nonaggressive settings, I don't think it will damage the IFN.

A major concern was the mount: would it behave itself for a target so close to the celestial pole? It slewed and centered on the target without difficulty. Manual rotation was easy and the riser won't be needed.

I think the ASI-2600 will do fine without dithering, but I may try that anyway with the PixInsight manual dithering tool.

It looks like almost any exposure will serve well; even a 4-minute exposure had nice round stars; I think I'll probably use 2 minutes for all four channels.

----------------

My reading of Hugo Award winning novels is winding down. I skipped back to the 2000 winner, A Deepness in the Sky, by Vernor Vinge, and it was slog to get through. A few times it was almost a DNF (did not finish). I just couldn't connect with the author's writing style, his use of many side characters that were of little consequence, and the too-happy ending that seemed rather forced. For some reason he felt compelled to add a bloated epilog that served mainly to punish readers. Most of the Hugos have been worth reading, but not this one.

Up next is the 1939 Retro Hugo Award winner, The Sword in the Stone by T. H. White. Yes, it's that sword in that stone; the story has spawned a number of adaptations (the 1963 animated version by Disney is probably still the best known.

This will be the end of the Hugos for me, at least for a while. Maybe I'll start another reading marathon when my wife has her other knee replaced.

----------------

It's lithium battery maintenance time: all the batteries have been fully recharged and then discharged to about 50% of capacity. Just before Northern Nights Star Fest I'll be bringing them up to full charge and selling/swapping them at 80% below list price. I'll provide a full description of what I'm bringing to NNSF in an August post.