Identify expected echelle data in a given week

[planetarymike]

We need a process or ideally automated routines to identify the echelle data that is expected in a given week, in order to identify data gaps.

Some ideas:

• Use planning file (PEF) --- justin knows how to access and read these
  • These are not always reliable as segment cutoffs can prevent alternation in the standard / echelle grating change, for example
• Automate reading / comparison with integrated report
  • Mike has some helper routines to do this he made for the IUVS H Lyman alpha quicklooks
  • This would enable automatic identification of missing frames due to segment cutoffs
  • Issue: the integrated reports often lag the data by a week or so, preventing day-by-day accuracy of any routine expecting them to be complete

[planetarymike]

According to Dale,

Delivered-To: michael.s.chaffin@gmail.com
Received: Mon, 17 Apr 2023
Subject: Re: Apr 17 Echelle Report

Hi Mike,

Sounds good, there should be a way to see if an image set is cut off by comparing the time between the img_init command and the end of the segment against the duration of the imaging set.

You are correct that the frames with missing data are due to the usual segment cutoffs. The IB and OB cutoffs tend to be consistent (here, 7 & 8 of 8 missing in all cases), sometimes with a slow progression of change. RELAY is, unfortunately, very variable and so all over the place in the cutoffs.

Dale Theiling

[planetarymike]

Also according to Dale there is a 'no op' command at the end of every nominal IUVS sequence. Incomplete sequences can be identified by the absence of that command.

[emcangi]

This came up recently and since we haven't worked up a process yet, I just wrote some adhoc code to display segments and orbits with data, but this still has to be used by just asking Dale what's up since we can't use it to make a call about what we actually expect. Anyway, this is on my radar now more accutely so will try to prioritize.