Conversation
|
use the style of the tests folder |
|
and in priority the pipelines in the multipers/ml folder. |
Co-authored-by: DavidLapous <15857585+DavidLapous@users.noreply.github.com>
multipers using conda, and improve the tests coverage.
DavidLapous
left a comment
There was a problem hiding this comment.
@copilot
put the tests in the tests folder (otherwise they wont be tested automatically)
Remove the tests (added in this pr) that correspond to functions that do not exist, and remove the exception catches on modules / fonctions that do not exist. These tests should fail if such a module doesn;t exist (and the test makes no sense in that case).
… style Co-authored-by: DavidLapous <15857585+DavidLapous@users.noreply.github.com>
I've addressed all your requests in commit aa1fac2:
I've updated the tests to follow the style of the existing tests folder in commit aa1fac2. The new tests use:
I've prioritized the ML pipelines in the
All tests directly exercise the key ML pipeline classes in multipers/ml. |
DavidLapous
left a comment
There was a problem hiding this comment.
@copilot remove the tests related to the one file
Co-authored-by: DavidLapous <15857585+DavidLapous@users.noreply.github.com>
This PR adds targeted tests for the core machine learning pipelines in multipers, focusing on the multi-parameter transformers and estimators in the
multipers/mlmodule as requested.Key ML Components Tested
MMA (Multiparameter Module Approximation) Pipeline:
Signed Measures Pipeline:
Point Cloud Processing:
Distance and Kernel Methods:
Design Principles
The tests follow the existing codebase style with:
Tests will fail appropriately if required modules are missing, ensuring they validate real functionality rather than masking import issues.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.