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.

This view is used to display throughput (to come in next commits).

- 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).

It's like a label but with fixed dimensions and maximum
characters' capacity at creation time.

This function is used to print rates (say '1kb/s' or '16Mb/s').

Conflicts:
	common/utils/T/T_messages.txt
	openair1/SCHED/phy_procedures_lte_eNb.c

[-1 29] was not very pleasant for MCS 28 or no DCI (value is -1 in this case).
[-2 30] looks better.

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.

Helps visualize MCS usage over time.

Conflicts:
	common/utils/T/tracer/enb.c

Helps visualize MCS usage over time.

Conflicts:
	common/utils/T/tracer/enb.c

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).

update to stats form

Support carrier aggregation with fapi scheduler.

Some hacks:
- hack for DL CQI reporting on 2nd CC
- hack to have carrier aggregation always enabled
  (we don't use activationDeactivationCE, always passing 2 instead)

This only works for a UE with primary CC = 0 and secondary CC = 1.
Many values are also hardcoded.

When receiving an uplink ACK/NACK we send SINR of 20dB
to the libscheduler. If we don't send this information
the scheduler does not activate 16QAM for uplink transmission.

We could do it at any time, this is has been chosen arbitrarily.

The libscheduler does not return a correct rbBitmap
(as far as I understand).

Let's memorize the one used for 1st transmission and reuse it.

If there are two or more UEs in the system then things may
fail if the scheduler allocates the PRBs used by UE 1 in 1st
transmission to UE 2 at the same time of a retransmission for
UE 1.