Re: Gemini 2 response to pulses that are smaller than minimum
|
>>>
I think that the hardware will ignore the shorter than minimum pulse.
Yes, and Paul did a good job of summing it up
One other thing to keep in mind is if your guiding is issuing these tiny pulses that are below the Gemini threshold, chances are your min moves are too small. you are almost certainly chasing seeing?at that point
On Thu, May 20, 2021 at 10:36 AM Paul Kanevsky < yh@...> wrote: There's no queuing of pulse guide commands. If a request is too small to result in movement, the mount will ignore it. Should the error continue to grow and exceed the minimum correction size, the pulse guide command will be processed and the position corrected. In effect, this acts as a low-pass filter, ignoring smaller, quick corrections which may sometimes be a good thing (ignoring seeing effects or small worm imperfections / dirt, for example).?
Regards,
? ? -Paul
On Thu, May 20, 2021 at 01:22 PM, Stephen Migol wrote:
There is the additional question of what happens with the guiding software.? If it sees that the shorter pulse change hasn't been made, it will make the request for movement based on the next measurement.??
If the hardware and the software will queue and sum pulses, then there's a potential for overcorrection.
I think that the hardware will ignore the shorter than minimum pulse.
Stephen
-- Brian?
Brian Valente portfolio
|
