TrafficCommandUpdate missing from trace file name documentation

[ClemensLinnhoff]

Describe the bug

The trace file naming convention in the documentation lists possible types of top-level messages. However, the TrafficCommandUpdate is missing. I propose to use 'tcu' as an abbreviation.

Show some screenshots

[ClemensLinnhoff]

The TrafficCommandUpdate is also missing from section 2.2.2 of the documentation:

[xuanyuxin]

I have a similar question. Why does 2.2.2 Top-level interfaces only have these classes i.e. how to include other classes mentioned in classes so that I can have these msg available in the trace file. Thanks!

[ClemensLinnhoff]

Chapter 2.2.2 only lists possible top-level messages. Other messages listed in the classes are contained in these top-level messages. Also, top-level messages can contain other messages, that can also be used as top-level messages. For example: A SensorData message can contain a SensorView message. But you could also use SensorView by its own.

This is also reflected in the possible trace file types, described here. To give an example: You can have a GroundTruth trace file containing MovingObjects. But you cannot have a MovingObject trace file.