You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We must provide a default way to calculate the confidence for every given tool in their tool adapter.
We must provide an optional input to the adapter to override the default input. This can be used from the SPHA-CLI as follows transform --tool osv --confidence 50 to set the confidence for this specific transformation.
It must be decided how to use --confidence for dynamic calculations. It is easy to set a fixed confidence score for all transformed results, e.g., just say tool results of this tool always have this confidence. However, it also might make sense to have the confidence depend on some parts of the tool results. Customizing this is more difficult and requires further thought. The naive solution to just override our calculation with whatever value --confidence provides is sufficient for the start.
calculate must be extended to take a --ignore-confidence flag to disable all confidence ratings. calculate must be extended to take confidence into account. We must decide where to integrate confidence in the calculation. Most likely in every KPI calculation. We want to make the confidence configurable through the KPI hierarchy. How should this work?
The text was updated successfully, but these errors were encountered:
Each RawValueKPI must contain a confidence score (0 <= confidence <= 100, 100 we are as confident as it gets). The confidence score reflects
We must provide a default way to calculate the confidence for every given tool in their tool adapter.
We must provide an optional input to the adapter to override the default input. This can be used from the SPHA-CLI as follows
transform --tool osv --confidence 50
to set the confidence for this specific transformation.It must be decided how to use
--confidence
for dynamic calculations. It is easy to set a fixed confidence score for all transformed results, e.g., just say tool results of this tool always have this confidence. However, it also might make sense to have the confidence depend on some parts of the tool results. Customizing this is more difficult and requires further thought. The naive solution to just override our calculation with whatever value--confidence
provides is sufficient for the start.calculate
must be extended to take a--ignore-confidence
flag to disable all confidence ratings.calculate
must be extended to take confidence into account. We must decide where to integrate confidence in the calculation. Most likely in every KPI calculation. We want to make the confidence configurable through the KPI hierarchy. How should this work?The text was updated successfully, but these errors were encountered: