Hmmm, I did war and peace again and deleted it after reading your post one more time as it really wouldn't answer your questions.
First up, Voyager won't do planning for you in terms of suggesting sub lengths per target, I don't know what software does that? I find my ideal sub lengths empirically by test shots on target, sticking to regular lengths (I.E. 30-60-120-24-300 seconds) shooting more than one length if required for really high dynamic range targets like M42. One length giving around 1000 saturated pixels per sub, and a longer one for the faint stuff. Normal targets I will just pick the approx 1000 saturated pixels and go.
Regards the 30 minute block time allocation strategy. I would not necessarily call it "Better" as that is subjective, but Voyager Advanced is going to do it very differently. It sounds like you are breaking up your 30 minute chunks to shoot different filters based on target location and moon distance (Dependant on phase)
To tackle moon distance and phase first, that is covered by the moon avoidance Lorentzian constraints (And why I create LRGB/HA-Sii and Oiii versions of the target, to make use of different Lorentzian settings) and you can be more explicit and set up discrete "Moon down" and "Moon up" constraints to force LRGB only when the moon is down, and NB only when it is up.
As to position of the target, the constraints you set per target do that for you, though it will probably be the same in terms of hour angles target after target. I prefer hour angle to altitude given it is constant regardless of declination but if you have an unfavourable horizon to the south east as an example you can use a custom horizon so that if a target would fall into your hour angle constraint but be blocked by a building or other obstruction, it won't be shot until it clears it.
The Voyager advanced way is rather than trying to actively schedule the imaging run in discrete blocks night by night, just set up your constraints, set how many subs per filter and how many repeats then set it going.
|