It has a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration, for mosaics even faster! 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. Improved Outlier Rejection with LN 2.0 rejection. macOS CMD+A works now in file chooser ! And more, all will be added to the release notes in the coming hours...
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.
Hi! New to APP - have successfully used to mosaic stacks processed and flattened in DSS/FITSWORK. However now trying to start from raw images, darks,flats.
See the attached - the flat is a fully calibrated flat (ie already stacked with flat darks) Master from DSS that I have dropped in. I dont use biases - recommended against with CMOS.
Im concerned that the flat has a 'D' against it, which suggests that the dark frame (also a Master stack from DSS) will be used with it, which would be disastrous. Can someone explain if this is the case, and if so how to prevent it?
I also find it odd and troubling that I cant upload flat darks into APP; does APP expect me to use biases or the same darks with flats?
Hi! New to APP - have successfully used to mosaic stacks processed and flattened in DSS/FITSWORK. However now trying to start from raw images, darks,flats.
See the attached - the flat is a fully calibrated flat (ie already stacked with flat darks) Master from DSS that I have dropped in. I dont use biases - recommended against with CMOS.
Im concerned that the flat has a 'D' against it, which suggests that the dark frame (also a Master stack from DSS) will be used with it, which would be disastrous. Can someone explain if this is the case, and if so how to prevent it?
I also find it odd and troubling that I cant upload flat darks into APP; does APP expect me to use biases or the same darks with flats?
Thank you for your question and welcome to the APP forum 😉
See the attached - the flat is a fully calibrated flat (ie already stacked with flat darks) Master from DSS that I have dropped in. I dont use biases - recommended against with CMOS.
That's fine 😉
First of all, let me point out that using masterframes from other applications can be a recipe for problems (especially for DSLR data). If you have the original calibration frames, I would recommend to use those as a starting point in APP for data calibration. If you only have the masters then we need to work with that.
Yes, the D next to the flat, means it will subtract a matching masterdark from the flat. I can't see everything of the frame list, so I don't know what else is there.. but I think the dark was converted to a masterdark and then that would be matched to the flat because it has the same iso/gain and exposure as reported by metadata. And that's because the metadata of the DSS masters is insufficient.
What you will need to do to fix this:
1) clear the frame list.
2) only load your DSS masterdark as dark. Let APP create a MasterDark for APP from it by clicking calibrate.
3) clear the list again.
4) only load your DSS masterflat as flat. let APP create a MasterFlat for APP from it by clicking calibrate. Since this master was created properly by having subtracted dark flats like you indicate, this should be fine.
5) Then clear the list
6) load your lights, and the APP Masterdark and Masterflat. That should be it 😉
I also find it odd and troubling that I cant upload flat darks into APP; does APP expect me to use biases or the same darks with flats?
APP 1.059 and lower can perfectly address flat darks. Just realize that a flat dark is just a dark for a flat, you should load them as darks. The masterdarkflat created will be matched with the flats if they have the same exposure and ISO/gain as the flats.
(I do this all the time with my ASI1600mm-cool, for the reason that you give)
But, APP 1.060 (which I am working on right now), will have a separate dark flat load button and will also create a MasterDarkFlat, so that will be easier. And the matching of masters to lights and flats will be much easier and transparant.
Currently, the calibration rules demand that a masterdark is only applied if it has the same exposure and ISO/gain value. That will no longer be the case in APP 1.060 and it will also include dark scaling 😉
Let me know if this answers your concerns and questions.