Improvements to Live Stacking
Posted: Mon Jul 01, 2024 2:27 pm
Hi folks,
this week I have added some improvements to live stacking, with hopefully more to come over the next few weeks.
UnStack in Live Stacking
The first new thing is the 'Unstack' button which I have added
This button will remove the most recently added frame from the stack, allowing a frame that perhaps introduced a satellite or aeroplane trail to be eliminated. Unstacking a frame should be exact for 'Default' stacking, although it is not perfectly exact for 'Sigma Clipped' stacking. Unstacking is not available when using the Max Value/Meteor Detection stacking mode.
The unstack button becomes available when
* At least 2 frames have been added to the stack
* The most recent frame was aligned correctly and added to the stack
* SharpCap has not yet begun adding the next new frame to the stack.
You will notice it disable as SharpCap starts to process a new frame for stacking and then become enabled again once the processing is complete.
All feedback welcome - I realise it would be nice to be able to go back further into history and unstack a frame from longer ago - it's not impossible, but it is much more complex, so I thought that this would be a good starting point.
Live Stack auto-save options
This one is very simple - there are now settings in live stacking to allow you to control what stack formats are saved when the 'Auto Save' feature of live stacking happens.
By default, the ones shown above will be saved - 16 bit stack and with adjustments. You can customize this as needed.
Frame-to-Frame drift info
Finally, I've added some info to the live stacking drift graph that shows how much the image had drifted between the most recent frame and the one before that...
The range of values is because when there is some rotation included as well as just a linear offset, the distance varies from one part of the image to another. For good images, this value should generally be small when compared to the star FWHM value. I did some quick tests and a drift of 1/2 of the FWHM gave noticeably stretched stars, while a drift of less than 1/4 FWHM showed little distortion to star shape.
I am planning to improve this in a later update - perhaps a graph showing the drift size/direction in different parts of the frame and a warning if the drift is large compared to the FWHM.
Note that if a dither occurs between two frames then a high value would be expected (the value shows the size of the dither) and in that case it's not a problem...
cheers,
Robin
this week I have added some improvements to live stacking, with hopefully more to come over the next few weeks.
UnStack in Live Stacking
The first new thing is the 'Unstack' button which I have added
This button will remove the most recently added frame from the stack, allowing a frame that perhaps introduced a satellite or aeroplane trail to be eliminated. Unstacking a frame should be exact for 'Default' stacking, although it is not perfectly exact for 'Sigma Clipped' stacking. Unstacking is not available when using the Max Value/Meteor Detection stacking mode.
The unstack button becomes available when
* At least 2 frames have been added to the stack
* The most recent frame was aligned correctly and added to the stack
* SharpCap has not yet begun adding the next new frame to the stack.
You will notice it disable as SharpCap starts to process a new frame for stacking and then become enabled again once the processing is complete.
All feedback welcome - I realise it would be nice to be able to go back further into history and unstack a frame from longer ago - it's not impossible, but it is much more complex, so I thought that this would be a good starting point.
Live Stack auto-save options
This one is very simple - there are now settings in live stacking to allow you to control what stack formats are saved when the 'Auto Save' feature of live stacking happens.
By default, the ones shown above will be saved - 16 bit stack and with adjustments. You can customize this as needed.
Frame-to-Frame drift info
Finally, I've added some info to the live stacking drift graph that shows how much the image had drifted between the most recent frame and the one before that...
The range of values is because when there is some rotation included as well as just a linear offset, the distance varies from one part of the image to another. For good images, this value should generally be small when compared to the star FWHM value. I did some quick tests and a drift of 1/2 of the FWHM gave noticeably stretched stars, while a drift of less than 1/4 FWHM showed little distortion to star shape.
I am planning to improve this in a later update - perhaps a graph showing the drift size/direction in different parts of the frame and a warning if the drift is large compared to the FWHM.
Note that if a dither occurs between two frames then a high value would be expected (the value shows the size of the dither) and in that case it's not a problem...
cheers,
Robin