PI says I have a non-empty processing history even though I saved it

[Nocturnal]

Hi,

before closing my image I open the history explorer, drag a new instance to the workspace and save the work space icons. When I then close the image it warns me that my processing history is not empty and not saved. How should I save this processing history so it stays associated with the image? I believe this is the project concept we talked about before but it seems I'm missing something here. I really want to save the image and processing history together so that I can open them together and proceed where I left off. Right now that does not appear to be possible but I hope I'm wrong.

Thanks,

  Sander

[Juan Conejero]

Hi Sander,

How should I save this processing history so it stays associated with the image?

Unfortunately, you can't, *for now*. Yes, you can check the "don't tell this anymore" thing to shut it up. But, of course, you don't want to do so because you know that you can lose invaluable data if you close an image without saving its processing history...

I really want to save the image and processing history together so that I can open them together and proceed where I left off.

Rest assured that this will be implemented. It's the PixInsight Document Format (or whatever it will be called) that we have to implement. With this format, you'll be able to save a set of images with their processing histories, masking relations, process icons, workspace state, etc.

I want to be very careful in designing and implement this new format, because it is very important. I don't want to make too horrible / too numerous mistakes. The platform is mature enough as to start working on this right now; It's just that I want to be less stressed to be able to think more efficiently. As I said in the other forum, I look forward to know about any opinions and suggestions regarding this important topic.

For now, you just have to be very very careful in saving your .psm files

[Nocturnal]

Hi Juan,

ok, another reply I missed Good to know I'm not missing when I wonder about that warning message.

Let me think a bit more about that document format. For now all I want is:

- original image
- current image
- processing history

Then when I process the image further the processing history gets longer. That's the biggest issue with the current psm strategy. As far as I can tell you can't associate a psm with an image without reapplying all those operations. That means you can't append operations to a psm except by creating a new psm and dropping it in the old one. That's cumbersome.

Ultimately I'd like the option of having a true processing Time Line. A sequence of images with processing steps in the middle. That way I can go back to a certain state, tweak a processing parameter in the next step and let the rest ripple through, updating each image along the way. I think that's close to the holy grail of image processing management. Sure it takes up some storage space and some options to prevent intermediate images from getting stored would be needed for lower resource machines.

In my other message I said I need to review the history explorer. From your description I think it does some or all of this except the saving in a single file part