doc: fix wrong uses of ns3 run

This commit is contained in:
Gabriel Ferreira
2022-06-27 19:31:37 -03:00
parent 7c11a1d012
commit 820dbeab66
9 changed files with 20 additions and 20 deletions

View File

@@ -1429,7 +1429,7 @@ For example, to run your |ns3| program ``hello-simulator`` with the arguments
.. sourcecode:: console
$ ./ns3 run=hello-simulator --command-template="gdb %s --args <args>"
$ ./ns3 run hello-simulator --command-template="gdb %s --args <args>"
Notice that the |ns3| program name goes with the ``--run`` argument,
and the control utility (here ``gdb``) is the first token

View File

@@ -33,10 +33,10 @@
// "tcp-star-server-$n-$i.pcap" where n and i represent node and interface
// numbers respectively
// Usage examples for things you might want to tweak:
// ./ns3 run="tcp-star-server"
// ./ns3 run="tcp-star-server --nNodes=25"
// ./ns3 run="tcp-star-server --ns3::OnOffApplication::DataRate=10000"
// ./ns3 run="tcp-star-server --ns3::OnOffApplication::PacketSize=500"
// ./ns3 run "tcp-star-server"
// ./ns3 run "tcp-star-server --nNodes=25"
// ./ns3 run "tcp-star-server --ns3::OnOffApplication::DataRate=10000"
// ./ns3 run "tcp-star-server --ns3::OnOffApplication::PacketSize=500"
// See the ns-3 tutorial for more info on the command line:
// http://www.nsnam.org/tutorials.html

View File

@@ -40,7 +40,7 @@
* Example Output:
* \verbatim
./ns3 run="hasher-example --time \
./ns3 run "hasher-example --time \
--dict=/usr/share/dict/web2 \
--dict=/usr/share/dict/web2a \
--dict=/usr/share/dict/propernames \

View File

@@ -156,19 +156,19 @@ namespace ns3 {
* Here is the output from a few runs of that program:
*
* \verbatim
$ ./ns3 run="command-line-example"
$ ./ns3 run "command-line-example"
intArg: 1
boolArg: false
strArg: "strArg default"
cbArg: "cbArg default"
$ ./ns3 run="command-line-example --intArg=2 --boolArg --strArg=Hello --cbArg=World"
$ ./ns3 run "command-line-example --intArg=2 --boolArg --strArg=Hello --cbArg=World"
intArg: 2
boolArg: true
strArg: "Hello"
cbArg: "World"
$ ./ns3 run="command-line-example --help"
$ ./ns3 run "command-line-example --help"
ns3-dev-command-line-example-debug [Program Arguments] [General Arguments]
CommandLine example program.

View File

@@ -96,11 +96,11 @@
//
// 6 - Run the server side:
//
// server host: $ ./ns3 run="fd-emu-onoff --serverMode=1"
// server host: $ ./ns3 run "fd-emu-onoff --serverMode=1"
//
// 7 - Run the client side:
//
// client host: $ ./ns3 run="fd-emu-onoff"
// client host: $ ./ns3 run "fd-emu-onoff"
//
#include <iostream>

View File

@@ -37,8 +37,8 @@
//
// Steps to run the experiment:
//
// $ ./ns3 run="fd2fd-onoff"
// $ ./ns3 run="fd2fd-onoff --tcpMode=1"
// $ ./ns3 run "fd2fd-onoff"
// $ ./ns3 run "fd2fd-onoff --tcpMode=1"
//
#include <sys/socket.h>

View File

@@ -37,7 +37,7 @@
//
// Steps to run the experiment:
//
// $ ./ns3 run="fd2fd-onoff"
// $ ./ns3 run "fd2fd-onoff"
//
#include <sys/socket.h>

View File

@@ -2188,7 +2188,7 @@ appending the parameters and their values to the ``ns3`` call when starting each
individual simulation. So the ``ns3`` calls for invoking our 3 simulations would
look as below::
$ ./ns3 run="lena-dual-stripe
$ ./ns3 run "lena-dual-stripe
--simTime=50 --nBlocks=0 --nMacroEnbSites=7 --nMacroEnbSitesX=2
--epc=1 --useUdp=0 --outdoorUeMinSpeed=16.6667 --outdoorUeMaxSpeed=16.6667
--ns3::LteHelper::HandoverAlgorithm=ns3::NoOpHandoverAlgorithm
@@ -2198,7 +2198,7 @@ look as below::
--ns3::PhyStatsCalculator::UlSinrFilename=no-op-UlSinrStats.txt
--RngRun=1" > no-op.txt
$ ./ns3 run="lena-dual-stripe
$ ./ns3 run "lena-dual-stripe
--simTime=50 --nBlocks=0 --nMacroEnbSites=7 --nMacroEnbSitesX=2
--epc=1 --useUdp=0 --outdoorUeMinSpeed=16.6667 --outdoorUeMaxSpeed=16.6667
--ns3::LteHelper::HandoverAlgorithm=ns3::A3RsrpHandoverAlgorithm
@@ -2208,7 +2208,7 @@ look as below::
--ns3::PhyStatsCalculator::UlSinrFilename=a3-rsrp-UlSinrStats.txt
--RngRun=1" > a3-rsrp.txt
$ ./ns3 run="lena-dual-stripe
$ ./ns3 run "lena-dual-stripe
--simTime=50 --nBlocks=0 --nMacroEnbSites=7 --nMacroEnbSitesX=2
--epc=1 --useUdp=0 --outdoorUeMinSpeed=16.6667 --outdoorUeMaxSpeed=16.6667
--ns3::LteHelper::HandoverAlgorithm=ns3::A2A4RsrqHandoverAlgorithm
@@ -2415,7 +2415,7 @@ along entire system bandwidth.
User needs to specify FR algorithm by overriding the default attribute ``ns3::LteHelper::FfrAlgorithm``.
Example command to run ``lena-dual-stripe`` with Hard FR algorithm is presented below::
$ ./ns3 run="lena-dual-stripe
$ ./ns3 run "lena-dual-stripe
--simTime=50 --nBlocks=0 --nMacroEnbSites=7 --nMacroEnbSitesX=2
--epc=1 --useUdp=0 --outdoorUeMinSpeed=16.6667 --outdoorUeMaxSpeed=16.6667
--ns3::LteHelper::HandoverAlgorithm=ns3::NoOpHandoverAlgorithm
@@ -2429,7 +2429,7 @@ Example command to run ``lena-dual-stripe`` with Hard FR algorithm is presented
Example command to generate REM for RB 1 in data channel from ``lena-dual-stripe`` scenario
with Hard FR algorithm is presented below::
$ ./ns3 run="lena-dual-stripe
$ ./ns3 run "lena-dual-stripe
--simTime=50 --nBlocks=0 --nMacroEnbSites=7 --nMacroEnbSitesX=2
--epc=0 --useUdp=0 --outdoorUeMinSpeed=16.6667 --outdoorUeMaxSpeed=16.6667
--ns3::LteHelper::HandoverAlgorithm=ns3::NoOpHandoverAlgorithm

View File

@@ -97,7 +97,7 @@ main (int argc, char *argv[])
// devices installed on both of the nodes. The data rate and delay for the
// channel can be set through the command-line parser. For example,
//
// ./ns3 run "tap=csma-virtual-machine --ns3::CsmaChannel::DataRate=10000000"
// ./ns3 run "tap-csma-virtual-machine --ns3::CsmaChannel::DataRate=10000000"
//
CsmaHelper csma;
NetDeviceContainer devices = csma.Install (nodes);