Target tracking is a representative and important application of wireless sensor networks. One of the fundamental studies of target tracking focuses on networks composed of sensor nodes capable of the most elementary binary sensing that provides just one bit of information about the target: whether it is present within the sensing range or not. These so-called binary sensor networks constitute the simplest type of sensor networks that can be used for target tracking.

This simulator is designed for target tracking with binary sensor networks. It is written with QT--a cross-platform application and UI framework. It could run on Windows, Linux and Mac OS. Each sensor node is simulaMulti-thread is used to simulate It provides a graphical interface to

• Configure simulation parameters
• Execute simulation operations
• Display
  • Sensor nodes
  • Target nodes
  • Target tracks
  • Estimated target positions
  • Sensing range of sensor node

ssss

Installation¶

Before you create a new project, please search for existing projects on this site and elsewhere on the web. It is better to help out with an existing project than to start one from scratch.

• Go to the Project Hosting main page and search for existing projects (How to join a project)
• Go to the Create Project page and fill out the form. Remember, pick good labels (see Project Hosting main page for examples).
• How to choose a license.
• How to choose a version control system.

Tutorial¶

You can use the functionality under the Administer tab to customize your project. This tab is visible only to project owners. The following subtabs are useful w

Download¶

You can use the functionality under the Administer tab to customize your project. This tab is visible only to project owners. The following subtabs are useful when creating new projects:

• Project Summary subtab -- You can modify some of the options that you set during project creation, as well as set up blogs, analytics, and a custom project logo. This also provides another opportunity to set up project labels, which will help others find your project.
• Project Members subtab -- You can add new owners or committers to the project.
• Source subtab -- You can elect to have non-project members review your code.

You'll also likely want to set up mailing lists for notifications of commits and issue changes. The emails allow project members and others to keep track of changes to the source code that might affect them. To set up mailing lists, perform the following:

1. If you need to create mailing lists, you may want to use Google Groups.
2. Add (your-project-name)@googlecode.com as an allowed poster to all mailing lists that will receive notifications.
3. In your project, click the Administer tab.
4. Click the Source subtab.
5. In the Activity Notifications area, enter mailing lists that will receive notifications of All commits and click Save Changes.
6. Click the Issue Tracking subtab.
7. In the Activity Notifications area, enter mailing lists that will receive notifications of All issue changes and click Save Changes.

Cite our work¶

Each project has its own Subversion or Mercurial repository.

• Learn more about using Subversion.
• Learn more about using Mercurial.

Perform the following to check code in and out of your source repository:

1. For instructions on how to check out a project's repository from the command line, go to the Source tab. Any user, regardless of whether they have a Google account, can check out and browse the repository anonymously, while project owners and committers are granted full read and write permissions. You can add project owners and committers at the Administer tab.
2. If you plan on synching from an existing repository, you must click the Reset This Repository link at the bottom of the Source tab page before making any other changes to your project's repository. This includes creating any new wiki pages because resetting the repository results in the loss of wiki content. Do not start a wiki page in your project before you complete this step.

After you've been working with your project for a while, the following subtabs on the Source tab will come in handy:

• Browse subtab -- Allows you to browse the files and directories in your project as they existed at a point in time.
• Changes subtab -- Lists changes made to the repository. You can also use this subtab to start a code review of any change.

Questions¶

You can use the functionality under the Administer tab to customize your project. This tab is visible only to project owners. The following subtabs are useful w

Improvements¶

You can use the functionality under the Administer tab to customize your project. This tab is visible only to project owners. The following subtabs are useful w