-
Notifications
You must be signed in to change notification settings - Fork 9
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
CMR #66
CMR #66
Conversation
@@ -6,6 +6,7 @@ | |||
import pkg.constants as cnsts | |||
from .edivisive import EDivisive | |||
from .isolationforest import IsolationForestWeightedMean | |||
from .cmr import CMR | |||
|
|||
|
|||
class AlgorithmFactory: # pylint: disable= too-few-public-methods, too-many-arguments, line-too-long |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Our factory seems to be growing, can we have switch-case here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In prow we are using python3.9, from what I read online switch-case doesn't work with that python version
+ python --version
Python 3.9.9
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need not necessarily be a switch case. Even a dictionary to map those constants with functions should work so that we can have all the mappings at one place. I am okay if we want to take that in a different PR
494a2f9
to
7cfd97e
Compare
84dd48c
to
5cbec6f
Compare
@shashank-boyapally @vishnuchalla @jtaleric any more comments here? |
Hi @paigerube14 lgtm from my side. just curious on the logic of max_time in the cmr algorithm. |
@paigerube14 I tried to access the console to see how to properly run Running locally, i keep getting
|
Thanks to @shashank-boyapally I pulled in the latest fmatch and this error goes away. |
@jtaleric awesome! The best way to do the lookback to see this feature work is a lookback of 3 (2 earliest will be meaned together and then compared to the latest one) |
@shashank-boyapally I feel like I had to set that to get the older results first. But will play around with taking that out and using the time from one of the runs instead |
/lgtm thanks for adding this @paigerube14 ! |
rh-pre-commit.version: 2.2.0 rh-pre-commit.check-secrets: ENABLED Signed-off-by: Auto User <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Type of change
Description
This new algorithm compares a new run with any previous matching runs and generates a percent difference. This algorithm is for smaller amount of runs to analyze if there is a significant difference/regression than in the current run
If there are more than 1 previous runs to compare to the current run, the previous runs are meaned together to 1 to compare with the new run
NOTE: Further enhancements are needed to pass/fail based on a given tolerancy in the config.
Related Tickets & Documents
Checklist before requesting a review
Testing
https://mastern-jenkins-csb-openshift-qe.apps.ocp-c1.prod.psi.redhat.com/job/scale-ci/job/paige-e2e-multibranch/job/orion/36/console