- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Tue, 14 Feb 2017 14:53:22 +0000
- To: public-webrtc-logs@w3.org
"Likelihood of echo" has a similar problem to that of rates - it's a snapshot. "Over the last 10s" is useful but 10s is arbitrary. With using counters instead of rates the caller can decide which time span to look at - is there something analogous for likelihoods? Can we have a `residualEchoLikelihoodCounter` that increases at a _rate_ of the likelihood of echo? That is, if the average likelihood of echo is 50% over a 4 second window, the counter will increase by 2.0. The rate calculated is 0.5/s. I don't think the user agent implementation even needs to be able to calculate likelihood of echo as a percentage. It's enough if the user agent is able to estimate whether or not there is echo. Even with a boolean true false, the rate could be 0 or 1. Perhaps the only requirement should be that for any period of time there is echo detected by the user agent, the average increase in the echo counter should be at a rate [0.5, 1], and for any period of time there is not echo detected by the user agent the rate should be [0, 0.5). -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/153#issuecomment-279728433 using your GitHub account
Received on Tuesday, 14 February 2017 14:53:29 UTC