[Solved] Badpixel map need some help

@moviecells I have asked Mabula to reply to you.

Hi @moviecells,

2 BPMs are created because the instrument name in your data is not consistent.

Look at the INSTRUME tag in the BPMs:

INSTRUME= 'ZWO ASI294MM Pro' / instrument name

INSTRUME= 'ASI294mm' / instrument name

So APP is seeing this as 2 different camera's which is logical and needs to be done like that.

You can fix it in your dataset by using the batch modify FITS metadata tool in the TOOLS tab.

@mabula-admin

Ok i see that now, if i ignore that for now which process gives the best pixel map just from the dark files as that give me what seem to be a good pixel map.

If i try and use both and flats/darkflat i don't seem to get a good pixelmap and the file names of the flat/darkflat match for camera i don't seem to get a good pixel map

Image #1
SIMPLE = T / Java FITS: Thu Sep 23 08:00:04 BST 2021
BITPIX = 8 / bits per data value
NAXIS = 2 / number of axes
NAXIS1 = 8288 / size of the n'th axis
NAXIS2 = 5644 / size of the n'th axis
EXTEND = T / Extensions are permitted
DATE = '2021-09-23T07:49:52' / creation date of BadPixelMap
SOFTWARE= 'Astro Pixel Processor by Aries Productions' / software
VERSION = '1.083-beta2' / Astro Pixel Processor version
CALFRAME= 'BadPixelMap' / bad pixel map for instrument ASI294mm
INSTRUME= 'ASI294mm' / instrument name
CFAIMAGE= 'no ' / Color Filter Array pattern
EXPTIME = 0.0 / exposure time (s)
GAIN = 0.0 / gain or ISO depending on instrument
AD-PED = 0.0 / adaptive pedestal from data calibration
NPIX = 46777472 / raw number of pixels
HOTKAPPA= '3.00 ' / kappa value used for hot pixel determination
COLDFRAC= '0.10 ' / percentage used for cold pixel determination
NBADPIX = 0 / number of bad pixels
PBADPIX = '0.000 ' / percentage of bad pixels
NHOTPIX = 0 / number of hot pixels
PHOTPIX = '0.000 ' / percentage of hot pixels
NCOLDPIX= 0 / number of cold pixels
PCOLDPIX= '0.000 ' / percentage of cold pixels
NLINPIX = 46777472 / number of linear pixels
PLINPIX = '100.000 ' / percentage of linear pixels
NUMDARKS= 200 / # of dark frames used in creation of the BPM
NUMFLATS= 200 / # of flat frames used in creation of the BPM

Mike

Hi Michael @moviecells,

The Bad Pixel Map tooltip explains it:

Darks are needed for hot pixels and Flats are needed if you have defective or cold pixels. Flat Darks have no influence for hot pixel detection because their exposure is so short that dark current and the hot pixels are less clear so you always want to use proper darks with several minutes of exposure time to get the best hot pixel detection.

You don't need to make darks again and again for the Bad Pixel Map. Just make one batch of long exposed darks without sensor cooling and make your Bad Pixel Map. That BPM will work very nicely for a long time on all your data 😉

@mabula-admin

Can i ask why do this without cooling, should it not match the lights are cooled.

The BPM is not destructive to your data, so it's a good idea to get as much noise (hot-pixels) as possible that your sensor can generate. No cooling would help with that. The no cooling-dark would then only be to create a BPM, regular darks for your data need the same settings indeed.

Posted by: @moviecells

@mabula-admin

Can i ask why do this without cooling, should it not match the lights are cooled.

 

 

Hi @moviecells, indeed like Vincent indicates, no cooling gives much more dark signal and hot pixels so the hot pixels are detected easier and thus the BPM will become more robust if you create a BPM with uncooled darks 😉 But, to be clear, even on well-cooled darks it works very well !

And yes, only use the uncooled darks to make the BPM, don't use them for light frame calibration 😉

@mabula-admin

Thanks to all for the help, clouds roll in tomorrow so will take some long non cooled darks for a BPM. it clear tonight only the 4 night this year so far so off to set up.