Skip to content
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

Feature Request - hybrid analysis to use more than one module #63

Open
shadowk29 opened this issue Nov 17, 2015 · 3 comments
Open

Feature Request - hybrid analysis to use more than one module #63

shadowk29 opened this issue Nov 17, 2015 · 3 comments

Comments

@shadowk29
Copy link
Collaborator

CUSUM works well for long events but does a poor job on short ones. SRA does very well with short events, but is not usually suited to long events that might have multiple levels.

Ideally, a user could set a number of data points - events which are longer than this are fed to CUSUM or MSA, and events that are shorter are fed to SRA. This gives the speed of CUSUM for multilevel events and the accuracy of SRA for short ones.

@abalijepalli
Copy link
Member

The logic for such a switch is easy to implement. It may however require us to rethink the DB format. Currently SRA and CUSUM have different DB tables. It is however possible to force SRA to use the CUSUM/MSA output format.

@shadowk29
Copy link
Collaborator Author

Standardizing the database format across the analysis methods might not be a bad idea anyway, for the sake of easy scripting/analysis of the output.

@abalijepalli
Copy link
Member

I agree. In the short term it will break a lot of pre-existing analysis, so it will require some thought. Perhaps some translation layer that upgrades old databases will be needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants