- time_meas to measure time spent in scheduling
- timeplot to show nice histograms in realtim of above measurement

This tracer takes the traces ENB_MAC_UE_DL_PDU_WITH_DATA
and ENB_MAC_UE_UL_PDU_WITH_DATA from a trace file
(as generated by the "record" tracer) and sends them
in UDP packets correctly formatted for wireshark to
dissect them.

One unresolved problem I face with my version of
wireshark (1.10.6) is that I don't get the frame number,
only subframe. See in the code to change the behavior
if you use a more recent version of wireshark.

You need to properly configure wireshark for it to work.
See $OPENAIR_DIR/openair2/UTIL/OPT/README.txt.

left click: enable autoscroll and go to end of list
right click: disable autoscroll

to scroll by only one line, hold CONTROL key and scroll with
mouse wheel

iqlog.c should change its name, it's too specific.
This new one is more generic and should take over the name.

we have to free memory in any case...

ctrl+c did not work when the program was not connected yet.
It also didn't work if no event was received.

stuff put in there is of lower quality / coding standard / whatever
and serves as example to do quick debugging taks using the T
infrastructure

the current version is very specific to PUSCH IQ data, where the
input buffer has a special format

to be rewritten cleanly at some point

XY_LOOP_MODE: replace old points with new ones, using the maximum size
              of the view
XY_FORCE_MODE: append_forced sets those and only those points
               and we crash if we pass too much points

to be used in conjunction with another tracer
so conceptually it's more a tracee than a tracer

very basic, to be refined, find a nice way to display (plot? text?)
protocol data movement

3 pixels wide look better than 1

more readable, still not satisfying though

events are accepted by the logger if the filter accepts them
the filter is optional (no filter means to accept all events)

this is like timeview but the plotting is done at frame/subframe
resolution of a given reference clock signal, let's say.

The realtime information of the events is not used. It's all
logical.

It will be used to log harq processes for the moment.

and also start to use the PHY textview