Need some clarification regarding the getting of commanded states about dpa_check HOT 2 OPEN

cc: @richardjedgar if you want to follow along

from dpa_check.

Why do we go back 5 values from the end of telemetry in line 272?

That's somewhat arbitrary, but I just wanted to back up a little to be sure the value is not right on the edge.

Is it necessary to take an average in lines 274-276?

Not strictly necessary, but it seemed like a reasonable thing because IIRC the DPA temperature telemetry is fairly quantized so getting a sampling over 1.4ks might give a better starting estimate. But it's true that it is not critical.

Is there any particular reason why we can't just pick some arbitrary time in the past long enough ago to pick a starting temperature, instead of the last commanded state with available telemetry?

You don't want to go back any further than necessary because then propagation errors are larger. That probably wasn't in your plan but just want to be clear.

Looking at this code again, the point is that it uses these discrete command states for thermal propagation and so you need to join the starting temperature (from available telemetry) to the available command states. The existing code does that, but I realize now that one could modify the start time of state0 to match the starting temperature time. This might avoid a situation where your propagation is longer than necessary because state0 happens to be a very long one and then current code backs up to the beginning of that state.

Something along the lines of:

    if None in state0.values():
        state0 = cmd_states.get_state0(tlm['date'][-5], db,
                                       datepar='datestart')
        state0.update({'T_dpa': np.mean(tlm['1dpamzt'][-10:])})  # last 10 samples
        state0['datestart'] = tlm['date'][-5]  # middle of the last 10 samples
        state0['tstart'] = ...

from dpa_check.