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

to be removed at some point

The UE sends 2 bits when a second CC is configured, even when
the 2nd carrier is not activated. At least, this is what I
understand and this seems to be what happens with the sequans UE.

this commit is a first step to have the softmodem work with 2 CCs
with the FAPI scheduler.

there is still work to do for it to work properly.

the trace ENB_MASTER_TICK did not work properly in the GUI of
the enb tracer.

Maybe use proc->subframe_tx (or _rx) instead of this proposed
solution, maybe more elegant?

was crashing the processing

important for carrier aggregation case