You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
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?
The text was updated successfully, but these errors were encountered: