BPM for lights with...
 
Share:
Notifications
Clear all

Mar 28 2026 APP 2.0.0-beta40 will be released in 7 days.

It did take a long time to have the work finished on this and it  will have a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration. We extensively optimized many critical parts of APP. All has been tested to guarantee correct optimizations. Drizzle and image resampling is much faster for instance, those modules have been completely rewritten. Much less memory usage. LNC 2.0 will be released which works much better and faster than LNC in it's current state. And more, all will be added to the release notes in the coming weeks...

Update on the 2.0.0 release & the full manual

We are getting close to the 2.0.0 stable release and the full manual. The manual will soon become available on the website and also in PDF format. Both versions will be identical and once released, will start to follow the APP release cycle and thus will stay up-to-date to the latest APP version.

Once 2.0.0 is released, the price for APP will increase. Owner's license holders will not need to pay an upgrade fee to use 2.0.0, neither do Renter's license holders.

 

BPM for lights with different exposure lengths

3 Posts
3 Users
0 Reactions
2,998 Views
(@chrismarshall800gmail-com)
Brown Dwarf
Joined: 8 years ago
Posts: 3
Topic starter  

Hi Mabula

Using APP 1.061 and getting great results. I have a query about creating BPMs

Can a BPM created with darks of one exposure time be used on lights of a different exposure time? Or should I create separate BPMs using darks of say 300s and 600s to match the corresponding lights. I notice that the header data, using hot pixel kappa=3.0 and cold pixel %=25, give %HPs of 0.3 and 0.9 respectively for 300s and 600s darks.  Is this a reasonable level for my ZWO ASI071C? Certainly the visual number of hot pixels seems quite a bit less than in the BPMs.

Also do I need to match the sensor temperature when creating BPMs to the lights I will use them on

Many thanks

Chris Marshall

 



   
ReplyQuote
(@Anonymous 174)
Joined: 9 years ago
Posts: 5702
 

A Bad Pixel Map can be used for all your data and for a very long time as well. No need to match anything.



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5056
 

Hi Chris @chrismarshall800gmail-com,

Indeed, like Vincent @vincent-mod indicates, simply create 1 effective Bad Pixel Map using a nice set of darks and flats and you will be able to use it on all your data shot with the sepecific camera.

You can see the Bad Pixel Map as a map of how the sensor in your camera works. It's not dependent on a ISO/gain value and not on exposure time.

To create the Bad Pixel Map, you will get better results if you use:

  • more darks
  • longer exposure times
  • higher temperatures

The goal is to get good statistics on the linearity of the pixels on your camera's sensor. With more darks, longer exposures, and higher temperatures, you get better statistiscs 😉

Kind regards,

Mabula

 



   
ReplyQuote
Share: