
Siril's comet registration begins with star-aligned images and valid timestamps. Selecting the comet alone does not replace that prerequisite. The additional alignment follows the comet's motion relative to the star field, so a comet-bound stack and a star-bound stack represent different intended results.
Preserve the star-aligned starting point
Begin with calibrated photographs from the actual comet session and complete the appropriate star registration. Retain the original sequence and its registration record.
The Siril 1.4.4 registration manual permits the existing star alignment to be represented by exported images or saved registration data from supported methods. Confirm which representation the project uses before adding the comet shift.
Check the image timestamps. They are inputs to this motion relationship, not merely labels used to sort a gallery. Do not fabricate times to make an incomplete acquisition record appear valid.
Pick the same nucleus at the endpoints
In the comet-registration controls, select the first sequence image, draw a region around the nucleus and use Pick object in #1. Select the last image, surround the same nucleus and use Pick object in #2.
Inspect the actual selections carefully. A neighboring star or a bright tail feature is not interchangeable with the nucleus. The star-versus-hot-pixel guide illustrates why the identity of a small bright feature requires evidence.
This is a proposed setup, not a report that a comet was detected or tracked.
Keep both reference motions intelligible
The manual describes a new comet-prefixed sequence, composing the extra shifts with existing registration. Retain a clear distinction between that sequence and the star-aligned source.
Siril's comet tutorial treats star-bound and comet-bound stills as separate results. Choose the intended final framing and verify the selected reference rather than assuming every registration step preserves a prior reference choice.
If the comet is fixed, the distant stars need not remain fixed too. Do not judge that physical difference as though every depth and motion should coincide. The panorama-alignment limitation is another example of why one alignment objective cannot satisfy every recorded relationship.
Review the selected subject and disclose composites
Inspect the nucleus and tail in the completed comet-bound result, and compare any separately retained star-bound stack. Check framing and the intended motion across multiple source moments.
If composing the two results later, describe that construction honestly; this guide supplies no automatic blend that guarantees artifact-free stars and comet together. No registration, orbit determination, image measurement or final composite was performed here.
Related tasks
- Are the Bright Colored Dots in My Night Photo Stars or Hot Pixels?
- How Do I Repair a Panorama Stitch Without Duplicating a Building?
Sources and scope
- Siril 1.4.4: Registration — Comet/Asteroid registration: Comet registration requires existing star alignment and image timestamps. Pick the nucleus in first and last frames; Siril derives motion and generates a distinct comet-prefixed sequence whose shifts compose with existing registration.
- Siril: Working with Comets: Star-bound and comet-bound stacks are separate intended results; choose framing intentionally and preserve the chosen reference after global registration.
Official Siril documentation was opened and read on October 23, 2026 (Asia/Shanghai). Versioned references identify 1.4.4; legacy StarNet controls are explicitly distinguished from the newer 2.5 Python integration. Acquisition, registration, processing and acceptance checks are proposed, not performed. The cover is decorative.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: 85 LENS (Ngô Hoàng Auth) / Pexels, Pexels License. This is an illustrative source photograph, not an application screenshot or a generated test result.