User can't use operational failure rate if it is missing in the data

[kostobog]

Operational failure rate cannot be used if it is not present in the data.

Tasks:

• Open access to failure rate api in analytics server module - resolved in kbss-cvut/ava-analytics#39
• Fix SNS export - add general fault event types (not related to aircraft) kbss-cvut/23ava-distribution#129
• Fix fault tree editor does not work as expected after failure rate is updated #533 - Make sure supertypes is array #534

[blcham]

Currently this was done by workaround -- https://github.com/kbss-cvut/ava-analytics/pull/39, which should be properly fixed in #532.

[blcham]

@kostobog so does it work now ?

[kostobog]

@blcham
This works. User can user operational failure rate if it is not calculated yet.

First user has to click the tree evaluation button. Operational failure rates in the tree will be updated according to the value of min. operational hours field next to the button even if there is an error message that the tree could not be evaluate due to unspecified failure rates in some of of the leaf nodes.

To see the newly added operational failure rates in the SNS node the tree must reloaded. The tree could be reloaded in several ways:

1. automatically if the tree was evaluated successfully without error messages for missing failure rates in leaf nodes
2. by updating one of the nodes, e.g. change the name of change the failure rate selection or manual failure rate.
3. exit the tree and open it again

[blcham]

@kostobog ok I guess the workaround you mentioned is good enough as it is, what do you think?
If so i suggest to close this issue.

[kostobog]

@blcham
Open access workaround works but I am not sure if we want keep it?

Otherwise, I can improve user experience by reloading the tree even if there were missing failure rates at the leaf events. This way the user will always need to only click the evaluate button to see the missing operational failure rates.

[blcham]

If it does not introduce other issues it would be better UX if you reload.

[blcham]

So we can close this issue if:

• refresh of failed evaluation works
• if the ticket about securing ava-analytics contains also adaptation of 23-ava see the issue

[blcham]

@kostobog please see my last comment