Calibration warning...
 
Share:
Notifications
Clear all

2022-05-29: APP 2.0.0-beta2 has been released !

Release notes

Download links per platform:

windows 2.0.0-beta2

macOS x86_64 2.0.0-beta2

macOS arm64 M1 2.0.0-beta2

Linux DEB 2.0.0-beta2

Linux RPM 2.0.0-beta2

Calibration warnings


 Heno
(@heno)
Red Giant Customer
Joined: 5 years ago
Posts: 114
Topic starter  

Today I have had all sorts of calibration warnings which I don't understand at all.

I took 8 sets (8 filters) of flats and dark flats using NINA's Flats wizard. I loaded them into APP to create master files. APP created the MDF as it should. But when APP started to create the MF, I got this critical warning. APP did not seem to recognize the MDFs it just created.

Calibration warning

But they were all there, image below. (This has in fact happened to me before!)

MDF

I removed the dark flats, kept the MDFs and rerun the calibration. No warning this time. So I thought all was OK. (MFs were created in both runs).

Now I want to use the MFs and MDFs to calibrate the lights. Immediately I had this warning.

Critical warning

This time I had these calibration files loaded:

Calibration files

I pressed OK to the warning and kept going, but I have absolutely no idea if the calibration works OK or not, or if the calibration warning is incorrect. I see no reason for this warning.

1. Why is this happening at all?
2. How can I see (numbers or otherwise) if the MDFs have been used when creating the MFs?
2. How can I find out if APP is using the MDFs as it should when stacking lights?

 


ReplyQuote
Topic Tags
(@wvreeven)
Galaxy Admin
Joined: 4 years ago
Posts: 1724
 

@heno I'll try to answer your questions.

1. In order to help you find out, we'll need more info. How many flats and dark flats are you loading per session? Are you loading any flats or dark flats in more than one session? Do all flats and dark flats in a single session have the same exposure time or do they vary because of the use of a flat wizard?

2. You can see that information in the console log of APP.

3. APP should not use the MDFs on the lights. The MDFs are only used to calibrate the flats. Once the MFs have been created, the MDFs are no longer used.


ReplyQuote
(@mabula-admin)
Quasar Admin
Joined: 5 years ago
Posts: 3159
 
Posted by: @heno

Now I want to use the MFs and MDFs to calibrate the lights. Immediately I had this warning.

Critical warning

This time I had these calibration files loaded:

Calibration files

Hi Heno @heno, If you only load MasterFlats to calibrate lights, then this warning should always appear. This is expected. The warning clearly states why the warning is thrown:

you need to add either bias and/or darks to calibrate the lights to have the flats as expected. Both Flats and Lights need to have the sensor offset subtracted for flat-field calibration to work 😉

Mabula


ReplyQuote
(@mabula-admin)
Quasar Admin
Joined: 5 years ago
Posts: 3159
 
Posted by: @heno

I took 8 sets (8 filters) of flats and dark flats using NINA's Flats wizard. I loaded them into APP to create master files. APP created the MDF as it should. But when APP started to create the MF, I got this critical warning. APP did not seem to recognize the MDFs it just created.

Calibration warning

But they were all there, image below. (This has in fact happened to me before!)

MDF

@heno, if all frames (flats and darkflats) were loaded correctly with the filter assignments then the warning should not happen provided that you use the latest APP version. Do you want me to test it? If so, upload a subset of frames of all 8 filters using the upload instructions on the top left of the forum and let me know once uploaded 😉

Mabula


ReplyQuote
 Heno
(@heno)
Red Giant Customer
Joined: 5 years ago
Posts: 114
Topic starter  

@wvreeven 
1.
There are 20 flats/dark flats pr. filter.
The exposure time (and gain used) may be different from filter to filter, but the same for each set (filter).
2.
I did not check that, is the log saved?
3.
I did not know that. This means that if I use MF there is no need to load the MDF for light calibration? I can delete them then. (I always take flats and dark flats together)


ReplyQuote
 Heno
(@heno)
Red Giant Customer
Joined: 5 years ago
Posts: 114
Topic starter  

@mabula-admin 
Thanks for your reply. This part (your first answer) is totally my mistake. Either I have forgotten to load the dark file or accidentally removed it. Not sure. And I did not read the error message carefully enough.
Sorry for wasting your time like this.


ReplyQuote
 Heno
(@heno)
Red Giant Customer
Joined: 5 years ago
Posts: 114
Topic starter  

@mabula-admin 
Regarding your second answer about creating the MF and MDF, I restarted my PC this morning just to be sure that everything was fresh and tried again with only one filter this time. I had no warnings.
When comparing the meta data for the MF I created yesterday and the one created today, they are identical down to the last digit. I can not tell them apart. 
I would have thought there had to be some difference if one MF was created without the use of an MDF? How would the numbers change, if at all?
I will create MFs the rest of the filters as soon as the current integration finishes. I will come back with the result.


ReplyQuote
(@wvreeven)
Galaxy Admin
Joined: 4 years ago
Posts: 1724
 
Posted by: @heno

2.
I did not check that, is the log saved?

It is not but you can inspect it before closing APP.

Posted by: @heno

3.
I did not know that. This means that if I use MF there is no need to load the MDF for light calibration? I can delete them then. (I always take flats and dark flats together)

Let me check with Mabula to be absolutely sure, but once the MF has been created you should be able to delete the MDF. On the other hand, if you often shoot flats at the same exposure time, temperature and gain you may want to store the MDF so you don't have to reshoot the dark flats.


ReplyQuote
(@wvreeven)
Galaxy Admin
Joined: 4 years ago
Posts: 1724
 

@heno I have checked and verified that the MDF indeed only is used for calibration of the flats when the MF is created. As soon as the MF has been created, APP no longer needs the MDF and you may do with it as you please, including deleting it.


Heno liked
ReplyQuote
 Heno
(@heno)
Red Giant Customer
Joined: 5 years ago
Posts: 114
Topic starter  

I just tried again, loaded up flats and dark flats + BPM for the remaining seven filters. It started out well as MF for blue and green were created without warnings. Then on Ha, Lum, OIII, Red and SII I had the same calibration error warning as yesterday. The MDF were all there.
If I'm doing something wrong, I have no clue what it is. This I have done a hundred times and I'm not doing anything different. And the MDFs looks fine to me.
I will upload the files, 10 of each for each filter.
The file name do not indicate which color the filters are, so here is an index:
Blue - 1.00s
Grn - 2,08s
Ha - 2,64s
Lum - 1,35s
OIII - 2,14s
Red - 3,36s
SII - 4,10s
The dark flats are the ones with (1) in the file name.
@mabula-admin For your info.

 

This post was modified 4 months ago 2 times by Heno

ReplyQuote
(@mabula-admin)
Quasar Admin
Joined: 5 years ago
Posts: 3159
 
Posted by: @heno

I just tried again, loaded up flats and dark flats + BPM for the remaining seven filters. It started out well as MF for blue and green were created without warnings. Then on Ha, Lum, OIII, Red and SII I had the same calibration error warning as yesterday. The MDF were all there.
If I'm doing something wrong, I have no clue what it is. This I have done a hundred times and I'm not doing anything different. And the MDFs looks fine to me.
I will upload the files, 10 of each for each filter.
The file name do not indicate which color the filters are, so here is an index:
Blue - 1.00s
Grn - 2,08s
Ha - 2,64s
Lum - 1,35s
OIII - 2,14s
Red - 3,36s
SII - 4,10s
The dark flats are the ones with (1) in the file name.
@mabula-admin For your info.

 

Hi Heno @heno,

Thank you for the upload, I will do testing this afternoon and will let you know my findings 😉

Mabula


ReplyQuote
(@mabula-admin)
Quasar Admin
Joined: 5 years ago
Posts: 3159
 

Hi Heno @heno,

I have used the latest version available at the top of the forum.

I have made the Masterflats twice without any issues.

1) first try, I have loaded the darkflats and used te filter tag to assign the filter name. All worked perfectly. In the console windows I verified that the correct MasterDarkFlats were used to calibrate the flats.

2) second try, I have loaded the darkflats for all channels. Still all worked perfectly... but there is a slight issue then with the exposure times. The exposure times of the O3 = 2,18s and Grn = 2,14 are so close, that APP will consider it the same exposure time. So in this case the O3 and Grn darkflats are combined into 1 MDF. But then that MDF is used to calibrate the O3 and Grn flats, which is perfectly okay since the gain matches and exposure times so close to each other will not affect the results. Dark current signal with those exposure time differences is simply the same...

So I can only assume that you might not be using the latest version?

Please see:

https://www.astropixelprocessor.com/community/release-information/astro-pixel-processor-1-083-2-ready-for-download/

Version 1.083 had a concurrency bug which would create your issue. But it was fixed in 1.083.2.

Mabula


ReplyQuote
 Heno
(@heno)
Red Giant Customer
Joined: 5 years ago
Posts: 114
Topic starter  

Hi Mabula @mabula-admin
Thanks for doing the testing and your response.
I checked the PC download folder and the I actually had downloaded 1.083.3. But I cannot be 100% sure if it was installed. So I have now reinstalled 1.083.3 just to be absolutely sure. (I also noticed that I can press the license button to see which version is running. Learning something new every day. 😀 )
So to your other responses:
1. This is what I always do. I did not know it could be done any other way.
2. If I understand this correctly, I can actually load dark flats and select "all channels" and APP will sort out which belongs which based on exposure time. That will save some time in the future.  

I'll go on with the calibration and let you know how it went.

EDIT:

Calibration finished without warnings, all good. Thanks!

This post was modified 4 months ago 3 times by Heno

ReplyQuote
Share: