[Apologies if you receive multiple copies of this CFP.]
DEADLINE EXTENDED: 23rd April
1st IEEE International Symposium on Wireless Vehicular Communications (IEEE
WiVeCÂ’07) 30th September - 1st October 2007, Baltimore,
Hi,
Have you tried to plot the received power of node1 against the distance to
node0? I think that an exponent equal to 2.5 for the log-distance pathloss
model could allow the signal to reach long distances. If despite of the
Ricean fading your average received power is always very high, y
set trdeb "Scen-50-"
for {set pause 0} {$pause < 700} {set pause [expr $pause + 100]} {
set scint "${scdeb}$pause-600-500x500."
for {set trafic 10} {$trafic < 50} {set trafic [expr $trafic + 10]} {
set cp "${cpdeb}$trafic-1.0-4"
for {set
You could run a script like:
for parameter1 in 0 1 2 3 4
do
for parameter2 in 10.0 15.0
do
ns myfile.tcl -parameter1 $parameter1 -parameter2 $parameter2
done
done
Don't forget to add the parameters that you want to be modified in your .tcl
file:
proc getopt {argc a
This link may answer the first question: 4.2.5 Precision of the scheduler
clock used in ns: http://www.isi.edu/nsnam/ns/doc/node37.html
What do you mean with "And 1 simulation second traslate directly into 1
realtime second" ?
Regards
Miguel
Keita Rose <[EMAIL PROTECTED]> esc
You can set a threshold (in bytes) with the instruction:
Mac/802_11 set RTSThreshold_
If the packet length is larger than RTSThreshold_, the RTS/CTS exchange process
preceds the data transfer.
Regards
Miguel
boygullit <[EMAIL PROTECTED]> escribió:
Hi
As we know DCF is used by default
