- 06 Dec, 2016 1 commit
-
-
Cedric Roux authored
Feature 68 enb agent See merge request !47
-
- 05 Dec, 2016 8 commits
-
-
Xenofon Foukas authored
-
Xenofon Foukas authored
-
Cedric Roux authored
Normally it is used to display throughput. The computation it does is to sum up the wanted value for the last second (1000 TTIs) and send this value to the views associated to this logger, at each TTI.
-
Cedric Roux authored
This view is used to display throughput (to come in next commits).
-
Cedric Roux authored
- change paint function: when the XY plot is resized we scale. Previously the last range was put in the middle of the new range (say when we increase the size). We may get aspect ratio changes if the resize is not identical vertically and horizontally, but I think this behaviour is more 'natural'. - fix a bug: the last horizontal tick label was printed to far on the right, out of the bouding box of the XY plot. This is not totally fixed in the case the label is larger than the XY plot. Now the part out of the bounding box will be printed on the left. No big deal, make the plot big enough. (Before, even if big enough you had a problem.) - add a new vertical tick display, to be used for throughput mostly. See in enb.c the difference between 'input signal' and throughput plots (those throughput plots will come in later commits).
-
Cedric Roux authored
It's like a label but with fixed dimensions and maximum characters' capacity at creation time.
-
Cedric Roux authored
This function is used to print rates (say '1kb/s' or '16Mb/s').
-
Cedric Roux authored
-
- 02 Dec, 2016 3 commits
-
-
Rohit Gupta authored
-
Rohit gupta authored
-
Rohit Gupta authored
-
- 01 Dec, 2016 5 commits
-
-
Rohit Gupta authored
-
Rohit Gupta authored
-
Cedric Roux authored
-
Cedric Roux authored
-
Cedric Roux authored
-
- 30 Nov, 2016 5 commits
-
-
Cedric Roux authored
[-1 29] was not very pleasant for MCS 28 or no DCI (value is -1 in this case). [-2 30] looks better.
-
Cedric Roux authored
The problem was visible when DL MCS was set to 20 (do a ping -c 192.172.0.1 -i0.2 to get it). The dots were not plotted at the exact line of the tick mark. Not sure the fix is always correct. No big deal anyway.
-
Cedric Roux authored
Helps visualize MCS usage over time.
-
Cedric Roux authored
A new logger is there: the "ticked TTI logger". Similar to TTI logger (used by the PUCCH1 energy plot) but takes another input, the "tick" (think subframe) and a default value for when no event is triggered between two ticks. This is used for the UL and DL MCS plots in enb.c (next commit).
-
Cedric Roux authored
- add mcs to ENB_PHY_DLSCH_UE_DCI - add mcs, round, first_rb, nb_rb, TBS to ENB_PHY_ULSCH_UE_DCI
-
- 29 Nov, 2016 2 commits
-
-
-
Florian Kaltenberger authored
tested with both EXMIMO and USRP. performance better than in master branch.
-
- 28 Nov, 2016 1 commit
-
-
Cedric Roux authored
When the user clicks on "next UE" or "prev UE" we change the filters of loggers. At the same time, the main thread of enb.c processes events received from the soft-modem and uses the filters, some of them maybe in the process of being changed. Changing the filters is not atomic and has to be protected.
-
- 25 Nov, 2016 10 commits
-
-
Cedric Roux authored
Just below the logo you see the current UE, eg. [UE 0], and near that you have two "buttons" [prev UE] and [next UE]. You click with left button of mouse on those and the various plots that depend on the UE are now done for the new UE (say UE 1 instead of UE 0 if you click on [next UE]). The plots are not cleared when you switch. Let's say it's a feature.
-
Cedric Roux authored
-
Cedric Roux authored
-
Cedric Roux authored
-
Cedric Roux authored
-
Florian Kaltenberger authored
-
Rohit Gupta authored
-
Rohit Gupta authored
-
Rohit Gupta authored
-
Rohit Gupta authored
-
- 24 Nov, 2016 5 commits
-
-
-
Florian Kaltenberger authored
-
Florian Kaltenberger authored
Conflicts: targets/PROJECTS/GENERIC-LTE-EPC/CONF/enb.band38.tm1.exmimo2.conf
-
Florian Kaltenberger authored
-
Cedric Roux authored
Something went wrong somewhere in the commit history, the function was not correct. The most obvious symptom was that way too much SR (scheduling requests) were given to the UE whenever it had some PUCCH to send. The case for TDD has not been tested.
-