handle H1 fast LOCKLOSS_DRMI -> ACQUIRE_DRMI_1F -> LOCKLOSS (3->101->2) transitions
Add logic to the history plugin to check if ISC_LOCK_STATE went from the lockloss state we're interested in (generally between 103-202) to LOCKLOSS_DRMI (3), then up briefly to ACQUIRE_DRMI_1F (101) before LOCKLOSS (2). In order to create the refined time plot correctly, the history followup moved before the refine followup in execution order. Additionally, I added a setter to change transition_index to the new values (I also removed the assertions, because they would cause an error whenever this condition was met). This is only for H1. Closes #150
Please register or sign in to comment