Re: [ns] problem with compilaion of make

2008-04-02 Thread bilge kartal

Hi rakesh,

your path should be ~ns2.31/
and then
./configure
make clean
make

Im doing this and it works. I hope this may help you.

Good luck
Bilge


On 4/2/08, srupesh [EMAIL PROTECTED] wrote:



 hi rakesh,
  Are you running configure before doin make??
 and u should do ur changes in   ~/ns*/Makefile.in



 rakesh chouhan-2 wrote:
 
 
  hi all ns-users
  when i do some changes in some c++ file ,or add a new C++ file,
  and like if we add a C++ file (ex-linkage.cc) in ns-2.31, do changes in
  makefile by writing ex-linkage.o in OBJ_CC.
 
  and when we recompile this by writing
  make depend
  there is a message: *Makefile:159: *** commands commence before first
  target. Stop*
  and after this I write
  make
  then same message generated:*Makefile:159: *** commands commence before
  first target. Stop*
  **
  what's the problem with this code ,
  I am using ns-2 on windowsXP with cygwin support
 
  plz help me
 
 

 --
 View this message in context:
 http://www.nabble.com/problem-with-compilaion-of-make-tp16419483p16437768.html
 Sent from the ns-users mailing list archive at Nabble.com.




[ns] Energy model question?

2007-11-14 Thread bilge kartal

Hi,

Can anyone explain me that what is happening in the following code piece of
wireless-phy.cc. I know it is too long :)) but i just want to know why it
doesnt use txtime directly. What does gap adjust time and actual txtime
mean . It is same in SendUp process too. In that case it computes actual
rxtime.

Thanks in advance
Bilge


 
WirelessPhy::sendDownhttp://www.auto-nomos.de/ns2doku/class_wireless_phy.html#b3c104399787b4c6a8feb6988f43d831
(Packet http://www.auto-nomos.de/ns2doku/class_packet.html *p)
00201 {
00202 /*
00203  * Sanity Check
00204  */
00205 
assert(initializedhttp://www.auto-nomos.de/ns2doku/class_wireless_phy.html#64da633aac66edcb7ab4778e0562dfcf
());
00206
00207 if 
(emhttp://www.auto-nomos.de/ns2doku/class_wireless_phy.html#fae1f79f5bdb8c1751c2f0897ed9f308())
{
00208 //node is off here...
00209 if
(Is_node_onhttp://www.auto-nomos.de/ns2doku/class_wireless_phy.html#6bd3fc55b0611ba38a4db1f3f028e98d()
!= true ) {
00210
Packet::freehttp://www.auto-nomos.de/ns2doku/class_packet.html#9fe78c9316daec88ed8613bc82bdb817
(p);
00211 return;
00212 }
00213
if(Is_node_onhttp://www.auto-nomos.de/ns2doku/class_wireless_phy.html#6bd3fc55b0611ba38a4db1f3f028e98d()
== true  
Is_sleepinghttp://www.auto-nomos.de/ns2doku/class_wireless_phy.html#1bde5343080fff2f7a9dcb6ba2720726()
== true){
00214
emhttp://www.auto-nomos.de/ns2doku/class_wireless_phy.html#fae1f79f5bdb8c1751c2f0897ed9f308()-
DecrSleepEnergy(NOWhttp://www.auto-nomos.de/ns2doku/object_8h.html#cc4a9ad83f9350a588d117e0c8916d45
-update_energy_time_http://www.auto-nomos.de/ns2doku/class_wireless_phy.html#7fde0be4a8fad88fa3af7a95b3389fc7
,
00215
P_sleep_http://www.auto-nomos.de/ns2doku/class_wireless_phy.html#9f564b48e2c1cd1033c18bc866d401d9
);
00216
update_energy_time_http://www.auto-nomos.de/ns2doku/class_wireless_phy.html#7fde0be4a8fad88fa3af7a95b3389fc7=
NOWhttp://www.auto-nomos.de/ns2doku/object_8h.html#cc4a9ad83f9350a588d117e0c8916d45
;
00217
00218 }
00219
00220 }
00221 /*
00222  * Decrease node's energy
00223  */
00224 
if(emhttp://www.auto-nomos.de/ns2doku/class_wireless_phy.html#fae1f79f5bdb8c1751c2f0897ed9f308())
{
00225 if
(emhttp://www.auto-nomos.de/ns2doku/class_wireless_phy.html#fae1f79f5bdb8c1751c2f0897ed9f308()-energy()
 0) {
00226
00227 double
txtimehttp://www.auto-nomos.de/ns2doku/class_phy.html#360432328ebf49a111c88900250d6f43=
hdr_cmn::accesshttp://www.auto-nomos.de/ns2doku/structhdr__cmn.html#f702fbe670e3a5c2fc6b1ca0fc3d915f
(p)-txtimehttp://www.auto-nomos.de/ns2doku/structhdr__cmn.html#408d3b7fda2669ce34434c6e7b013153
();
00228 double start_time =
MAXhttp://www.auto-nomos.de/ns2doku/fsm_8cc.html#fa99ec4acc4ecb2dc3c2d05da15d0e3f
(channel_idle_time_http://www.auto-nomos.de/ns2doku/class_wireless_phy.html#5869801e88394dc74796cda2d3bae0fb,
NOWhttp://www.auto-nomos.de/ns2doku/object_8h.html#cc4a9ad83f9350a588d117e0c8916d45
);
00229 double end_time =
MAXhttp://www.auto-nomos.de/ns2doku/fsm_8cc.html#fa99ec4acc4ecb2dc3c2d05da15d0e3f
(channel_idle_time_http://www.auto-nomos.de/ns2doku/class_wireless_phy.html#5869801e88394dc74796cda2d3bae0fb,
NOWhttp://www.auto-nomos.de/ns2doku/object_8h.html#cc4a9ad83f9350a588d117e0c8916d45
+txtime);
00230 double actual_txtime = end_time-start_time;
00231
00232 if (start_time 
update_energy_time_http://www.auto-nomos.de/ns2doku/class_wireless_phy.html#7fde0be4a8fad88fa3af7a95b3389fc7)
{
00233
emhttp://www.auto-nomos.de/ns2doku/class_wireless_phy.html#fae1f79f5bdb8c1751c2f0897ed9f308
()-DecrIdleEnergyhttp://www.auto-nomos.de/ns2doku/class_energy_model.html#7c9de0819f41400569a19b5e854705ce(start_time
-
00234
update_energy_time_http://www.auto-nomos.de/ns2doku/class_wireless_phy.html#7fde0be4a8fad88fa3af7a95b3389fc7,
P_idle_http://www.auto-nomos.de/ns2doku/class_wireless_phy.html#076e5bc9c8ef4f6b580237d4332cb0ce
);
00235
update_energy_time_http://www.auto-nomos.de/ns2doku/class_wireless_phy.html#7fde0be4a8fad88fa3af7a95b3389fc7=
start_time;
00236 }
00237
00238 /* It turns out that MAC sends packet even though, it's
00239receiving some packets.
00240
00241 if (txtime-actual_txtime  0.01) {
00242 fprintf(stderr,Something may be wrong at MAC\n);
00243 fprintf(stderr,act_tx = %lf, tx = %lf\n,
actual_txtime, txtime);
00244 }
00245 */
00246
00247// Sanity check
00248double temp =
MAXhttp://www.auto-nomos.de/ns2doku/fsm_8cc.html#fa99ec4acc4ecb2dc3c2d05da15d0e3f
(NOWhttp://www.auto-nomos.de/ns2doku/object_8h.html#cc4a9ad83f9350a588d117e0c8916d45
,last_send_time_http://www.auto-nomos.de/ns2doku/class_wireless_phy.html#03cb2c6c5a0ff462f123a35353b07d5f
);
00249
00250/*
00251if (NOW  last_send_time_) {
00252fprintf(stderr,Ar !! Overlapping transmission. NOW
%lf last %lf temp 

Re: [ns] Bug in 802.15.4?

2007-10-25 Thread bilge kartal

Hii,

I have similar problem but mine is related to sleeping state of nodes. When
i set sleep time a value. After that time my nodes spend most of their time
in sleep mode. I m using AODV over 802.15.4. So all packets drop becasue of
the routing hole.
And another question about ARP disabling. Becasue i remove all headers
including ARP headers. I didnt understand why you are changing C++ code.
Removing ARP headers can use to disabling ARP protocol. I confused. It
should be so. If packet doesnt have ARP headers how it can use ARP
protocol. Can u explain me why you need to change c++ code.Thank u in
advance

Regards
Bilge.


On 10/23/07, Cesare M. Carretti [EMAIL PROTECTED] wrote:


 Hi again,
 I have tried to turn off arp packets but I have still the problem. I was
 thinking to produce a function to reset in some way the mac if this 'get
 stuck' situation happen. What do you think?
 For be aware of blocking inside the code I could wait some attempt to send
 counting from application layer or from the queue...

 Regards
 Cesare Carretti

  Hi,
  thank you so much for your answers!
  I will try to disable ARP packet transmissions. Thank you also for the
 explanation, I was trying to debug p802_15_4mac but it is not so easy...
 I forced the queue to send packet modifying the recv function in the
 file
  queue.cc, adding a counter and calling the resume function after a
 certain
  number of attempts, also with the blocked flag true. It is not so
 elegant
  but it helped me to understand something more!
 
  Regards
 
  Cesare Carretti
 
  Hi there,
  this failure should most probably relate to the busy_rx state returned
 after the call to switch the radio to transmit.
  This happens basically in two different situations,
  one is during the association and the other one is during sending/CCA.
 If during the CCA a packet arrives, this packet gets falsely received
 and
  thus, upon the call to switch, the function to switch the radio state
 returns with a busy_rx, that doesn't get handled and thus the whole
 sending process gets stuck. As there is still the outgoing packet
 within
  the mac, the enforcement of an additional sending - by the way, how did
 you manage/implement that one? - leads to a task overflow.
  The arp only diminishes the probability of this failure happening, as
 it
  shortens the time for packet processing at the node...
   Original-Nachricht 
  Datum: Thu, 18 Oct 2007 18:11:48 +0200
  Von: Stefano Busanelli [EMAIL PROTECTED]
  An: Cesare M. Carretti [EMAIL PROTECTED]
  CC: ns-users@ISI.EDU
  Betreff: Re: [ns] Bug in 802.15.4?
  In the past I'd had noticed a similar strange behavior: in fact,
 during
  some simulation runs, nodes didn't transmit packets, seemingly without
 no reason, while in other simulations nodes transmitted normally. I
 had solved the problem disabling ARP packet transmissions.
  In the mailing list archive there are many threads that explain how to
 do this.
  Regards
  Stefano Busanelli
  Il giorno gio, 18/10/2007 alle 12.33 +0200, Cesare M. Carretti ha
 scritto:
   Hello all,
   I am implementing a distributed algorithm for sensor network, and I
  wrote
   an application and a transport protocol simil-UDP to send data. I
 have a strange problem in my simulation:
   at some point, one node stop to send packet, it is blocked and if I
  try
  to
   force the queue to send packet, I have a task overflow error from
 mac
   layer.
   I still do not know why this thing happen at some point, I am trying
  to
  do
   some debugging, maybe for some collision. Anyway I think this is not
 normal, because it should never happen that a node stop sending data
  (it
   continues to receive) at all forever, it should maybe reset itself
 if
   there is some problem. Maybe it is waiting for something?
   My application works very well over 802.11, so I think it should be
  the
   same with 802.15.4 (of course with a different output, number of
  packet
   etc).
   However it shouldn't stop!
  
   What do you think?
  
   best regards
  
   Cesare Carretti
  
  --
  GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS.
  Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail
 
 
 







[ns] Fwd: what is the relation between Poisson PMF and simultion parameter

2007-10-02 Thread bilge kartal

-- Forwarded message --
From: bilge kartal [EMAIL PROTECTED]
Date: Oct 2, 2007 4:08 PM
Subject: what is the relation between Poisson PMF and simultion parameter
To: ns-users@isi.edu

hi,

I really lost in Poisson traffic.  How can i simulate a poisson traffic with
using general poisson distribution parameter. For example if i said that
packets arrive at rate lambda does it mean that i should set rate parameter
as lambda. I m using CBR traffic source as setting burst time_ 0. But i
confused about to set packet size, rate, interval. idle time  according to
PMF of my poisson distribution.

I ll be really glad if someone help mee :(

Regadrs

Bk