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.
Did you ever come back to a project, days later, and wonder what options you picked in order to get where you ended up (or left off)? Or want to reproduce successful steps exactly in later runs (or for support...)?
I'd like a log of the choices I make (explicits and defaults), in the current working directory, with a timestamped filename, so one run does not overwrite the other. If you want to send exceptions to it, that would be a nice-to-have, but this is about capturing workflow choices.
This cannot be done by redirecting the APP startup command, as the working directory is not known at start time, and in any case, such a log would be filled with java chatter and not focused on workflow options that the user has followed. Output redirection as a means of capturing errors has its place, but this is not about that - it's about making it easier to reproduce steps taken, at a later date.
For an example of such a *functional* log, have a look at Ivo's StarTools. You can pick up one of his logs and reproduce workflow steps very easily, because that's the focus. That's the functionality I'm looking for...
Thanks!
- Bob
Until we get the ability to save projects your suggestion would be helpful. Send the logs to the working directory.
Time and date stamp each log.
Â
Â
Yes that would be nice, also, the steps you took are in the FITS header information now. So some of that info is saved there.
Is the FITS header what's shown to the left of the current image?
I did some playing around with changes and while I can see that there's some indication of what's gone on before, it's not a functional log - something that you'd use to reproduce steps taken. ALL of the steps - user pushes a button, moves a slider, etc.
There's more than one way to do this. Could be a simple log of steps as they happen (lots of chatter, but simple to implement). Could be summary-of-net-changes-on-save. Harder to implement, because the user may go back and forth and you'd have to keep track and net out, but if accurate, better for the user.
Anyway, the point of it all would be to log functional steps taken, so they can be reproduced , either by the user, or for support, capturing the session's workflow.
HTH...
- Bob
Â
Â
