FeXIII + FeXI waves program and optimization.

[bberkeyU]

The current waves program is based on a FeXIII (1074.7) 3-point 2-beam script that runs in 33 seconds.

1074_03wave_2beam_14sums_1_rep_BOTH.rcp
📗 data rcam both 1074.59 14
📗 data rcam both 1074.81 14
📗 data rcam both 1074.70 14
📗 data tcam both 1074.59 14
📗 data tcam both 1074.81 14
📗 data tcam both 1074.70 14

The program starts with a dark, then takes a flat using the above script, then 120 coronal images with the above script, and finally finishes with another flat. Assuming no pauses for clouds or other issues, this program takes about 70 minutes of wall clock time to run.

As a test, Zihao has asked about adding some FeXI observations to a Waves program. He also tells us that to invert the waves, they need a minimum of 20 minutes of continuous observations (but the data is higher quality with longer stretches).

Questions for the Waves program progressing forward:

• Should the FeXIII + FeXI program replace the current waves program or be an option?
• How much time should we devote to the FeXIII (1074) waves? Are 120 observations still the correct amount?
• Should we bring the 1079 (flats and corona) data observations into the Waves program to make density explicitly part of the script or rely on it likely being included in synoptic scripts taken just before or after the Waves program? The current 1079 3-wavelength script used 2.5 minutes per flat and coronal measurement (5 minutes total). Are we happy with the SNR in these measurements? Should we shorten the observation time, or do we need to stay longer?
• Should we continue using the 33-second cadence? This includes 14 co-added frames; to go faster, we could co-add 12 frames and get a 29-second cadence, or for more snr, we coudl go slower and co-add 16 frames for a 38-second cadence.
• What cadence/number of co-adds should we take the FeXI at?