|
[DPRG] Implementing Escape Behaviors
Subject: [DPRG] Implementing Escape Behaviors
From: Rud Merriam
k5rud at arrl.net
Date: Tue Jun 10 00:12:22 CDT 2008
As I mentioned, I have the Create working with behaviors. Tonight I
identified a third "escape" behavior. The three escapes are "bump",
"trapped", and "undock". All do the same thing with slightly different
parameters: back, spin, and drive.
I can implement the action as a function called by each of the behaviors. I
already have that for bump and trapped.
But I am wondering if "escape" should be a behavior of its own triggered by
virtual sensor, say, "flight" that is set by the three escape behaviors.
Flight could have different values. Bump would set it to "go around" while
trapped and undock are "run away". Maybe there are other escapes behaviors
that could be setup? Yup, just thought of one. When I get the IR proximity
detectors setup they will require a milder version of "go around" than
implemented with bump.
I keep thinking of "fight or flight" responses. Fundamental question is when
do behaviors drive other behaviors versus reusing hard-coding actions.
Rud Merriam K5RUD
ARES AEC Montgomery County, TX
http://TheHamNetwork.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://list.dprg.org/pipermail/dprglist/attachments/20080610/6c6f5f1f/attachment.html
More information about the DPRG mailing list
|
