No Red Data with CLS Filter

13 replies337 views
Mark Germani avatar
Hi there!

I'm pretty perplexed by the lack of red data when using CLS filters. I have two - the Svbony CLS and the Astronomik CLS (not CCD) which I'm testing with an unmodified Canon 600D/T3i. I'm shooting from a Bortle class 8 zone.

Here is a single RAW file from my camera:

https://www.dropbox.com/s/sfvqyctkapl9i6j/IMG_0650.CR2?dl=0

This is the North America nebula, taken with the Astronomik CLS filter, 120s ISO 800. My red channel shows only stars, and zero nebulosity or background levels. The Svbony is pretty similar, but with less green and blue and *slightly* more red. Given that this is a Ha-rich magnitude 4 object, I'm quite baffled as to how my red channel collected as little as it did. Here is the spectral response of the channels in my camera:

https://www.researchgate.net/figure/Spectral-response-of-a-Canon-T3i-APS-C-CMOS-image-sensor-with-a-Bayer-pattern-CFA-This_fig5_287249644

I see that the blue and green channels have a small amount of response at 650nm. I do see nebulosity when I stack images. Am I only seeing Ha nebulosity from the green and blue channels, then? Am I seeing nebulosity in a different wavelength? I know the Astronomik CLS cuts from about 545-645nm, but even with an unmodified camera, I thought Canons still picked up a fair bit of Ha. In the spectral response graph, it looks like my camera should still be picking up some red that the CLS filter shouldn't be cutting off, but all I see are star cores.

Is this completely normal, and I should continue using the filter and balance the colours during processing? Is this completely normal and I should modify my camera before trying to collect light from emission targets? Or is this abnormal and something is wrong with my filter/camera/acquisition technique?

Thanks in advance for your input! I'm planning on imaging tonight and I'm torn between holding off on nebulae and imaging globular clusters, or going with what I have and starting a new nebula project.

Cheers,
Mark
Well Written Helpful Insightful Respectful Engaging
Ferenc Szabo avatar
I looked at the image, and although I'm a beginner, I believe it's light pollution defeating your camera, regardless of the LP filter.  The star cores look clipped so it's a bit over exposed, but the sky brightness gets ahead and fills your electron well depths of your sensors.  Regardless what you see or don't see in the subs, keep the histogram of the subs at the 1/4 of the graph. Also try ISO400 also and adjust exposure length so your light information peak is still at the first quarter of the histogram.  I can't tell you what's that gonna be, maybe 60seconds maybe 90 maybe even 30seconds, maybe 120 so don't be surprised.  
Me at Bortle 5 with no filters on my Pentax, I can only go like 90 seconds at ISO 400 before I clip the stars. Just some info. 
I know it's possible to get the N. American Nebula with a stock Canon, people done it at Bortle 9 with no filter at all. 
Anyway clear skies! 
Experiment with ISO-s and exposure lengths, that's what I do. 
 I am also new at this, so someone with more experience may chime in and correct me if I'm wrong. 

