-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: add basic testing #15
base: master
Are you sure you want to change the base?
Conversation
@jfsantos could you please help me with the tests? I have some problems making them pass by running FYI: running the CI on the fork, ref: Lightning-Sandbox#1 |
Here are the results by running
|
could be related to #7 |
@jfsantos could you pls accept this CI addition so we can validate the actual state as well as any future contributions? 🐰 |
ok, it seems we will need to move to our own fork... :( |
I apologize for the delay in replying. SRMRpy is a package I wrote almost 10 years ago and do not really actively maintain, but I am happy to include patches! Can you summarize in which state the current contribution is? To reply to one of your questions in the thread, I test SRMRpy locally by comparing its results to the original MATLAB implementation when applicable (SRMRpy does have features the original SRMRtoolbox does not, like using the fast gammatone filterbank implementation). The results do not need to be exactly the same but close enough for me to consider the implementation valid. I also usually do a sanity check by running it on the same file while increasing the amount of added noise and making sure the metric is going down accordingly. |
It about adding automated testing you you do not need to manually run all tests locally and just see the results and so simplify any future fix/update approval
so is it safe also assume that all testing results via Matlab are static so they can be just dumped a file and used for testing/validation... |
to ensure reproducibility and allow any future contributions