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
The list of KPIs that can be extracted are available in the kpi_mapping.csv file (link to file?). If I am interested in a KPI that has not yet been integrated in the list:
I download the kpi_mapping.csv file and edit it with additional KPI (where? interface?)
I make sure that the newly updated kpi_mapping.csv file is the one fed to the extraction pipeline (needs to be detailed)
I should be aware that extraction on new KPIs might not work well since the models have not yet been trained for these specific KPIs
Training might be necessary and is definitely recommended if performance is not satisfying (please refer to User Story I want to (re-)train the model)
It also depends on how the tool is used. For technical users and contributors that can fork the code and update it, they should be able to do it locally. A non-technical audience would not be able to do that.
But if the tool is only used as a service (using an interface/app), we should not allow people to modify the kpi_mapping file and re-upload it (unless there are stringent validation rules for file modification and training). However, people could submit a request for the community/team to do it.
The text was updated successfully, but these errors were encountered:
The list of KPIs that can be extracted are available in the kpi_mapping.csv file (link to file?). If I am interested in a KPI that has not yet been integrated in the list:
It also depends on how the tool is used. For technical users and contributors that can fork the code and update it, they should be able to do it locally. A non-technical audience would not be able to do that.
But if the tool is only used as a service (using an interface/app), we should not allow people to modify the kpi_mapping file and re-upload it (unless there are stringent validation rules for file modification and training). However, people could submit a request for the community/team to do it.
The text was updated successfully, but these errors were encountered: