Skip to content
This repository has been archived by the owner on Oct 3, 2023. It is now read-only.

Lacking statistics in log #3

Open
nvduc opened this issue Feb 11, 2020 · 4 comments
Open

Lacking statistics in log #3

nvduc opened this issue Feb 11, 2020 · 4 comments

Comments

@nvduc
Copy link

nvduc commented Feb 11, 2020

According to the challenge homepage, a proposed algorithm is evaluated using the following six criteria: Average selected bitrate (Mbps), Average buffer occupancy (s), Average live latency (s), Average number of bitrate switches, Average number of stalls, Average stall duration (s).

However, only the switch history, stallDuration, avgLatency, and avgBufferLength are provided in the log after running a test mode. Here is the result I got:

Run complete
{
  switchHistory: [
    { start: 8.821109, end: 9.978802, quality: [Object] },
    { start: 9.978802, end: 81.066866, quality: [Object] }
  ],
  stallDuration: 63883.05500005663,
  avgLatency: 12.028431111111123,
  avgBufferLength: 0.08518444444444441
}
Done

Could you please update the code so that I can get all the above six statistics to evaluate my algorithm?

@johnBartos
Copy link
Contributor

@nvduc Thanks for the report, I'm still working on it. Should have it done by today. Will update this issue when it's committed.

@johnBartos
Copy link
Contributor

Sorry had a busy day and didn't finish this, will get around to it tomorrow.

@johnBartos
Copy link
Contributor

johnBartos commented Feb 12, 2020

@nvduc Ok, average bitrate and # switches have been added, and stats are saving to a json file (one per run). I haven't yet computed the NQoE score but I'll do that tomorrow.

@nvduc
Copy link
Author

nvduc commented Feb 13, 2020

@johnBartos Thank you very much for your help.

@johnBartos johnBartos reopened this Mar 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants