PursuingComm.h File Reference

Pursuing Task. More...

#include <fstream>
#include <Task.h>
#include <Resource.h>
#include <SharedMem.h>
#include <Time.h>
#include <CommonOptions.h>
#include <CommModule.h>
#include <PursuingData.h>

Go to the source code of this file.

Namespaces
namespace	MipTasks
Classes
class	MipTasks::PursuingComm
	Task for pursuing. More...
Enumerations
enum	MipTasks::PursuingMessageTypes {   MipTasks::PUR_MES_MY_POSE, MipTasks::PUR_MES_MY_STATE, MipTasks::PUR_MES_GIMME_FRONTIER, MipTasks::PUR_MES_MY_FRONTIER,   MipTasks::PUR_MES_NO_GUARD_FRONTIER, MipTasks::PUR_MES_YOUR_NEW_FRONTIER, MipTasks::PUR_MES_FOLLOW, MipTasks::PUR_MES_EXPAND,   MipTasks::PUR_MES_WANDER, MipTasks::PUR_MES_WANNA_BE_FOLLOWER, MipTasks::PUR_MES_NO_GUARD_AFFILIATION, MipTasks::PUR_MES_FOLLOW_ME,   MipTasks::PUR_MES_NUM }
	The messages used by the Pursuing task. A posteriori, we have four categories of messages: AsyncInfo (MY_POSE) AsyncRequest which can be received in every state aka UniversalAsyncRequest (GIMME_FRONTIER,GIMME_STATE,WANNA_BE_FOLLOWER) AsyncRequest which can be received only in the follow state (FOLLOW,EXPAND,WANDER) SyncAnswer (MY_FRONTIER,YOUR_NEW_FRONTIER,FOLLOW_ME,I_AM_NOT_A_GUARD_FRONTIER,I_AM_NOT_A_GUARD_AFFILIATION,MY_STATE). AsyncRequests and SyncAnswers are referred to as Dialog messages. More...
Variables
static const char *	MipTasks::pursuingMessageStrings [PUR_MES_NUM]
	The headers (aka messageTypes) of the messages used by the Pursuing task.

---

Detailed Description

Pursuing Task.

Author:

Antonio Franchi and Arnaud Dufranne