Here is where to get that histogram (ignore that picture in the LCD, you'll never see that in a single sub) 

https://scopetour.com/wp-content/uploads/2021/03/histogram.jpg
Helpful Respectful Engaging Supportive
normmalin avatar
Not sure what is happening with your specific image, but I can tell you that with a Svbony CLS filter in a Bortle 7 sky using a Canon 800D (T7i), I was able to see the nebula in a 2-minute exposure at ISO 1600 in the red channel.  That said, my blue and green histograms were right of center during collection which is not ideal.   If you have the money, investing in a narrow band h-alpha filter or dual narrow band h-alpha/OIII (like an optolong L-enhance) will pay off.  It will remove most of the light pollution and make the h-alpha emission nebulae pop - even in badly polluted skies.

Clear Skies!
Well Written Helpful Insightful
Björn Arnold avatar
Hi Mark,

There is nothing wrong with your observation. If you don’t use the CLS, you will see red tones in the sky background but that’s the light pollution which is supposed to be suppressed.

The nebula itself is emitting in Ha, which the filter does transmit but your camera is not sensitive enough to show it that quickly, compared to wavelengths in the green and blue spectral range. The Ha sensitivity , compared to peak sensitivity (in the green spectrum) can be as low as 5% (depending on the camera).

The are two solutions:
- much longer exposures 
- astromodification/dedicated astro camera. 

Best,
Björn

PS: in another thread this has recently also been discussed
Helpful Respectful Concise Supportive
HR_Maurer avatar
Here is the spectral response of the channels in my camera:
https://www.researchgate.net/figure/Spectral-response-of-a-Canon-T3i-APS-C-CMOS-image-sensor-with-a-Bayer-pattern-CFA-This_fig5_287249644

Mi Mark,
indeed your image doesnt look like i'd expect in the first place. But something different caught my attention! I'm a bit confused of the Canon T3i (aka Canon 600D) spectral response image from that paper. It shows peak sensitivity at 650 nm. To be honest, i doubt it, despite it has been published in Optics Letters. At least, it must be a modified camera, but i found no mention in the paper prosa. Usually i would expect to obtain a spectral response from that camera, that is somewhat resembling that of the human eye - having something like 5% response in that spectral region.
Capturing absolute spectra, including spectral responses, is not a trivial task. Usually you need a calibrated tungsten strip lamp for intensity calibration. I heard of rumors, it is possible using the sun as an alternate method, but i think it is very (to terribly) inprecise because of aerosols.
I see that the blue and green channels have a small amount of response at 650nm.

Couldn't this result from h-beta (486 nm), which is very close to OIII?

CS Horst
Helpful Insightful Engaging
Björn Arnold avatar
The article only says that they‘ve used the sensor. This might mean that it’s without the IR-Filter.
Also, I don‘t know what RAW means to them? I would assume that they didn’t develop a readout and processing circuit but use Canon‘s DIGIC chip which provides a white balance, which IMHO would explain this response spectrum.
A few things aren’t explained since the CFA collects twice the amount of green than red (area wise). Therefore, it’s dubious that green should have a lesser response than red.
Helpful Insightful Respectful
Mark Germani avatar
Thank you all!

Sorry for the delay in wading back in here, I've had a busy few days.

@frankszabo75 thank you for the insight regarding clipped stars. I might either have to live with that, or try doing shorter or lower-ISO subs and combining them with a starless version of the nebula. My histogram is at the 1/4 mark currently. Since I'm imaging un-guided, my stars become more and more eccentric past 2 minutes so using a lower ISO for the nebulosity is not an option for me at this point, sadly.

@normmalin thanks, I think a narrowband filter like the l-enhance or l-extreme will be in my future, but perhaps not until I invest in a guiding setup so I can image for the longer times it will take with those filters.

I actually discovered the red info hiding beneath the bottom of the histogram when viewing the raw files in Adobe Camera Raw. As soon as I changed the white-balance slider and the tint, I was able to balance the colours and retrieve the red info. I have NO idea why the histogram doesn't show red info below a certain point, perhaps it's not in the desirable range of red for daytime photography so they don't show it? Alternatively, was I taking blue and green data and redistributing it as red by sliding the temperature and tint sliders in Camera Raw? The histogram didn't really bear that out, it seemed like the bumps for red and green were just just moving laterally rather than decreasing or narrowing.

@Björn Arnold some great insight, thank you! I decided to increase my exposure by upping my ISO rather than time, as I need to be mindful of how many subs I have to toss. I modified my histogram to show RGB separately instead of averaged, and nudged my ISO up to 1600. I increased my exposure time until the red channel was no longer clipping at the bottom. I think this is a good balance between blown-out stars and underexposed nebulosity. In the end, 75-90s at ISO1600 was the sweet spot for NGC 7000.

@HR_Maurer thanks - that's reassuring. I guess I should be a little more skeptical. I remember seeing more accurate spectral response curves for the 600D/T3i elsehwere on the internet, but I had trouble tracking that graph down. 5% transmission at 650nm would account for my reduced red data. @Björn Arnold your comment on the green response makes total sense. Also one of the reasons I love processing in APP with bayer-drizzle. I get twice the SNR on the green channel!

With all your feedback in mind, I did manage to get 25 minutes of pretty decent subs during a break in the clouds on Thursday night, and I did a quick process which revealed plenty of nebulosity which I was able to colour-correct. There is SO much to learn in this hobby!

CS,
Mark
Helpful Respectful Engaging
Björn Arnold avatar
Hi Mark,

I'm actually making tests to use longer exposures to capture the fainter/-est details. That's where statistics comes again back into the game: to capture the faint details with very low photon rates, the statistical methods are likely clipping them out as they'd only appear on a smaller subset of the lights when using short exposures. I've been using 300s subs for luminance data. I didn't go further because I first want to assess the quality of the guiding for even longer shots. With longer exposures the number of subs drops accordingly (for fixed total integration time) and mishaps (satellites, wind gusts) kill a more significant amount of data than with many short exposures.

For my approach, I'm turning the gain down to the lowest possible value, i.e., 1. For a DSLR that would be ISO 100. Blowing out stars will happen but also keep in mind: increasing gain decreases the available full well depth and reduces dynamic range. If you reduce ISO from 1600 to 800, you should be able to double exposure time without clipping more than before.

Björn
Helpful Insightful Respectful Engaging Supportive
Mark Germani avatar
Björn Arnold:
For my approach, I'm turning the gain down to the lowest possible value, i.e., 1. For a DSLR that would be ISO 100. Blowing out stars will happen but also keep in mind: increasing gain decreases the available full well depth and reduces dynamic range. If you reduce ISO from 1600 to 800, you should be able to double exposure time without clipping more than before.


Thanks @Björn Arnold. You’re right - I did find that statistically I get a better SNR at ISO400 than at ISO800 for the same integration time, but below ISO400 I have read that banding becomes an issue on Canon cameras, and some of my early camera lens work confirms this. Without a CLS sensor, I’m able to shoot 60-90s before blowing out stars at ISO400, and I used this approach when imaging M101 recently.

I would love to be able to take the same approach with the CLS filter, but that might have to wait until I get a guiding setup.

This has been really helpful in terms of setting my priorities for future investments. Thank you all for your input!

CS,
Mark
Well Written Respectful Supportive
Björn Arnold avatar
I haven't tried lowest ISOs with my Canon since I haven't used it after I bought a dedicated camera. I would assume that the banding would be corrected through calibration?

My dedicated camera also has banding which calibrates fine with Bias and Darks.

Sure, for these long exposures, you'll need guiding or an encoder based high-end mount.

Cheers,
Björn
Mark Germani avatar
Ok, I thought I'd just add a few things here:

I've been imaging with the Astronomik for a few nights now, same target. First two nights I shot at ISO1600 for 75 seconds. Last night I tried ISO800 for 120s, after seeing a few subs with good stars (spoiler alert: I had to toss 2/3 of them).

I have only stacked the first night so far, as a test. Once I corrected the colour balance, there was plenty of nebulosity despite being underexposed on the red channel. I'm going to add stack the rest of them just as soon as I get dark frames for last night's session.

One interesting little tidbit, though: I found a program called RawDigger because I was wondering if the Canon histogram was for a gamma-corrected image instead of the RAW file (which I think it is). RawDigger revealed some really interesting stats on overexposed/underexposed channels. As I suspected, Red is dramatically underexposed:

75s @ ISO1600: 13.4% underexposed
90s @ ISO1600: 9.7% underexposed
120s @ ISO800: 26.4% underexposed (but looks better than ISO1600 - better contrast in nebulosity too)
180s @ ISO800: 1.5% underexposed (wait, what?)

There is a big jump in red channel exposure beween 120s and 180s @ ISO800. Given that the histogram sits roughly at the same spot (on my camera at least) for "x" @ ISO1600 and "2x" @ ISO800, this means that lower ISO and longer exposures are key here, which everybody has been saying anyway!

Without guiding I'll stick to 75s or 90s @ ISO1600 for now. I really, really wonder how much astromodification could further reduce the underexposure levels without having to extend exposure times beyond what my mount is capable of, without guiding.

Cheers,
Mark
Helpful Insightful Engaging
Mark Germani avatar
Mark Germani:
120s @ ISO800: 26.4% underexposed (but looks better than ISO1600 - better contrast in nebulosity too)


I should add, these stats seem to vary based on seeing. As Cygnus rose in the sky, the underexposure rate increased from 14% to 26% so I suspect a certain amount of the exposure earlier in the evening was just atmosphere or thin cloud reflecting city lights.
HR_Maurer avatar
Hi Mark,
maybe i missed something - how do you define "underexposure"?
Is this the missing percentage of the brightest (non-defect) pixels, to reach full bit count?

CS Horst
Mark Germani avatar
@HR_Maurer I wondered this too. My guess is that it represents pixels that recorded no value. I wasn’t able to find out anything further in the included documentation, so I figured I’d consider the numbers as relative rather than absolute values, for the purposes of comparison between exposure settings. It’s a good point though!
Well Written Respectful Engaging Supportive