Colony » Colony Scout » Colony Scout OS

Revision c384dc7e

Updated the Behavior definition and extensions.

The Behavior.cpp/h class now works and can be extended by simply implementing its run() method. However, the subclass must also be extantiated and used in an external executable. An example of this can be seen in PriyaBehavior.cpp/h, and the executable, priya_behavior_process.cpp. In the future, we should move all behaviors into a behaviors/ folder, and autogenerate the executable to be compiled.

I also changed Behavior and the MotorControl class to accept a scoutname string as a parameter so that each behavior only controls a single scout. This means when you call the priya_behavior_process executable, you pass it one argument (the name of the scout in scoutsim), and all control classes will prefix their output ROS messages with that scoutname so that only the scout you intended gets the messages.

I removed behavior files which do not use this new abstract behavior class.

 *

 * @author Colony Project, CMU Robotics Club

 * @author Priyanka Deo

 * @author Alex Zirbel

 **/

#include "Behavior.h"

Behavior::init(int argc, char** argv)

{

    ros::init(argc, argv, "libscout");

using namespace std;

    motors(node);

Behavior::Behavior(string scoutname)

{

    motors = new MotorControl(node, scoutname);

    loop_rate = new ros::Rate(10);

    //buttons(node);

    //sonar(node);

    ros::Rate loop_rate(10);

}

Behavior::ok()

bool Behavior::ok()

{

    return ros::ok()

    return ros::ok();

}

Behavior::spin()

void Behavior::spin()

{

    ros::spin();

    return;

}

Behavior::spinOnce()

void Behavior::spinOnce()

{

    ros::SpinOnce();

    ros::spinOnce();

    return;

}

Also available in: Unified diff