Skip to main content


Showing posts from June, 2014

Featured in Openshift Developer Spotlight

As many of you would know, a few months back I have launched the ONE Knowledge Base , which is hosted on Openshift. This week, my profile has been featured in the Openshift Developer Spotlight . Check out the mini-interview to learn why the ONE KB was developed and what problem it solves. Besides, you would also get to know about my favorite tools and development stack :) If you have not tried the ONE KB yet, go for it now. Search the archives, and you might find that your question has already been answered!

Controlling Transmission Range from within the Simulation

While simulating scenarios with the ONE simulator, one typically defines one or more network interfaces, and add them to the nodes as required. This use case prevails in most of the scenarios. However, a drawback here is that different network interfaces are mutually incompatible — an interface of type 1 can't communicate with any interface not of type 1. Under certain circumstances, it might be required to control the transmission range of one or more network interfaces dynamically from within the simulation. For example, in one of my works, " On emotional aspects in Mission-Oriented Opportunistic Networks ", I have considered the case where users occasionally turn off their device radios based on their contemporary emotions. In particular, the following shows how to set the radio range to 0: ModuleCommunicationBus comBus = host.getComBus(); // Store the original radio range the first time it is reset if (this.originalRadioRange == -1) { this.originalRadioRange =