Support DES Metrics traces

This set of patches adds optional support to create traces for the DES Metrics project.

For more information see the DES Metrics Project page:
https://wilseypa.github.io/desMetrics/

This feature requires CommandLine to trigger the creation of the trace files.  The first patch set adds CommandLine to the examples which didn't already have it.

The second patch implements the DES Metrics tracing for examples and tests.

This feature is enabled by the "--enable-des-metrics" argument to "./waf configure"

See the doxygen comments in src/core/model/des-metrics.h for details on usage, output, and useful filtering commands.

[Peter Barnes, 2016-07-06 23:02:20]

This set of patches adds optional support to create traces for the DES Metrics
project.

For more information see the DES Metrics Project page:
https://wilseypa.github.io/desMetrics/

This feature requires CommandLine to trigger the creation of the trace files. 
The first patch set adds CommandLine to the examples which didn't already have
it.

The second patch implements the DES Metrics tracing for examples and tests.

This feature is enabled by the "--enable-des-metrics" argument to "./waf
configure"

See the doxygen comments in src/core/model/des-metrics.h for details on usage,
output, and useful filtering commands.

[Tom Henderson, 2016-07-17 23:12:47]

On 2016/07/06 23:02:20, Peter Barnes wrote:
> This set of patches adds optional support to create traces for the DES Metrics
> project.
> 
> For more information see the DES Metrics Project page:
> https://wilseypa.github.io/desMetrics/
> 
> This feature requires CommandLine to trigger the creation of the trace files. 
> The first patch set adds CommandLine to the examples which didn't already have
> it.
> 
> The second patch implements the DES Metrics tracing for examples and tests.
> 
> This feature is enabled by the "--enable-des-metrics" argument to "./waf
> configure"
> 
> See the doxygen comments in src/core/model/des-metrics.h for details on usage,
> output, and useful filtering commands.

I am fine with both patches, and tested the second patch.  It shouldn't affect
non-users.  I have one request; can you make the .json files from test.py land
in the testpy-output at the same place as the example-generated .json files?  I
suppose that at least test.py could take care of this by moving any newly
created .json files into the testpy-output directory before exiting.

[Peter Barnes, 2016-08-04 20:58:59]

Patch set 3 addresses Tom's request that test.py output .json files should all
go in the testy-output/.../ subdirectory.

This patch should be applied on top of Patch 2.  I could supply a unified patch
if that's easier.