Feature Request: Set up Command Line Output of Lockloss Select to be an SDF-like MEDM Interace
When following up on lock losses, it is rare that we are chasing down and solving a problem from looking at a single lock loss. It's also (difficult / a lot of work) to (find / identify) a pattern in a collection of lock osses such that the pattern is readily automated for tagging.
In order to facilitate the pattern-finding work-flow of - "filter the lockloss tool webpage for a given ISC_LOCK guardian state" - "record the time" - "run lockloss select to obtain the list of past lock losses" - "select from the list the lockloss that matches lockloss j in your investigation" > rinse and repeat for the next jth aLOG up to the 10 you want to analyze to establish a pattern Further, for a given investigation, it's not always that we need everything that's launched in a lockloss select query, (1) the specific lockloss webpage (2) a default ndscope template (3) the guardian log
Acknowledging that this will be a ton of work (but so was ndscope, and the lockloss tool itself, right? worth it in the end!), I'm imagining being able to pull up an MEDM screen that has all the information that is displayed when one types "lockloss tool," i.e. (i) the reverse-chronological number, (ii) the data and time, (iii) the relevant guardian node name, and (iv) the state transition to lockloss in the same fashion that SDF diffs are displayed. Even more awesome, would be -- from that same screen: (I) there could be buttons (just like the "revert" "accept" and "mon") buttons that would launch the users' choice of (1), (2), or (3), or (all) of the above. (II) That button could also be fed (maybe?) by a user input string (as a field on the MEDM screen) for which ndscope template to run. (III) there could be a field, much like "sort on substring" field in the SDF system, in which you can filter the list of losses for given state names (or numbers it thats easier). (I), (II), and (III) collectively would allow an investigator to open the lockloss screen, filter for locklosses at ISC_LOCK state 342, change the ndscope template launcher name to their desired template, and hit "launch," "launch," "launch," "launch," "launch," "launch," for the 6 lock specific lock losses in which they want to find a pattern.
Understandable hurdles (I'm sure my list is no where near complete, but its what I could think of immediately): (a) Unlike SDF, the list of locklosses is a countably infinite. How far back in time do we limit what's displayed? That decision's kinda already been made with lockloss select at 50, but woth re-assessing. (b) Such an interface would need its own EPICs IOC to support the dynamic collection of strings / information about each lock loss.