CaLIGHTs Version 3.1.8 Released

15 views
Skip to first unread message

wols...@gmail.com

unread,
Dec 12, 2022, 3:20:05 PM12/12/22
to CaLIGHTs

I decided to switch to the 64bit version of LabVIEW from now on. 64b computers are pretty much standard these days There is certainly some memory improvements and speed improvements switching to a 64bit environment.

As always let me know if you have issues with this version

Peter


Latest Revision 3.1.8.00

How CaLIGHTs works with masterDARKs and masterFLATs  I have been doing some very careful analysis of how CaLIGHTs calibrates your LIGHT frames and I decided to make two changes which should improve your results. When you use the Preference button to change the Pedestal Priority to Master DARK, CaLIGHTs was using the mean values of the masterDARK to determine this pedestal. Amp Glow can be a significant issue with masterDARKs which can increase the calculated mean values of the masterDARK. All of the benefits of using a masterDARK were being achieved but the calibrated LIGHT frame could end up being slightly darker. I decided to change the Pedestal calculation so that, for masterDARKs, the pedestal values are determined by using only the pixel values in the center of the masterDARK. This avoids any influence of Amp Glow and also eliminates the slight darkening I was detecting.

The vignetting effects that are corrected by using a masterFLAT can be dramatic. Pixel values at the edges of your LIGHT frames can need to be increased by 30% or more to compensate for vignetting. Up to this point I had decided to “split-the-difference” and distribute the masterFLAT compensation over the entire image. The 30% or more increase was re-distributed such that the center of the image was darkened and the edges were brightened so that the 30% or more vignetting compensation would still be applied. I decided that I wanted the brightness of the center pixels to not be affected by FLAT compensation. The FLAT compensation now only brightens the outer pixels of your LIGHT frames and preserves the brightness of the center pixels. This means that bright stars located at the edges of your LIGHT frame can be saturated solely because of FLAT compensation. I would encourage everyone to use the StarSatGuard feature which understands this issue and will limit the brightness of these affected stars so that they are not saturated and their color can be preserved.

Don’t allow Negative values  During the calibration process, specifically masterDARK subtraction, there is a grey area where some pixels in the masterDARK are slightly HOT but are not HOT enough to be detected statistically.  When you throw in random noise from shot noise and camera noise and combine this will LIGHT frames taken at a dark site you can get a situation where a pixel’s calibrated value can be smaller than the camera’s BlackADU value. The BlackADU value is defined as the value equal to complete darkness...so values less than BlackADU don’t make any practical sense.  These very dark pixels look like black specs that are very pronounced in the darkest portions of your LIGHT frame.

I have added a Don’t allow Negative values option to mark these very dark pixels as bad pixels so that their pixel values are substituted using the values of their nearest neighbours. This new option can be enabled via the Preferences button on the main screen.

Image Viewer  You can now use the F9 function key to save a screen capture of the image to your computer. This may be useful to document issues you experience with your astrophotos. The title is not included in the screen capture but the statistics (right-clicking on the image displays stats where you clicked) are included.

Image Viewer Statistics  When you are using the Image Viewer you still can right-click anywhere on the displayed image and some statistics will appear. I have modified the statistics to make them more useful. Here is what the statistics look like now…

N=1024  dX x dY = 32 x 32

 Range(X,Y)=(1700,1306) to (1732,1338)

 RED       SNR=0.21  SD=  18

 Min=  32 Avg=  76 Max= 128

 GREEN  SNR=0.47  SD=21.2132

 Min=  60 Avg= 108 Max= 208

 BLUE     SNR=0.21  SD=  18

 Min=  36 Avg=  84 Max= 212

 

The values displayed for “SD=” are still standard deviation values but they are calculated using what I call a graphical method. This is the same graphical method I use for the StdDevg statistics displayed on the Make Averaged Master Histogram. The graphical method is more immune to hot or cold pixel values which, I believe, improves the usefulness of the SD values. Hot and Cold pixel values still influence the Min and Max values.

 

