Yes, this.
OK, thanks! Might be nice to limit the end date, but this does get at what I want to achieve.
A mosaic sensitive AF option would be useful.
It would be an option that turns off the AF routine when centering between targets of a mosaic sequence of the same object (ie. small moves) but maintain AF when centering on a new object (ie. large move). This would be especially useful eg for SCT’s that suffer from mirror shift after large movement of the scope but not necessarily after very small movements and when your sequence includes several objects among at least one is a mosaic.
One feature I’d find useful is an option to set the Image History panel to show FWHM in arc-seconds instead of HFR. I’d like to be able to use that graph to track seeing over time and FWHM correlates directly to seeing, while HFR does not.
I know that changes in focus over time will also affect both HFR and FWHM, so it would not always be an accurate representation, but regular autofocusing would take care of most of that.
It would be great to be able to set up a “seeing monitor” sequence in SGP to use just for keeping track of changes in seeing over time. Using FWHM in Image History would be a way to do that.
2 Likes
Thank you for the opportunity to make suggestions. Here are my thoughts.
- The ability to capture a certain amount of subs (time frame) of a certain quality. HFR is your current measure, but SNR, eccentricity etc. should also be considered. Performance tradeoff’s of course need to be considered.
- For people with manual rotators and OAG;s, the ability to talk current angles directly with PHD2. I expect that the accuracy we now get via plate solving is far greater than the PHD2 calibration process.
- The speed of plate solving is to the point that you can run it after every frame and rectify if out by more than your plate solving error. Use the image you just captured whilst dithering / settling.
- The new dark theme is great, much appreciated, but an image from framing and mosaic wizard object leaves white borders to the left and right with my setup. An actual captured image was fine. This was a sequence from 4.0. Dark theme should equal black borders.
- Splitting the job queue functionality out of the sequence. The ability to have a number of sequences active based on time, elevation limits etc. Data from each target can go into separate directories. The ability to add / edit targets whilst a sequence is active.
- Given everyone has a smart phone in their pocket, a phone app to drive / keep tabs on SGP remotely
Hope some of these are of interest. Please keep up the great work.
I forgot one.
7. Auto exposure length option based on target and conditions.
You already calculate the ideal exposure time, making this an optional input into sequence exposure (maybe even the default) will help beginners get up to speed. Auto rather than 0 being the default exposure value.
Experts will select their exposure time manually in exactly the same way they do currently.
You already have a process in getting the ideal ADU for flats, repurposing a version of that for auto exposure maybe the way to go.
The more smart defaults the better.
Just a comment on your #6. I use an app called GNS (for Good Night System) that is supported natively in SGP’s notification system. So my phone app monitors the progress of my sequence, lets me know how its progressing, and notifies me of errors or warnings generated by SGP. It can set to wake you up if the situation warrants. It also has a heartbeat signal from your imaging computer to your phone app so it will alert you even if SGP dies, or if your computer crashes or goes up in smoke. It’s published by Lunatico Astronomia.
1 Like