Closed dentalfloss1 closed 8 months ago
I see this in the lwana
branch at https://github.com/lwa-project/orville_wideband_imager/blob/lwana/orville_imager.py#L1236.
Is this a North Arm-only issue or is it also affecting Sevilleta?
It looks like it currently is not affecting Sevilleta because we are now storing int_len in days at Sevilleta: [cid:3ac02599-7f5d-4159-8b06-e8ded94f4814]
From: jaycedowell @.> Sent: Tuesday, March 26, 2024 1:05 PM To: lwa-project/orville_wideband_imager @.> Cc: Sarah Chastain @.>; Author @.> Subject: Re: [lwa-project/orville_wideband_imager] file_end sometimes wrong (Issue #20)
[EXTERNAL]
I see this in the lwana branch at https://github.com/lwa-project/orville_wideband_imager/blob/lwana/orville_imager.py#L1236.
Is this a North Arm-only issue or is it also affecting Sevilleta?
— Reply to this email directly, view it on GitHubhttps://github.com/lwa-project/orville_wideband_imager/issues/20#issuecomment-2021259376, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AF35E62TPPZYCEHIUHQM5FTY2HBHRAVCNFSM6AAAAABFJLNRDKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRRGI2TSMZXGY. You are receiving this because you authored the thread.Message ID: @.***>
Great, I've deployed the fix for North Arm.
On some archival oims files, the file_end date is well after the file should have ended. As the screenshot below shows, it appears that on these files, we are getting confused about the units used in "int_len"