Inheritance diagram for ns3::DataCollector:
Collaboration diagram for ns3::DataCollector:
Public Member Functions | |
| void | DescribeRun (std::string experiment, std::string strategy, std::string input, std::string runID, std::string description="") |
| std::string | GetExperimentLabel () const |
| std::string | GetStrategyLabel () const |
| std::string | GetInputLabel () const |
| std::string | GetRunLabel () const |
| std::string | GetDescription () const |
| void | AddMetadata (std::string key, std::string value) |
| void | AddMetadata (std::string key, double value) |
| void | AddMetadata (std::string key, uint32_t value) |
| MetadataList::iterator | MetadataBegin () |
| MetadataList::iterator | MetadataEnd () |
| void | AddDataCalculator (Ptr< DataCalculator > datac) |
| DataCalculatorList::iterator | DataCalculatorBegin () |
| DataCalculatorList::iterator | DataCalculatorEnd () |
Protected Member Functions | |
| virtual void | DoDispose () |
Member Function Documentation
| virtual void ns3::DataCollector::DoDispose | ( | ) | [protected, virtual] |
This method is called by Object::Dispose or by the object's destructor, whichever comes first.
Subclasses are expected to implement their real destruction code in an overriden version of this method and chain up to their parent's implementation once they are done. i.e., for simplicity, the destructor of every subclass should be empty and its content should be moved to the associated DoDispose method.
It is safe to call GetObject from within this method.
Reimplemented from ns3::Object.
The documentation for this class was generated from the following file:
- src/contrib/stats/data-collector.h
