Currently, we make a new INI file if a new feature is added, e.g., adding shap value, generating reports, etc.
This can be complex and time consuming when there are a lot of features addition in the future.
As solution, we can simplify several features (not acoustic features but Nkululeko features) by combining them.
For instance, using the following format for naming INI file:
module_dataformat_clf_feats_test1_test2_test3.ini
For instance,
nkulu_aud_svm_os_limit_umap_shap.ini
That (INI) file could be shown at the top of each feature to be tested (e.g., explore module, feats_opensmile.py, etc).
Also, running test_runs.sh did not provide which tests are passed and which are failed. There is a need to output error (and which test is causing error) if any, like in GH action.
Currently, we make a new INI file if a new feature is added, e.g., adding shap value, generating reports, etc.
This can be complex and time consuming when there are a lot of features addition in the future. As solution, we can simplify several features (not acoustic features but Nkululeko features) by combining them. For instance, using the following format for naming INI file:
For instance,
That (INI) file could be shown at the top of each feature to be tested (e.g., explore module, feats_opensmile.py, etc).
Also, running
test_runs.shdid not provide which tests are passed and which are failed. There is a need to output error (and which test is causing error) if any, like in GH action.