I took a stab with my over powered Sky-Watcher Evoguide 50 ED. No guiding, just siderial tracking. I took 60s exposures. About 100 of them. WBPP, then stripped the stars and ran comet alignment. I came back and integrated 4 or 5 with stars to make a star layer. Cool target. Nice to see all the different approaches and equipment being used.?
On Mon, Jan 30, 2023, 1:48 PM Brian Valente <bvalente@...> wrote:
Hi folks,
Another ZTF from sunday
oxut9p/
It's interesting to see how the comet is evolving.?
A few interesting?notes:
- i switched to a tak Sky90 w/ reducer for 407mm focal length. Based on this image, it seems like a good wide focal length is needed to get the tail
- I had terrible TERRIBLE focus. There is a problem with my image train but the stars were huge and blobby. Fortunately BlurXterminator saved this session?from the scrap heap, but i am working on this now (probably some additional backfocus spacing). I am hoping to revisit this whole setup including the horizons feature (described below) for sharper results?
- I tried tracking the comet using the Orbitals plugin to set the tracking rate and the guider rate (phd) and then used SGP for imaging. Not the best plan: Orbitals does continuous rate adjustments so it's less useful when using it just to set the rates. Next time I use Orbitals, I'll do the imaging in NINA as well
- I also tried tracking the comet in the new Horizons integration in Gemini Telescope.net, with mixed results (mised results were?my fault). First, I used the new feature to slew to the comet, which worked perfectly.? I then manually off-centered the comet to get more of the tail, and then started tracking in the Horizons screen. However, PHD guiding immediately stopped, reporting the telescope was slewing. I believe (Paul K?) Horizons tracking may sometimes look like slewing, and what I should have done was disable PHD2's option "stop guiding on slewing" but I forgot that option.