[ns] Wimax implementation in ns2

2013-05-12 Thread nishil dahin

Hi guys,

I wanted to know which all are the main files related to wimax
implementation in ns2.

 Like for wifi - ieee 802.11, it is mac-802_11.cc, .h and mac-timers.cc, .h;
correspondingly, which files are for 802.16 (wimax) ?

Nihad S.


[ns] Problems attaching new agent to a node

2013-05-12 Thread Mohsen Sasaninasab

Hello everybody,

I implemented a new agent Clustering in application layer. I put  my .cc,
.h, and .tcl files in my own directory (mohsen) under the ns directory.
Then I added the new packet type in 'packet.h' under packet_t{} and p_info
{}. Also I did necessary changes in ns-default.tcl, ns-packet.tcl, and
Makefile. Then I did 'make clean', 'make depend', and 'make'. Everything
was fine. In my tcl script when I make an object of my new agent and I try
to attach it to a node, NS returns the following Error.

*Here is a piece of my tcl script:*

---

#Create a node

set n0 [$ns node]

set c0 [new Agent/Clustering]

$ns attach-agent $n0 $c0

---





*NS returns the following errors:*



---



can't read debug_: no such variable

(Object set line 1)

invoked from within

Classifier/Port set debug_

invoked from within

catch $c set $var val

invoked from within

if [catch $self cmd $args ret] {

set cls [$self info class]

global errorInfo

set savedInfo $errorInfo

error error when calling class $cls: $args $...

(procedure _o59 line 2)

(SplitObject unknown line 2)

invoked from within

$agent target [[$self node] entry]

(procedure _o11 line 2)

(RtModule attach line 2)

invoked from within

$m attach $agent $port

(procedure _o10 line 4)

(Node add-target line 4)

invoked from within

$self add-target $agent $port

(procedure _o10 line 15)

(Node attach line 15)

invoked from within

$node attach $agent

(procedure _o3 line 2)

(Simulator attach-agent line 2)

invoked from within

$ns attach-agent $n0 $p0

(file clustering.tcl line 29)

root@qq-desktop:~/ns-allinone-2.30/ns-2.30/mohsen#



---



Even I can reach the data members (variables) of my newly defined agent.
When I add the code

$ns attach-agent $n0 $c0

NS returns the above mentioned error.



Does anybody know the cause of this error? Is this because of something I
didn't do or something I did wrong? I am very puzzled by this problem.  Any
help would be very much appreciated.



Thanks in advance,

Mohsen Sasani

Information Technoology, Computer Networks Engineering

Shiraz University of Technology

mohn@gmail.com


[ns] GPSR implementation running out of memory

2013-05-12 Thread Anas Almajali

All,

I ported GPSR implementation to ns-2 2.34. The examples that come with the
implementation work fine.
Some of my simulations that have small number of nodes or few events
happening work fine too. However, when I increase the number of nodes above
100 nodes and have more events, the simulation runs for a while then
aborts. I was checking the memory while running the cases that fail and
found that these simulations are consume the whole memory on my machine and
off course abort after that. I have 8GB of memory! The same simulations
work fine with other routing protocols like AODV and the memory consumption
is within limits.

Does anyone know were does GPSR goes wrong and consumes the memory? and is
there a fix for that?

Anas


Re: [ns] GPSR implementation running out of memory

2013-05-12 Thread Saravanan Kandasamy

Anas,

You are facing a memory leak. The effect of memory leak aggravated when you
run longer simulation time, simulating larger number of nodes or both.

Valgrind is good for memory leak detection. It able to show the functions
and exact lines of codes that potentially causing some of the memory leaks.
In case you have no experience using Valgrind, do spend some time on
internet to learn how to setup and test using Valgrind, it has ample of
information on this.

NS2 does not have automatic garbage collection, thus warrants a manual
freeing of allocated memory once an object is no longer needed.

Good Luck.

rgds
Saravanan K

On Sun, May 12, 2013 at 6:24 PM, Anas Almajali almaj...@usc.edu wrote:


 All,

 I ported GPSR implementation to ns-2 2.34. The examples that come with the
 implementation work fine.
 Some of my simulations that have small number of nodes or few events
 happening work fine too. However, when I increase the number of nodes above
 100 nodes and have more events, the simulation runs for a while then
 aborts. I was checking the memory while running the cases that fail and
 found that these simulations are consume the whole memory on my machine and
 off course abort after that. I have 8GB of memory! The same simulations
 work fine with other routing protocols like AODV and the memory consumption
 is within limits.

 Does anyone know were does GPSR goes wrong and consumes the memory? and is
 there a fix for that?

 Anas



[ns] Extended Deadline: IEEE HEALTHCOM 2013, Lisbon, Portugal October 09-12, 2013

2013-05-12 Thread Jaime Lloret Mauri


CALL FOR PAPERS

15th IEEE International Conference on e-Health Networking, Application  
Services (IEEE HEALTHCOM 2013)
Lisbon, Portugal – October 09-12, 2013
http://www.ieee-healthcom.org

IEEE Healthcom 2013 is fully sponsored by the IEEE Communications Society. It 
aims at bringing together interested parties from around the world working in 
the health care field to exchange ideas, to discuss innovative and emerging 
solutions, and to develop collaborations. eHealth is defined as the 
cost-effective and secure use of information and communications technologies in 
support of health and the related fields, including health-care related 
services, surveillance, literature, education, knowledge, and research, both at 
the local site and at a distance. It will make personalised medicine possible 
and affordable in the near future. The adoption of eHealth technologies in 
medical fields creates huge opportunities yet lots of challenges still need to 
be resolved to build reliable, secure, and efficient networks or platforms with 
great flexibility.

Prospective authors are cordially invited to submit their original 
contributions covering completed or ongoing work related to the eHealth area. 
The topics include but are not limited to

- Biomedical and biosensors engineering
- Body sensor networks and wearable sensor systems
- Clinical biofeedback, decision support systems, and tools
- eHealth information and network Infrastructure
- eHealth for public health (including disease prevention, emergency 
preparedness, epidemiologic interventions)
- eHealth for aging (to support quality of life for older adults, aging in 
place and independence) 
- Emerging eHealth applications
- Health grid and health cloud
- Health monitoring, traffic characterisation,  management
- ICT-enabled personal health system
- Image and video processing on eHealth
- Network/Communications Infrastructures and Architectures for Healthcare
- New IT-enhanced Models for Healthcare delivery
- Pervasive and ubiquitous computing on eHealth
- Practical Applications of e-Health
- Security and privacy on eHealth 
- Storage and Display Devices for eHealth
- Telemedicine and mobile telemedicine

Important dates

- Paper Submission deadline (Extended):May 20, 2013  (firm)
- Notification of acceptance:June 30, 2013
- Submission of camera-ready papers:August 31, 2013

PAPER SUBMISSION

Perspective authors are invited to submit their papers using EDAS System at 
http://edas.info/newPaper.php?c=13601track=26533. A full paper should not have 
more than five (5) IEEE style pages including results, figures and references. 
Papers will be reviewed with the standard reviewing procedure (with at least 3 
independent anonymous reviews). Accepted papers will be published on IEEExplore 
(http://ieeexplore.ieee.org/). The best accepted paper will receive the Best 
Paper Award. Extended version of best papers will be considered for publication 
on the International Journal on E-Health and Medical Communications 
(http://www.igi-global.com/IJEHMC) and in the Elsevier IRBM 
(http://www.elsevier.com/journals/irbm/1959-0318).

Note: To be published in the IEEE Healthcom 2013 Conference Proceedings and 
IEEEXplore, an author of an accepted paper is required to register for the 
conference at the full (member or non-member) rate and present the paper at the 
conference.

General Chair:
Joel Rodrigues, Instituto de Telecomunicações/ University of Beira Interior, 
Portugal

TPC Chairs:
Ricardo Correia, Fac. Medicine, Univ. Porto, Portugal
Christos Verikoukis, CTTC, Barcelona, Spain

Operations Chairs:
Maria Helena Monteiro, ISCSP, Tech. Univ. Lisbon, Portugal
Rita Amorim, ISCSP, Tech. Univ. Lisbon, Portugal

IEEE HEALTHCOM Steering Committee:
Joel Rodrigues (Chair), IT/Univ. of Beira Interior, Portugal
Tsong-Ho Wu, Industrial Tech. Research Inst., Taiwan
Pradeep Ray, Univ. of New South Wales, Australia
Norbert Noury, University of Lyon, France
Chi-Ren Shyu, Univ. Missouri, Columbia, MO, USA

Portuguese Government Liaison:
Henrique Martins, Clinical Information Coordinator, Portugal

Industry and Exhibition Chair:
Rui Gomes, Fernando Fonseca Hospital, Portugal

Industry Forum Chair:
Miguel Sales Dias, Microsoft 

Workshop Chairs:
José Neuman de Souza, Federal University of Cear‡, Brazil
Rui Rijo, Polytechnic Inst. of Leiria, Portugal

Tutorial Chairs:
Jorge Sá Silva, University of Coimbra, Portugal
José Carlos Nascimento, University of Minho, Portugal

Panel Chair:
Eric Addeo, DeVry University, USA

Publicity chairs:
Jaime Lloret, Univ. Politécnica de Valencia, Spain
Lei Shu, Guangdong Univ. Petroc. Tech., China
Aravind Kailas, Univ. North Carolina Charlotte, USA
Scott Fowler, Linköping University, Sweden

Communication Chair:
Francisco Roxo, Catholic Univ. of Lisbon, Portugal

Web Chair:
Vasco Soares, Inst. for Telecom./ IPCB, Portugal



[ns] selfish node isolation

2013-05-12 Thread Ramaprabha N

Hi All
  I have implemented the selfish node creation in aodv.cc . Can
any body tell me how to isolate a malicious/ selfish nodes in aodv.cc
function??? and it should be reflected in the printed route table. i mean
the route table should avoid the particular malicious nodes... thanks in
advance...

-- 
*---
prabha*