BadPixelMap for two...
 
Share:
Notifications
Clear all

BadPixelMap for two cameras


(@batch)
Hydrogen Atom Customer
Joined: 3 years ago
Posts: 3
Topic starter  

When Calibrating and Integrating Subs from Multiple Sessions and using Two Different Cameras how do I load a BadPixelMap for each Camera? If I load two BadPixelMaps will APP differentiate  between them and assign them to the correct camera and the proper corresponding Session?

 

Thanks


ReplyQuote
Topic Tags
bpm
(@vincent-mod)
Quasar Admin
Joined: 5 years ago
Posts: 4723
 

You want to make that data in 2 sessions then and assign one bpm to 1 and the 2nd bpm to the other camera.


ReplyQuote
(@batch)
Hydrogen Atom Customer
Joined: 3 years ago
Posts: 3
Topic starter  

Hi Vincent,

Yes that's what I would like to be  able to do.

The actual project that I am working on consists of three sessions of NB data from 2018 taken by camera A that I would like to combine with two sessions of NB data captured in 2020 from camera B. When calibrating the data I can load master flats, bias and darks seperatly for each camera (or session) but it appears that I can only use one BadPixelMap and it is then applied to all sessions (clearly not useful for one of the cameras).

Bill


ReplyQuote
(@vincent-mod)
Quasar Admin
Joined: 5 years ago
Posts: 4723
 

Is it? I must say I have not done a lot of multi session processing, but that's exactly why that would be the way to go, you can't assign the bpm to a session? (if not, I'll ask Mabula straight away). 😉


ReplyQuote
(@vincent-mod)
Quasar Admin
Joined: 5 years ago
Posts: 4723
 

Ah you're correct, just tried myself. Let me get back to that.


ReplyQuote
(@vincent-mod)
Quasar Admin
Joined: 5 years ago
Posts: 4723
 

Ah ok, got an answer back. It should automatically assign the BPM to the correct sensor. If the dimensions of the chip are exactly the same, the capture software should add the name of the sensor to the header, otherwise APP wouldn't know indeed. Basically it would recognize the darks for another camera then also automatically like that. Sessions are more for the same sensor, with different calibration files for that session of that sensor.


ReplyQuote
(@batch)
Hydrogen Atom Customer
Joined: 3 years ago
Posts: 3
Topic starter  

Ok, but in my case the sensor size of the two individual cameras are exactly the same and I cant see any differentiation between the two in the FITs header. Wouldn't it be easier to treat the BPM in the same manner as the other Master calibration files and simply designate what sessions you want each BPM to apply to?

 

What I have done as a work around is to calibrate each camera group seperately, save the calibrated subs and then reload both groups for registration and integration. This seems to work but adds a couple of additional steps and time to what is an otherwise wonderful and fully automated process. 


ReplyQuote
(@ippiu)
Red Giant Customer
Joined: 3 years ago
Posts: 132
 

I'm interested too in this possibility, that is: let me choose to add and assign each BPM freely to each corresponding session, as i normally do with all other calibration files...

Thanks Mabula if you can do this 


ReplyQuote
(@vincent-mod)
Quasar Admin
Joined: 5 years ago
Posts: 4723
 

Yes, when the sensor is exactly the same in dimensions and no name is given (you may have a look if the capture software can provide that, normally they should) the best is to process that data separately. It might be interesting to see if this can be changed somehow.


ReplyQuote
Share: