<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.nsnam.org/mediawiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Nikkipui</id>
	<title>Nsnam - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://www.nsnam.org/mediawiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Nikkipui"/>
	<link rel="alternate" type="text/html" href="https://www.nsnam.org/wiki/Special:Contributions/Nikkipui"/>
	<updated>2026-05-04T14:00:21Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.39.8</generator>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=Doxygen-warnings&amp;diff=8130</id>
		<title>Doxygen-warnings</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=Doxygen-warnings&amp;diff=8130"/>
		<updated>2013-11-26T22:02:43Z</updated>

		<summary type="html">&lt;p&gt;Nikkipui: wifi module, one typo&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOC}}&lt;br /&gt;
&lt;br /&gt;
= Doxygen warning removal =&lt;br /&gt;
&lt;br /&gt;
This page is to help coordinating the efforts in fixing [http://www.nsnam.org/bugzilla/show_bug.cgi?id=938 Bug 938: missing Doxygen in ns-3].&lt;br /&gt;
&lt;br /&gt;
As a followup of [http://www.nsnam.org/wiki/Sprints Friday November 15 ns-3 Sprint], we'd like to coordinate the efforts of Doxygen warning removal.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It must be pointed out that warning removing is not good per-se. It is a way to complete the documentation and make it better.&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Undocumented functions leads to poor coding and, ultimately, not be able to use the ns-3 full power.&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Moreover, bad or missing documentation means '''bugs''' !&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Doxygen work status =&lt;br /&gt;
The following table might seems overwhelming. And the warning are just the ones in the model and helper folders.&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
However, mind that many are chain-warnings, meaning that once you fix the master one in the base class, many of them will disappear. More on that at the bottom of the page.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The current doxygen warning status, by module is:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Number of warnings !! Module !! Who's working on it&lt;br /&gt;
|-&lt;br /&gt;
&lt;br /&gt;
| 4086 || lte || &lt;br /&gt;
|-&lt;br /&gt;
| 1903 || wifi || Daniel L.&lt;br /&gt;
|-&lt;br /&gt;
| 1727 || wimax || &lt;br /&gt;
|-&lt;br /&gt;
| 1416 || core || &lt;br /&gt;
|-&lt;br /&gt;
| 696 || network || &lt;br /&gt;
|-&lt;br /&gt;
| 466 || mesh || &lt;br /&gt;
|-&lt;br /&gt;
| 368 || uan || &lt;br /&gt;
|-&lt;br /&gt;
| 363 || dsr || &lt;br /&gt;
|-&lt;br /&gt;
| 259 || mobility || &lt;br /&gt;
|-&lt;br /&gt;
| 237 || spectrum || &lt;br /&gt;
|-&lt;br /&gt;
| 209 || propagation || &lt;br /&gt;
|-&lt;br /&gt;
| 191 || olsr || &lt;br /&gt;
|-&lt;br /&gt;
| 188 || applications || &lt;br /&gt;
|-&lt;br /&gt;
| 171 || stats || &lt;br /&gt;
|-&lt;br /&gt;
| 133 || netanim || &lt;br /&gt;
|-&lt;br /&gt;
| 133 || config-store || &lt;br /&gt;
|-&lt;br /&gt;
| 129 || visualizer || &lt;br /&gt;
|-&lt;br /&gt;
| 126 || buildings || &lt;br /&gt;
|-&lt;br /&gt;
| 84 || energy || &lt;br /&gt;
|-&lt;br /&gt;
| 48 || openflow || &lt;br /&gt;
|-&lt;br /&gt;
| 47 || point-to-point || &lt;br /&gt;
|-&lt;br /&gt;
| 46 || dsdv || &lt;br /&gt;
|-&lt;br /&gt;
| 41 || point-to-point-layout || &lt;br /&gt;
|-&lt;br /&gt;
| 39 || mpi || &lt;br /&gt;
|-&lt;br /&gt;
| 38 || aodv || &lt;br /&gt;
|-&lt;br /&gt;
| 33 || fd-net-device || &lt;br /&gt;
|-&lt;br /&gt;
| 30 || bridge || &lt;br /&gt;
|-&lt;br /&gt;
| 24 || brite || &lt;br /&gt;
|-&lt;br /&gt;
| 22 || nix-vector-routing || &lt;br /&gt;
|-&lt;br /&gt;
| 21 || antenna || &lt;br /&gt;
|-&lt;br /&gt;
| 18 || emu || &lt;br /&gt;
|-&lt;br /&gt;
| 17 || virtual-net-device || &lt;br /&gt;
|-&lt;br /&gt;
| 16 || csma || &lt;br /&gt;
|-&lt;br /&gt;
| 11 || tap-bridge || &lt;br /&gt;
|-&lt;br /&gt;
| 8 || csma-layout || &lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= How to proceed =&lt;br /&gt;
The procedure is simple.&lt;br /&gt;
# Post online that you're working on a module. Eventually coordinate with who's already working on the same module.&lt;br /&gt;
# Follow the direction in the [http://www.nsnam.org/wiki/Sprints Sprint] page to setup Doxygen to show you the warnings.&lt;br /&gt;
# Start with base classes. Mind that ''virtual'' functions can (and should) be documented only in the base class.&lt;br /&gt;
# Don't be afraid of the numbers. I was able to kill 1400 warnings in 2 days (just in my spare time).&lt;br /&gt;
# Once you have a patch, post it in Bugzilla: [http://www.nsnam.org/bugzilla/show_bug.cgi?id=938 Bug 938: missing Doxygen in ns-3].&lt;br /&gt;
# Go drink a beer, you deserve it.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Hint and tips =&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The doxygen.warnings.report.sh script will make a long list of warnings. You're probably interested in the ones from a single module. The following command might help:&lt;br /&gt;
&lt;br /&gt;
  grep &amp;lt;module name&amp;gt; doc/doxygen.warnings.log | sort &amp;gt; doc/my.doxygen.warnings.txt&lt;br /&gt;
Now you have a shorter list of bugs to work with. Cut out the ones from the tests and examples (or not, depends on how pedantic you are). Those are your warnings to kill.&lt;br /&gt;
&lt;br /&gt;
--[[User:Tommaso|Tommaso]] ([[User talk:Tommaso|talk]]) 16:29, 26 November 2013 (EST)&lt;/div&gt;</summary>
		<author><name>Nikkipui</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=HOWTO_add_basic_rates_to_802.11&amp;diff=8049</id>
		<title>HOWTO add basic rates to 802.11</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=HOWTO_add_basic_rates_to_802.11&amp;diff=8049"/>
		<updated>2013-10-15T23:04:24Z</updated>

		<summary type="html">&lt;p&gt;Nikkipui: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOC}}&lt;br /&gt;
&lt;br /&gt;
The 802.11 standard is quite clear on the rules for selection of transmission parameters for control response frames (e.g. CTS and ACK). ns-3 follows the standard and selects the rate of control response frames from the set of basic rates or mandatory rates. This means that control response frames may be sent using different rate even though the &amp;lt;code&amp;gt;ConstantRateWifiManager&amp;lt;/code&amp;gt;  is used. The &amp;lt;code&amp;gt;ControlMode&amp;lt;/code&amp;gt; attribute of the &amp;lt;code&amp;gt;ConstantRateWifiManager&amp;lt;/code&amp;gt; is used for RTS frames only. The rate of CTS and ACK frames are selected according to the 802.11 standard.&lt;br /&gt;
&lt;br /&gt;
However, several real 802.11 drivers allow changing the rate of all control frames. To accomplish this in ns-3, you can manually add WifiMode to the basic rate set.&lt;br /&gt;
&lt;br /&gt;
== HOWTO add basic rates to 802.11 ==&lt;br /&gt;
&lt;br /&gt;
Here's an example of how you can add basic rates to 802.11b.&lt;br /&gt;
&lt;br /&gt;
  // Add the DSSS/CCK rates as the basic rates of our AP&lt;br /&gt;
  Ptr&amp;lt;WifiRemoteStationManager&amp;gt; apStationManager =  DynamicCast&amp;lt;WifiNetDevice&amp;gt;(apDev.Get (0))-&amp;gt;GetRemoteStationManager ();&lt;br /&gt;
  apStationManager-&amp;gt;AddBasicMode (WifiMode (&amp;quot;DsssRate1Mbps&amp;quot;));&lt;br /&gt;
  apStationManager-&amp;gt;AddBasicMode (WifiMode (&amp;quot;DsssRate2Mbps&amp;quot;));&lt;br /&gt;
  apStationManager-&amp;gt;AddBasicMode (WifiMode (&amp;quot;DsssRate5_5Mbps&amp;quot;));&lt;br /&gt;
  apStationManager-&amp;gt;AddBasicMode (WifiMode (&amp;quot;DsssRate11Mbps&amp;quot;));&lt;br /&gt;
&lt;br /&gt;
Please be aware that the rate you are adding must be supported by the PHY layer.&lt;/div&gt;</summary>
		<author><name>Nikkipui</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=HOWTO_add_basic_rates_to_802.11&amp;diff=8048</id>
		<title>HOWTO add basic rates to 802.11</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=HOWTO_add_basic_rates_to_802.11&amp;diff=8048"/>
		<updated>2013-10-15T13:22:19Z</updated>

		<summary type="html">&lt;p&gt;Nikkipui: Add a new page &amp;quot;HOWTO add basic rates to 802.11&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOC}}&lt;br /&gt;
&lt;br /&gt;
The 802.11 standard is quite clear on the rules for selection of transmission parameters for control response frames (e.g. CTS and ACK). ns-3 follows the standard and selects the rate of control response frames from the set of basic rates or mandatory rates. This means that control response frames may be sent using different rate even though the ConstantRateWifiManager  is used. The “ControlMode” attribute of the ConstantRateWifiManager is used for RTS frames only. The rate of CTS and ACK frames are selected according to the 802.11 standard.&lt;br /&gt;
&lt;br /&gt;
However, several real 802.11 drivers allow changing the rate of all control frames. To accomplish this in ns-3, you can manually add WifiMode to the basic rate set.&lt;br /&gt;
&lt;br /&gt;
== HOWTO add basic rates to 802.11 ==&lt;br /&gt;
&lt;br /&gt;
Here's an example of how you can add basic rates to 802.11b.&lt;br /&gt;
&lt;br /&gt;
  // Add the DSSS/CCK rates as the basic rates of our AP&lt;br /&gt;
  Ptr&amp;lt;WifiRemoteStationManager&amp;gt; apStationManager =  DynamicCast&amp;lt;WifiNetDevice&amp;gt;(apDev.Get (0))-&amp;gt;GetRemoteStationManager ();&lt;br /&gt;
  apStationManager-&amp;gt;AddBasicMode (WifiMode (&amp;quot;DsssRate1Mbps&amp;quot;));&lt;br /&gt;
  apStationManager-&amp;gt;AddBasicMode (WifiMode (&amp;quot;DsssRate2Mbps&amp;quot;));&lt;br /&gt;
  apStationManager-&amp;gt;AddBasicMode (WifiMode (&amp;quot;DsssRate5_5Mbps&amp;quot;));&lt;br /&gt;
  apStationManager-&amp;gt;AddBasicMode (WifiMode (&amp;quot;DsssRate11Mbps&amp;quot;));&lt;br /&gt;
&lt;br /&gt;
Please be aware that the rate you are adding must be supported by the PHY layer.&lt;/div&gt;</summary>
		<author><name>Nikkipui</name></author>
	</entry>
	<entry>
		<id>https://www.nsnam.org/mediawiki/index.php?title=HOWTOs&amp;diff=8047</id>
		<title>HOWTOs</title>
		<link rel="alternate" type="text/html" href="https://www.nsnam.org/mediawiki/index.php?title=HOWTOs&amp;diff=8047"/>
		<updated>2013-10-15T12:39:45Z</updated>

		<summary type="html">&lt;p&gt;Nikkipui: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOC}}&lt;br /&gt;
