Stacking creating slices

Somewhere to ask questions about the best way to use SharpCap
Forum rules
‍

If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
Post Reply
garyhawkins
Posts: 54
Joined: Sun Dec 22, 2019 6:59 pm

Stacking creating slices

#1

Post by garyhawkins »

I have a series of photometry files (1504x1504), which were created by extracting a color channel from a series of color images (3008x3008). The single color file still has COLORTYP = RGGB in the FITS header - ASTAP did not update it. When I livestock these single color files (to improve SNR) using the Folder Monitor Option and save the 16-bit Stack, I get a 1504x1504 image file that has three slices. Is SharpCap treating the file as an RGB rather than a mono image because of the COLORTYP setting?

Best regards,

Gary
User avatar
admin
Site Admin
Posts: 17495
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: Stacking creating slices

#2

Post by admin »

Hi Gary,

it shouldn't treat it as RGB for that reason, as it is supposed to understand the various COLORTYP headers. Can you share one or more of the problem files with me and I will see if I can work out what is going on?

thanks,

Robin
garyhawkins
Posts: 54
Joined: Sun Dec 22, 2019 6:59 pm

Re: Stacking creating slices

#3

Post by garyhawkins »

Hi Robin,

I've discovered the issue I was looking into is not associated with the COLORTYP setting.

I am still interested to know why "when I livestock these single color files (to improve SNR) using the Folder Monitor Option and save the 16-bit Stack, I get a 1504x1504 image file that has three slices."

Thanks for the great work on SharpCap.

Happy Holidays,

Gary
User avatar
admin
Site Admin
Posts: 17495
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: Stacking creating slices

#4

Post by admin »

Hi Gary,

yes, I would be interested to dig into this - I tried a few tests myself and couldn't get anything like this to happen when re-loading FITS saved in SharpCap. I suspect there is something about the processed FITS that is not as I would expect - if you can upload one of them somewhere and share it with me I will investigate.

cheers,

Robin
Post Reply