15th Feb 2024: Astro Pixel Processor 2.0.0-beta29 released - macOS native File Chooser, macOS CMD-Q fixed, read-only Fits on network fixed and other bug fixes
7th December 2023: added payment option Alipay to purchase Astro Pixel Processor from China, Hong Kong, Macau, Taiwan, Korea, Japan and other countries where Alipay is used.
I am running into a problem performing 1-star comet registration on two different image sets from the same night.
I use a barn door tracker. It can track for about 30 - 45 minutes. After that I have to reset/rewind, resume tracking, and recenter the camera on the comet field. The delay is only a few minutes of time, but the second image set is offset (and slightly rotated) compared to the first image set.
If I try to register all images in APP, the resulting integration stack will have a double comet nucleus, and the double star trails show that there is also a slight angular misalignment. Somehow the software does not appear to be properly keeping track of the registration changes in the second set of images.
As a workaround I am performing normal (multi-star) registration on all images, saving those registered (and normalized) images, then registering again using comet/1-star mode, then performing final integration.
Am I using an incorrect workflow? Am I asking APP to try to do too much at once?
(First attached image shows final integration result after using the workflow method I described above. You can see the shift/rotation difference between the two image sets. Second image is a final integration of about 175 frames of comet 104P Kowal from last night.)
Thank you in advance,
Tom Krajci
New Mexico
I did a quick double check of my comet image workflow on a small sample of images.
This shows the integrated result after using comet/1-star registration on three different image sets from the same evening. You can see there are differences in positioning and rotation of the camera frame.
But a close look at the final stack/integration shows:
...the comet images are not accurately registered, so the nucleus is triple. Also, the stars do not show motion in a straight line between the three image sets, so there is also a problem with keeping track of the necessary rotation for proper registration.
At the present moment my workflow is to calibrate and register all frames using normal registration...save these registered (and normalized) frames...clear/reset/restart APP and then register all these frames using comet/1-star registration.
I think we can do the same question with the data I already asked for you to upload. 🙂
