User Ratings

★★★★★
★★★★
★★★
★★
0
0
0
0
1
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 1 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 1 / 5

Rate This Project
Login To Rate This Project

User Reviews

  • First things its: I'm an ns-3 maintainer. About tracemetrics, even though it might have been a useful tool, it has some important issues. 1) ns-3 ascii traces are not "consistent" between protocols (e.g., some might lack the drop event), 2) ns-3 trace format has changed over the years, and 3) tracemetrics is not supported anymore (afaik). In particular, as 2021, ns-3 does enforce a time unit qualifier in the time-related numbers. I.e., "0.2 seconds" is printed as "0.2s", whereas once upon a time it was simply printed as "0.2". This did break tracmetric ability to parse trace files, as numbers are parsed by "Double.parseDouble", which is unable to cope with the qualifier. Fixing this is possible - but it would be kinda pointless for the reasons above. Instead of relying on tracemetrics, one should use wireshark, and/or use the ns-3 data collection systems to gather data for further analysis.
  • Previous
  • You're on page 1
  • Next