UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred  after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Â Before I release it, I will make sure that everything is working properly and then I will release it.
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
Â
Â
