Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • ns-3-dev ns-3-dev
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 250
    • Issues 250
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 157
    • Merge requests 157
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nsnamnsnam
  • ns-3-devns-3-dev
  • Issues
  • #28
Closed
Open
Issue created Feb 13, 2019 by Bastian Bloessl@bastibl

wifi error model: coded bits vs. data bits

The interference helper class calculates the chunk success ratio using the number of coded bits (phyRate * duration). My understanding is that the error models calculate a bit error rate for data bits. If I understand that correctly, the current implementation assumes that the error model returns something like an "equivalent bit error rate" for an uncoded frame that has the size of the coded frame, which seems odd to me.

Shouldn't phyRate be replaced by dataRate?

https://gitlab.com/nsnam/ns-3-dev/blob/master/src/wifi/model/interference-helper.cc#L265

Assignee
Assign to
Time tracking