signetlabdei / lorawan

An ns-3 module for simulation of LoRaWAN networks
GNU General Public License v2.0
185 stars 131 forks source link

Can't use EnablePacketTracking(filename) to tracking #28

Closed qtrunguet closed 5 years ago

qtrunguet commented 5 years ago

Expected Behavior

Performance file in complete-network-example.cc have data

Actual Behavior

That file is empty

Steps to Reproduce the Problem

1.run complete-network-example.cc

  1. Open performance file
  2. This is empty

Specifications

DvdMgr commented 5 years ago

Hi, the argument to the EnablePacketTracking method is a leftover of a previous implementation. In the current one, performance is printed directly on the standard output. Can you confirm that the results are printed when the script completes?

qtrunguet commented 5 years ago

At example: complete-network-example.cc the result printed but i think something has wrong because i got it: Completed configuration Running simulation... Computing performance metrics... Successful with 1 | Successful with 2 | Successful with 3 | Successful with 4 | Successful with 5 | Successful with 6 | Successful with 7 | Successful with 8 | Failed after 1 | Failed after 2 | Failed after 3 | Failed after 4 | Failed after 5 | Failed after 6 | Failed after 7 | Failed after 8 | Average Delay | Average ACK Delay | Total Retransmission amounts || PHY Total | PHY Successful | PHY Interfered | PHY No More Receivers | PHY Under Sensitivity | PHY Lost Because TX 0 0 0 0 0 0 0 0 | 0 0 0 0 0 0 0 0 | 0 0 | 0 || 200 193 7 0 0 0

DvdMgr commented 5 years ago

The metrics look good to me: since by default the EDs don't require confirmation, they only transmit the packets once and you get the PHY layer performance.

You can safely ignore the zeros in the first part, since they are only filled when confirmed transmissions are used.