Closed ExoClock-adrian closed 1 year ago
LeonBew
commented
1 year ago I've experienced the same alignment and IndexError with a few transits since updating to 3.1. On another machine where 3.0 is still installed, the same images work fine. Though I haven't yet tried deleting the first image as Adrian has.
atsiaras
commented
1 year ago Hopefully fixed in v3.1.1 - I will keep this issue open until you confirm it has been fixed.
ExoClock-adrian
commented
1 year ago Hi Angelos.
The alignment problem I reported does not occur in V3.1.1 with the same data 🙂.
Adrian From: Angelos @.> Sent: 12 April 2023 10:03 To: @.> Cc: @.>; @.> Subject: Re: [ExoWorldsSpies/hops] HOPS Alignment (Issue #19)
Hopefully fixed in v3.1.1 - I will keep this issue open until you confirm it has been fixed.
— Reply to this email directly, view it on GitHubhttps://github.com/ExoWorldsSpies/hops/issues/19#issuecomment-1504918093, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A45GQGS3B6A3KO35YGXHILTXAZVUXANCNFSM6AAAAAAVPHEZTI. You are receiving this because you authored the thread.Message ID: @.***>
HOPS stalled at start of Alignment ('Choosing calibrating stars'.) No stars are selected and progress remains at 0%. Required a forced exit from command log. Log shows an IndexError.
I tried deleting the first image file in the sequence and the problem did not occur. The only significant difference between first and second images I could see was a small patch of saturated pixels (cosmic ray?) around position (2407,1068) in the first image. When I restored the first image with the defect cloned out, the problem did not occur. Image (as JPG) and HOPS log attached.
HOPS log.txt