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.
I have not figured out yet how to combine two nights data since the flats will have the same times and the Dark will have the same times. Can I take a finished integration from Monday and a finished integration from Tuesday and integrate them together being of the same ISO and exposure time time, just different flats and darks...same bias and bpm?
Yes, you can just integrate two or more already stacked integrations to combine each evenings data.
My image in the gallery of M 42 and Running Man is the result of integrating two nights work of data using the stack created for each night.
Thom
Thanks Thom. I think I had different dimensions on my Integrations cuz I cropped one a little bit. I'll try again with unaltered dimensions.
Hi @gregwrca and @thompeters,
Yes you can integrate the data of different sessions by integrating the stacks from those sessions.
But, it is recommended to register and integrate all calibrated frames all at once for the best result.
If I have data shot at several nights, with different flats and darks, I always first calibrate all frames per session and then load all calibrated frames and proceed from there in 3) Analyse stars.
And... frames that have different dimensions shouldn't be an issue to be able to register and/or integrate 😉
Cheers,
Mabula
OK, thanks. Not sure what went wrong then. I will try again using kappa .03 and register with triangles, as there aren't many stars in the set.
@gregwrca, if the starcount is below 250, use triangles indeed 😉 let us know if it works now.
Mabula
Mabula,
i had not read the recommendation of using triangles for registration before.
Are there any other recommendations for frames with small star counts (ie <250) ?
I guess I need to change my work flow.
The default of quadrilaterals, or quads, is fine in almost all cases. Triangles can only become a real requirement with less than 100 stars usually.
If registration works fine with quads and low star counts, there is no need to use triangles instead of quads. Quads are more robust so recommended but they do have increased calculation time. Which you can easily test by running registration with triangles versus quads.
So the choice between triangles, quads, pentagons depends on how registration is working and the amount of stars. Pentagons are normally only needed with huge amounts of stars, like 5000+.
I use quads in almost all data, also in mosaics.
Triangles are what DSS, I believe, does and is only well-suited for very low star counts.
Mabula
