Darks, Flats, Bias created with Voyager, Lights created with SGP WBPP rejects with the error....

Main Sequence Software Sequence Generator Pro (SGP) Starkeeper Voyager Processing Calibration Deep Sky
12 replies•204 views
Seymore Stars avatar
Seymore Stars avatar
No matching Master Bias, Master Dark and Master Flat found.


 The following image parameters are all the same.
QHY600M Mode set to Mode_3 ( 'Extend Fullwell 2CMS')
Binning
Exposure length
Gain
Offset
Filter The only significant difference I can see in the FITS Header is READOUTM. For SGP = 'Fast   ' and for Voyager = 'Extend Fullwell 2CMS'.

Are things so crazy that all all image types (Darks, Flats, Bias, Lights) have to be created with the same imaging software package? 

Thanks!!
Steve
Roger Nichol avatar
Roger Nichol avatar
Check that the pixel dimensions are identical.
Dark Matters Astrophotography avatar
Dark Matters Astrophotography avatar
They do not need to be created in the same package. Does one set of the data have the overscan enabled?
Seymore Stars avatar
Seymore Stars avatar
Roger Nichol:
Check that the pixel dimensions are identical.



Yes they are all the same 3.76 um square which is correct for the QHY600 camera.

Steve
Seymore Stars avatar
Seymore Stars avatar
They do not need to be created in the same package. Does one set of the data have the overscan enabled?


Good question Bill I will have to fire up the observatory to answer that one, Thanks!!

Steve
Seymore Stars avatar
Seymore Stars avatar
Correction you hit the Nail On the Head Bill. The Y/X axis' are different.

Solution found Problem solved.

Thank You!!
Steve
Reg Pratt avatar
Reg Pratt avatar
Roger Nichol:
Check that the pixel dimensions are identical.

This. Back when I was trying Voyager from NINA the calibration frames from NINA wouldnt calibrate lights from Voyager. Upon inspection the pixel dimensions of light frames captured between the 2 software were different.
Seymore Stars avatar
Seymore Stars avatar
Roger Nichol:
Check that the pixel dimensions are identical.



Roger you probaly meant for me to compare the "Sensor" dimensions.

Thanks
Steve
Dark Matters Astrophotography avatar
Dark Matters Astrophotography avatar
Reg Pratt:
Roger Nichol:
Check that the pixel dimensions are identical.

This. Back when I was trying Voyager from NINA the calibration frames from NINA wouldnt calibrate lights from Voyager. Upon inspection the pixel dimensions were different.

Was this an overscan issue? Both Voyager and NINA use the same QHY SDK so images taken with either should match, unless overscan was turned on in one and off in the other.
Well Written Insightful Respectful Concise
Dark Matters Astrophotography avatar
Dark Matters Astrophotography avatar
I just checked, and they are indeed the same:

9576 x 6388.

Seymore Stars avatar
Seymore Stars avatar
Reg Pratt:
Roger Nichol:
Check that the pixel dimensions are identical.

This. Back when I was trying Voyager from NINA the calibration frames from NINA wouldnt calibrate lights from Voyager. Upon inspection the pixel dimensions of light frames captured between the 2 software were different.


Definitely an "Overscan Area" incompatibility in my case. Though not corrected yet they are different. 

Steve
Seymore Stars avatar
Seymore Stars avatar
The light frame dimesions are 9600 X 6422  and the calibration frames are 9576 X 6388.

Thanks everyone!!
Steve
Dark Matters Astrophotography avatar
Dark Matters Astrophotography avatar
Seymore Stars:
The light frame dimesions are 9600 X 6422  and the calibration frames are 9576 X 6388.

Thanks everyone!!
Steve

Hi Steve -- those are the exact dimensions I see with overscan turned on.
Well Written Respectful
Related discussions
New version of Python script to generate target acquisition.csv file from image files in a format suitable for upload using AstroBin's upload csv dialogue
Update 28th October 2024 I have just released the latest version of the script. v1.3.11V1.3.11 changes 1.0 Fixes bug where running the script for the first time from the installation directory would fail 2.0 Deals with the case where the filter names...
Script generates CSV from images; unrelated to calibration frame matching issues.
Feb 12, 2024
Reason for those linear image artifacts
Hi there, during the last nights, I collected some data of M51. Today, I stacked the images and in the master frames, i realized a linear halo through all of them. I could not detect those issues in the subs, but I guess they are there and just can&#...
Linear artifacts in stacked images; different problem than calibration frame compatibility.
May 15, 2024
Flats wrong orientation during calibration creating dust motes?
I have run into this very bizarre flat calibration issue in Pixinsight. Just some background, I imaged a target with my Luminance filter on my 6200mm pro last night, 60s each frame, for a total of 250 frames, at gain 100, default ASIair offset (50), ...
Flat calibration orientation issues; relevant to flat frame calibration problems.
Feb 14, 2024
"L" flats problem..
Hello All, My L flats at 3910 mm never seem to apply properly in WBPP; or at least not as well as the RGB flats. SHO always seem to work well. All else being the same. Values are consistent, calibration method in WBPP is consistent (with the other fi...
L-filter flat application problems in WBPP; directly relevant to flat calibration.
Mar 15, 2024
Confusing results coming from WBPP
Attached is a screenshot showing two different stacks from WBPP, each stacked with exactly the same settings (including the same master dark and master flat dark). Each stack is from two different nights but the same scope, camera, filter, etc (Rig i...
WBPP stacking with master dark/flat frames; relevant to calibration frame matching.
Apr 10, 2024