== How to do Various Interesting Things with ns-3 ==&lt;br /&gt;
&lt;br /&gt;
=== System-Related Items ===&lt;br /&gt;
* [[HOWTO make ns-3 interact with the real world]]&lt;br /&gt;
* [[HOWTO use VirtualBox to run simulations on Windows machines]]&lt;br /&gt;
* [[HOWTO get ns-3 running on Mac OS X (10.5.2 Intel)]]&lt;br /&gt;
* [[HOWTO get ns-3 running on Mac OS X (10.6.2 Intel)]]&lt;br /&gt;
* [[HOWTO Use Linux Containers to set up virtual networks]]&lt;br /&gt;
* [[HOWTO use VMware to set up virtual networks (Windows)]]&lt;br /&gt;
* [[HOWTO use ns-3 scripts to drive real hardware (experimental)]]&lt;br /&gt;
* [[HOWTO use ns-3 directly on the ORBIT testbed hardware]]&lt;br /&gt;
* [[HOWTO use ns-3 in the ORBIT testbed environment]]&lt;br /&gt;
* [[HOWTO use ns-3 directly on the CMU wireless emulator]]&lt;br /&gt;
* [[HOWTO use ns-3 with other libraries]]&lt;br /&gt;
* [[HOWTO use ns-3 on Windows with Visual Studio 2010]]&lt;br /&gt;
* [[HOWTO use ns-3 with BonnMotion mobility generator and analysis tool]]&lt;br /&gt;
&lt;br /&gt;
=== Programming-Related Items ===&lt;br /&gt;
* [[HOWTO make and use a new application]]&lt;br /&gt;
* [[HOWTO extract the IP src/dst address from a packet]]&lt;br /&gt;
* [[HOWTO create a new type of protocol header or trailer]]&lt;br /&gt;
* [[HOWTO use null callbacks]]&lt;br /&gt;
* [[HOWTO create a new OSI layer 1 + 2 implementation]]&lt;br /&gt;
* [[HOWTO create a traffic generator]]&lt;br /&gt;
* [[HOWTO determine the path of an attribute or trace source]]&lt;br /&gt;
* [[HOWTO use the ConfigStore]]&lt;br /&gt;
* [[HOWTO determine all the available Values]]&lt;br /&gt;
* [http://www.eg.bucknell.edu/~perrone/2010/08/19/looking-at-ns-3-packet-traces/ HOWTO work with ns-3 packet traces]&lt;br /&gt;
* [http://www.eg.bucknell.edu/~perrone/2010/08/27/creating-a-new-module-in-ns-3/ HOWTO create a new module in ns-3]&lt;br /&gt;
* [[HOWTO enable a subset of ns-3's modules]]&lt;br /&gt;
* [[HOWTO enable/disable examples and tests in ns-3]]&lt;br /&gt;
* [[HOWTO resolve circular references in ns-3 memory disposal]]&lt;br /&gt;
&lt;br /&gt;
==== IDE Integration ====&lt;br /&gt;
* [[HOWTO configure Eclipse with ns-3]]&lt;br /&gt;
* [[HOWTO configure NetBeans with ns-3]]&lt;br /&gt;
* [[HOWTO configure QtCreator with ns-3]]&lt;br /&gt;
&lt;br /&gt;
=== Debugging-Related Items ===&lt;br /&gt;
* [[HOWTO use NS_LOG to find a problem]]&lt;br /&gt;
* [[HOWTO understand and find cause of terminated with signal errors]]&lt;br /&gt;
* [[HOWTO debug smart pointer | HOWTO debug smart pointers and packet pointers]]&lt;br /&gt;
* [[HOWTO use Valgrind to debug memory problems]]&lt;br /&gt;
* [[HOWTO resolve circular references in ns-3 memory disposal]]&lt;br /&gt;
* [[HOWTO build old versions of ns-3 on newer compilers]]&lt;br /&gt;
* [[HOWTO use oprofile]] to profile your ns-3 program&lt;br /&gt;
&lt;br /&gt;
=== Mercurial-Related Items ===&lt;br /&gt;
* [[HOWTO use Mercurial Queues to manage your ns-3 patches]]&lt;br /&gt;
&lt;br /&gt;
=== Data Analysis-Related Items ===&lt;br /&gt;
* [[HOWTO get ns-3 data into SciPy]]&lt;br /&gt;
* [[HOWTO get ns-3 data into ROOT]]&lt;br /&gt;
* [[HOWTO get ns-3 data into SciLab]]&lt;br /&gt;
* [[HOWTO get ns-3 data into Octave]]&lt;br /&gt;
* [[HOWTO get ns-3 to detect steady-state times in your data]]&lt;br /&gt;
&lt;br /&gt;
=== Code Review-Related Items ===&lt;br /&gt;
* [[HOWTO use the coding style tool]]&lt;br /&gt;
* [[HOWTO control Rietveld patch generation]]&lt;br /&gt;
&lt;br /&gt;
=== WiFi Model-Related Items ===&lt;br /&gt;
* [[HOWTO add basic rates to 802.11]]&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
[[User:Craigdo|Craigdo]] 16:34, 22 April 2010 (UTC)&lt;/div&gt;</summary>
		<author><name>Nikkipui</name></author>
	</entry>
</feed>