Flats and darks don...
 
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.

 

Flats and darks dont seem to be working

7 Posts
2 Users
1 Reactions
1,974 Views
(@gmehal)
Main Sequence Star
Joined: 7 years ago
Posts: 23
Topic starter  

I have been trying to process this image using flats darks dark flats and bias frames. It seems like Astro pixel processor is not using those frames for the final image. I have done a test where I used just the light frames, Then I would add the flat frames to another integration, then add the darks etc. each image looks exactly the same when integrated. Is there a setting or something that I missing? You can see by the image titles which images are which. Just seems like adding flats and darks don't seem to make any difference in the final integration.  Last image is one of my flat frames and the one with the boxes is the light pollution correction with darks, flats, dk flats and bias frames integrated.

ngc 6914 test all St
ngc 6914 test dkflat St
ngc 6914 test dark St
ngc 6914 test flat 1 St
Screen Shot 2021 09 04 at 8.35.54 AM
Screen Shot 2021 09 04 at 8.33.45 AM

 


This topic was modified 5 years ago by gmehal

   
ReplyQuote
(@wvreeven)
Quasar
Joined: 8 years ago
Posts: 2134
 

@gmehal If you first only integrate the lights and then add the calibration frames, you cannot go straight to tab 6 and click integrate. You need to go through all the tabs and click the buttons for each processing step. Can you do that and verify that that solves your issue?

Another thing you can try is to start APP and load all frames in tab 1 and then go to tab 6 and click integrate. That should show that APP indeed does use the calibration frames. 



   
ReplyQuote
(@gmehal)
Main Sequence Star
Joined: 7 years ago
Posts: 23
Topic starter  

@wvreevenI will try both methods now.  Will report back shortly



   
ReplyQuote
(@gmehal)
Main Sequence Star
Joined: 7 years ago
Posts: 23
Topic starter  

@wvreevenLooks like that did the trick! Adding all images and then integrating. Im still getting registration errors using 1.83b2.  When I increase star registration to 1500 it works.

Screen Shot 2021 09 04 at 9.46.04 AM

 



   
ReplyQuote
(@wvreeven)
Quasar
Joined: 8 years ago
Posts: 2134
 

@gmehal The star registration occasionally shows a glitch in 1.083-beta2 and Mabula is working on a fix. Please try 1.083-beta instead and see if that solves this error for you.



   
ReplyQuote
(@gmehal)
Main Sequence Star
Joined: 7 years ago
Posts: 23
Topic starter  

@wvreevenyou mean 1083-b1. correct?



   
ReplyQuote
(@wvreeven)
Quasar
Joined: 8 years ago
Posts: 2134
 

@gmehal Yes, that's the one.



   
gmehal reacted
ReplyQuote
Share: