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

Policies: “AND” rule #243

Open
ablwr opened this issue May 16, 2017 · 4 comments
Open

Policies: “AND” rule #243

ablwr opened this issue May 16, 2017 · 4 comments
Assignees

Comments

@ablwr
Copy link
Contributor

ablwr commented May 16, 2017

Users would like to generate policies based on each other, and also be able to see graphs and values compared against each other (“AND” policy).

@kieranjol
Copy link
Contributor

👍
This would be really great to have. I haven't ran enough tests to see if Signalserver would catch enough errors without this, but I'm familiar with interpreting spikes in multiple graphs in the QCTools GUI so I'd love if this was included.

@yayoiukai
Copy link
Contributor

okay will do!

@yayoiukai yayoiukai self-assigned this Jul 2, 2017
@yayoiukai
Copy link
Contributor

Actually, can you tell me what kind of example? Right now signalserver is treating all filter separately. So I am not sure how I can give two conditions at the same time. I may be able to come up with something after I see the document @ablwr uploaded. (Example policy.) But for the meantime, an example would be great. Or do you actually want a graph not separate by the filter?

@dericed
Copy link
Member

dericed commented Jul 3, 2017

Example could be : TOUT > X & PSNR.Y > Y. This would, for example, show when the frame has many dropouts or speckle while the fields become more different, which would possibly indicate a head clog rather than tape damage.

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

4 participants