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

Clarification of Dataset Collection Procedure #2

Open
finleyb opened this issue Dec 29, 2021 · 1 comment
Open

Clarification of Dataset Collection Procedure #2

finleyb opened this issue Dec 29, 2021 · 1 comment

Comments

@finleyb
Copy link

finleyb commented Dec 29, 2021

From my understanding the dataset was collected with G-NetTrack Pro, however the actual collection procedure is still a bit unclear. Specifically, did the G-NetTrack Pro app just do passive bitrate tracking while you, for example, download the file (without any G-NetTrack Pro active bitrate tests) and also do active ping tests every 10 seconds? Also, the bitrates seem to often drop very low during the second when the ping is reported. Is this a result of the testing method? How do you handle this?

@jq5
Copy link
Collaborator

jq5 commented Dec 30, 2021

Hi there,

I spend a decent bit of time this morning hunting through this.

So, we have ping on the download log files only, not the streaming logs.

For streaming, we used G-Net as a logging system while we streaming via a second device connected to the phone.

For download, we used G-Net to download a 200mb file and we could then turn on the ping element.

I had a look at the raw logs and G-Net stops tracking the download and uses ping for each time period ping is used.

I've added a sample of the raw logs so you can see this.
sample_raw.txt

You will also notice that the DL_bitrate is logged every second, and multiple times per second when the rate DL very large.

We did not handle any of the rate logging that G-Net undertook, we just extract the time period content from the raw logs and populated these in to our dataset.

I hope this helps,

J

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

No branches or pull requests

2 participants