Is NS3 simulation result always deterministic given the same workload and topology?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 184
- Avg merge
- 13h 4m
- Merged PRs (30d)
- 1
Description
When using NS3 with the same workload and network topology, sometimes I get identical results, but other times the results differ. Does this variation depend on factors such as the number of threads allocated, random number generation and different physical machine? Or should the NS3 simulation result always be deterministic?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the same workload and network topology, then compare results while varying the number of threads, random-number generation, and physical machine. Done means the issue documents whether NS3 results are deterministic and identifies the conditions that cause variation.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100