Improvements to SUSPEND

[s3igell]

A couple of suggested Improvements:

 

1) Display the Image Count (Image Progress Count - "## of ##") during a "Suspend", so that the User can determine how much of the current Image Plan remains when deciding whether to "Resume" or "Abort".  It would be even better if the Estimated Completion Time were updated and displayed during a "Suspend" - again so the User can best determine whether to "Resume".

 

2) Add the ability to "Abandon" the Current Exposure yet continue along the current Image Plan.  It is unfortunately too common that an Airplane will fly through the FOV; or that a Car's Headlights (Taillights, Dome Lights, etc) will intrude into an Imager's setup; or even a Curious Star Partyer will pop a Smartphone Flash or Flashlight on your Imaging Rig.  You KNOW that your current Exposure is Ruined, but you only have the choice to either "Suffer Through the Exposure" or "Abort the Whole Capture Plan".  Provide a third option:  "Abandon the Current Image" and Repeat the Current Exposure of the Capture Plan.  The Abandoned Exposure would still need to be Downloaded in order to keep the SDK Workflow, which could then either be either Processed and Renamed as "Abandoned" or outright Deleted.

[astroman133]

I like your "Abandon" suggestion...great idea!

 

Since you are posting suggestions for improvements to the capture plan, here are a couple of others:

 

 

1) while the capture plan is paused, allow the user to switch to Frame and Focus and use typical techniques (LiveView or Snap images) to adjust focus, then return to Imaging and resume the capture plan.

2) allow changes to the capture plan itself while imaging is paused, specifically to adjust the number of exposures. This would allow the user to extend the plan to capture additional exposures as replacements for known bad (DELETED) images.