It will be nice to have tags / annotations to verification steps

[hrishiballal]

At the moment the steps in a scenario are displayed in the UI one after the other, it would be nice to annotate these steps e.g. pre-flight, in-flight, post-flight etc. In addition, steps that have the same annotation / tags can be grouped in the UI, the tags can be optional and if they are present these can be grouped in the UI.

[hrishiballal]

To be clear, I am suggesting that these annotations can be in the Python code for the client and not something that is set in the UI. It is just displayed in the UI. For e.g, you can even create a Dataclass / Base model with pre-defined terms: https://skybrary.aero/articles/flight-phase-taxonomy so that every step is one of these phases. The IATA terms in the second column in the second table are the most relevant for us.

[RomanPszonka]

@hrishiballal why is it useful?

[hrishiballal]

Hi @RomanPszonka , thanks for the comment. This came from really two things:

• Firstly, your image [1] where the chart gets very complicated and it is hard to follow what is going on so tagging / annotation will help with grouping / highlighting from these steps so we can potentially visually and conceptually separate the different steps and also with the goal to make certification etc. easier. You can imagine also adding these steps to the output reports so that it is clear to the regulator what is going on.
• The phase of flight is just a initial list of states but eventually we want to be able to customize this in any way for steps e.g. I can imagine "scenario data prep" as a tag and all the activities are for data prep etc.

Hope this helps, the goal is enable some UI that will limit the complexity and make it easier for the regulator to understand what is going on in the steps.

[1] -