Image Preview I split the Shift HFD Rnd Angle feature into two features. There is now a Show Color Shift feature which generates the Shift image. I also created a Show Star Statistics feature which performs the HFD, Rnd and Angle analysis.  I also made the Show Star Statistics feature the default when you first call up the Image Preview.

Scott Kuchma

unread,
Dec 12, 2022, 5:33:05 PM12/12/22
to CaLIGHTs
Hi Peter ,

For some reason I decided I needed to have a look at the CaLIGHTs page and Voila ! A new version of CaLIGHTs !

Quick question / observation ... in the above text...in the Bold "Don't allow Negative values" , you have a text line as follows...

"...random noise from shot noise and camera noise and combine this will LIGHT frames taken at a dark site you can get a situation where a pixel’s calibrated value can be smaller than the camera’s BlackADU value."

I can't figure out what you meant to say here . Something is missing I think .

Now a real question , will my old Master Calibration Frames , taken using earlier versions of CaLIGHTs , be valid in re-Calibrating an old set of Lights using this new version of CaLIGHTs ?
If so , I may be tempted to try re-doing a few Astro Images from 2019 that gave me some grief . As well , there have been several impressive Updates to SiriL as of late which I would like to explore as well .

Cheers and thanks for all the hard work .

Scott............

Scott Kuchma

unread,
Dec 12, 2022, 5:46:13 PM12/12/22
to CaLIGHTs
Hi Peter ,

Oh well , it looks like this latest version only supports Win10 which I do not have on my Laptop nor ever will . The requirements of this "Hobby" are quickly exceeding the financial resources required to support it  . LOL .
Time to sell it all and get back into Model Railroading maybe .

Thanks again ,

Scott.........

wols...@gmail.com

unread,
Dec 13, 2022, 8:38:42 AM12/13/22
to CaLIGHTs
Scott,
That particular sentence is just too huge to grasp what I was trying to explain. I will re-write it. Here is the background behind why I added this feature:
When I use my LeNhance narrowband filter at my dark site the resulting pixel values are very low. The Black ADU value for my QHY294C is roughly 35 counts and the pixel values in my astrophotos that correspond to the sky background barely reach 100 to 150 counts. When CaLIGHTs subtracts the masterDARK you can get a situation where a hot pixel value in the masterDARK will cause the corresponding pixel in the calibrated LIGHT frame to be very low....even lower than Black ADU. Values lower than Black ADU are not realistic so this is a problem that I decided to have CaLIGHTs identify. These pixels as declared BAD so that they are substituted with good values based upon its neighbouring pixels. Previous versions of CaLIGHTs did not try to catch this issue...this means that previous versions of CaLIGHTs had "Don't allow Negative values" = FALSE.

This feature is called "Don't allow Negative values" because when you subtract a masterDARK from a LIGHT frame the resulting pixel values get biased downward such that Black ADU = 0. So resulting values less than Black ADU are negative values.

When I noticed this happening only with my narrowband astrophotos I thought about always having CaLIGHTs detecting and correcting negative values. It wasn't until I start working on my "Optimum exposure time" post that I realized that this feature needs to be selectable. 

There is a lot going on in CaLIGHTs as it calibrates your LIGHT frames

Peter

On Monday, December 12, 2022 at 5:33:05 PM UTC-5 Scott Kuchma wrote:

wols...@gmail.com

unread,
Dec 13, 2022, 8:46:34 AM12/13/22
to CaLIGHTs
This year I decided to try the 64b version of LabVIEW because I hoped it would have lots of benefits. There are some minor improvements and I didn't make any changes that would prevent me from reverting back to a 32b environment. I also noticed that the 64b environment has quirks that make it frustrating to work with when you use two monitors as I do. I wrote CaLIGHTs specifically for beginners to learn about LIGHT frame calibration and for me to study this complicated hobby. I will revert V3.1.8 back to a 32b application which should solve your issue.

I will post an update here when the 32b version is available for download

Peter

On Monday, December 12, 2022 at 3:20:05 PM UTC-5 wols...@gmail.com wrote:
Reply all
Reply to author
Forward
0 new messages