package bosdyn.api.autowalk

Get desktop application:
View/edit binary Protocol Buffers messages

• rpc CompileAutowalk (stream DataChunk, stream DataChunk)

  autowalk_service.proto:21

  Compile a walk into a mission. Input DataChunks should deserialize into a CompileAutowalkRequest. Output DataChunks should deserialize into a CompileAutowalkResponse. This rpc is stateless.

• rpc LoadAutowalk (stream DataChunk, stream DataChunk)

  autowalk_service.proto:26

  Compile a walk into a mission then load to mission service. Input DataChunks should deserialize into a LoadAutowalkRequest. Output DataChunks should deserialize into a LoadAutowalkResponse.

An Action is what the robot should do at a location. For example, the user may desire that the robot perform a laser scan at a given waypoint.

Used in: Element

• oneof action

  • Action.Sleep sleep = 1

  • Action.DataAcquisition data_acquisition = 2

  • Action.RemoteGrpc remote_grpc = 3

  • Action.ExecuteChoreography execute_choreography = 5

  • mission.Node node = 4

    This field can be used to specify a behavior tree as an action. If the user had two callbacks they would like to run simultaneously at the waypoint this action is associated with, they could use create a behavior tree inside Node with both callbacks embedded in a simple parallel. The downside of using node, is that editors might not support editing parameters directly.

For actions associated with the Data Acquisition Service.

Used in: Action

• optional AcquireDataRequest acquire_data_request = 1

  The autowalk service replaces the action_name field in the CaptureActionId with the element name.

• mission.DataAcquisition.CompletionBehavior completion_behavior = 2

• optional AcquisitionCapabilityList last_known_capabilities = 3

  Last known Data Acquisition capabilities.

• repeated ImageCaptureAndSource record_time_images = 4

  Any images taken at action creation time. For DataAcquisition actions, this includes: - Any images in the Data Acquisition capture. - Any images that are inputs to NCB workers that are in the Data Acquisition capture. - Any images that a Data Acquisition plugin in the Data Acquisition capture requests a region of interest for. Note that both this message and AcquisitionCapabilityList will contain the Spec for images sources. This message will contain the spec at record time, while last_known_capabilities should be updated as time progresses and services evolve. This data is meant to allow UIs to give users context about their actions, AND provide them a canvas to edit region of interests with after the fact. It is not used at mission playback time.

Used in: Action

• string sequence_name = 1

  The name of the sequence to play.

• optional ExecuteChoreography.PromptParams prompt_params = 2

Used in: ExecuteChoreography

• bool prompt_for_start_time = 1

  Should the dance start time be determined before the dance plays at runtime from user input

• optional google.protobuf.DoubleValue prompt_timeout = 2

  How long will the prompt run before timing out. If unset, the default value of 10 minutes will be used.

Used in: Action, GlobalParameters

• string service_name = 1

  Name of the service in the directory.

• optional google.protobuf.Duration rpc_timeout = 2

  Timeout of any single RPC. If the timeout is exceeded, the RPC will fail. The mission service treats each failed RPC differently: - EstablishSession: An error is returned in LoadMission. - Tick: The RPC is retried. - Stop: The error is ignored, and the RPC is not retried. Omit for a default of 60 seconds.

• repeated string lease_resources = 3

  Resources that we will need leases on.

• repeated mission.KeyValue inputs = 4

  The list of variables the remote host should receive. Variables given can be available at either run-time or compile-time. The "key" in KeyValue is the name of the variable as used by the remote system. DEPRECATED as of 3.3. Please use 'parameters' instead.

• optional CustomParamCollection parameters = 5

  All specifications and any values chosen at record time.

• repeated ImageCaptureAndSource record_time_images = 6

  Any images taken at action creation time. For RemoteGRPC's, this will only happen if the RemoteGRPC advertises parameters that require a region of interest for a specific camera. This data is meant to allow UIs to give users context about their actions, AND provide them a canvas to edit region of interests with after the fact. It is not used at mission playback time.

The robot does nothing but wait while also performing its ActionWrapper(s). For example, if the user wants the robot to pose for some amount of time (while doing nothing else), they would populate an ActionWrapper with Pose and set the desired duration here accordingly.

Used in: Action

• optional google.protobuf.Duration duration = 2

An ActionWrapper is what the robot should do prior to and during an action. For example, the user may desire that the robot stand in such a way that its z-axis is aligned with the gravity vector, even though it is standing on an incline.

Used in: Element

• optional ActionWrapper.RobotBodySit robot_body_sit = 1

• optional ActionWrapper.RobotBodyPose robot_body_pose = 2

• optional ActionWrapper.SpotCamLed spot_cam_led = 4

• optional ActionWrapper.SpotCamPtz spot_cam_ptz = 5

• optional ActionWrapper.ArmSensorPointing arm_sensor_pointing = 6

• optional ActionWrapper.SpotCamAlignment spot_cam_alignment = 9

• optional ActionWrapper.GripperCameraParams gripper_camera_params = 7

• optional ActionWrapper.GripperCommand gripper_command = 8

Position the body and perform a joint move and cartesian command in target frame

Used in: ActionWrapper

• optional ArmJointTrajectory joint_trajectory = 2

  Arm Joint Move Command The joint trajectory to execute in the initial rough pointing joint move. Can be unset - if it is, robot will skip this step.

• optional SE3Pose wrist_tform_tool = 3

  Arm Cartesian Command The tool pose relative to the parent link (wrist). Defaults to a frame with it's origin slightly in front of the gripper's palm plate aligned with the wrist's orientation.

• optional SE3Trajectory pose_trajectory_rt_target = 4

  A 3D pose trajectory for the tool expressed in target frame, Can be unset - if it is, robot will skip this step.

• optional SE2Pose target_tform_measured_offset = 7

  Robot desired stance relative to waypoint This is taken by measuring the average of the footprints in body frame at the time of waypoint creation. This is used to generate the stance command. Target == waypoint. This assumes the waypoint is gravity aligned.

• optional spot.BodyControlParams.BodyAssistForManipulation body_assist_params = 5

  Body mobility params during cartesian move

• bool force_stow_override = 6

  If true, the arm will stow after this action no matter what. If false, the arm will only stow if the next action is far away.

Set the camera params of the gripper camera

Used in: ActionWrapper

• optional GripperCameraParams params = 1

Used in: ActionWrapper

• optional GripperCommand.Request request = 1

• bool disable_post_action_close = 2

  By default, any action that includes a GripperCommand action wrapper will run the specified command BEFORE the action is run. By default, after the action is run the gripper will be closed. This behavior can be turned off by setting this flag to true.

Pose the robot prior to performing the action

Used in: ActionWrapper

• optional SE3Pose target_tform_body = 1

  If your Target is a graph_nav waypoint, this pose will be relative to the waypoint you are navigating to. If no target was specified, this parameter will be ignored and the robot will stand in a generic pose.

Sit the robot prior to performing the action

Used in: ActionWrapper

(message has no fields)

Align the SpotCam to given reference image(s). The robot will initially point the camera in the direction specified by target_tform_sensor. Then, the robot will align the SpotCam by computing the homography between the live image(s) from the camera and the supplied reference image(s). Cannot be used with SpotCamPtz or RobotBodyPose

Used in: ActionWrapper

• repeated SpotCamAlignment.Alignment alignments = 2

  List of alignments to perform

• optional SE3Pose target_tform_sensor = 3

  Desired transform from the sensor to the waypoint. This is used to initially point the camera in the correct direction before refining the alignment using reference images.

• float final_zoom = 4

  Final zoom the camera should be after all alignments have finished

• repeated string target_sensor_ids = 5

  Optional list of sensor names which should be unobstructed after alignment

Used in: SpotCamAlignment

• float zoom = 1

  Camera zoom parameter

• string sensor_id = 2

  Sensor to use for alignment. The sensor must be registered with the sensor pointing service. The sensor_id is the name of the sensor given by the sensor pointing service's ListSensors RPC.

• oneof reference

  Image to use for alignment

  • string scene_object_id = 3

    Points at a world object in the waypoint snapshot corresponding to the waypoint of this action. The world object should contain the reference image.

  • ImageCaptureAndSource reference_image = 6

    Reference image to use for alignment and the camera source of the image.

• bool is_skipped = 4

  If true, this alignment will be skipped during playback

• optional spot_cam.PtzFocusState focus_state = 5

  Focus state used during alignment. Defaults to auto-focus.

Set the brightness of the LEDs on the SpotCam.

Used in: ActionWrapper

• map<int32, float> brightnesses = 1

  There are four LEDs at indices [0, 3]. The brightness for each LED may be set between [0.0, 1.0], where 0 is off and 1 is full brightness.

Set the pan, tilt, and zoom of the SpotCam.

Used in: ActionWrapper

• optional spot_cam.PtzPosition ptz_position = 1

  See bosdyn/api/spot_cam

If your mission has docks, autowalk can pause the mission to return to the dock if the battery gets too low. Use this message to control when this behavior happens.

Used in: Element

• float battery_start_threshold = 2

  Once charging, the robot will continue to charge until the battery level is greater than or equal to this threshold, at which point in time, the mission will start.

• float battery_stop_threshold = 3

  If the battery level is less than or equal to this threshold, the robot will stop what it is currently doing and return to the dock. Once the battery level is greater than or equal to the battery start threshold, the mission will resume.

Choreography elements required for the mission.

Used in: Walk

• repeated spot.ChoreographySequence choreography_sequences = 1

  Any sequences we need to play the mission.

• repeated spot.Animation animated_moves = 2

  Any animations we need if we want to play the sequence.

• optional RequestHeader header = 1

  Common request header.

• optional Walk walk = 2

  Walk to compile.

• bool treat_warnings_as_errors = 5

  If this is set to true, mission compilation will fail if the Walk contains parameters that are set incorrectly. This can be useful during development to help the developer find issues with their client (e.g., suppose the client UI allows a user to set a parameter incorrectly). If this is set to false, mission compilation is more likely to succeed for the same Walk because any parameters that are both incorrect and modifiable are modified during mission compilation.

• optional ResponseHeader header = 1

  Common response header.

• CompileAutowalkResponse.Status status = 2

  Result of compiling the mission.

• optional mission.Node root = 4

  Root node of compiled walk.

• repeated ElementIdentifiers element_identifiers = 5

  There will be one ElementIdentifier for each Element in the input Walk. The index of each ElementIdentifier corresponds to the index of the Element in the input Walk. Skipped elements will have default values for id's. (0 and empty string) Deprecated as of 5.0. The active_mission_text field in the mission service's State proto will indicate when the robot is undocking, navigating, performing an action, or docking at mission runtime.

• map<int32, FailedElement> failed_elements = 6

  If certain elements failed compilation, they will be reported back in this field. The map correlates the index of the Element in the input Walk to the FailedElement.

• optional NodeIdentifier docking_node = 7

  Final docking node.

• optional NodeIdentifier loop_node = 8

  Node that contains the main sequence of actions performed in the walk. In continuous playback mode, the walk repeats when this node completes.

Possible results of compiling a walk to mission.

Used in: CompileAutowalkResponse

• STATUS_UNKNOWN = 0

  Invalid status, do not use.

• STATUS_OK = 1

  Compilation succeeded.

• STATUS_COMPILE_ERROR = 2

  Compilation failed. The walk was malformed.

The dock itself and the target associated with it

Used in: Walk

• uint32 dock_id = 1

  The docking station ID of the dock corresponds to the number printed on the fiducial, below the part of the fiducial that looks like a QR code. Only fiducial IDs greater than or equal to 500 should be used here because they are reserved for docks.

• string docked_waypoint_id = 2

  To maximize reliability, at record time, the client should dock the robot while graph_nav is still recording. When the robot is finished docking, the client should create a waypoint on top of the dock, while the robot is docked, and then stop recording. The waypoint created while the robot is sitting on the dock should be specified here.

• optional Target target_prep_pose = 3

  When it is time for the robot to dock, it will approach this target before issuing docking commands. If the user is using graph_nav, the final waypoint in the NavigateRoute OR the waypoint ID in the NavigateTo MUST be at the docking prep pose. To do this, send a docking command to move the robot to the docking prep pose. Then, create a waypoint at the docking prep pose location. Graph_nav is responsible for navigating the robot to the docking prep pose. Once the robot is in the docking prep pose, the docking service does the rest.

• optional google.protobuf.Duration prompt_duration = 4

  At mission playback, if the robot is unable to reach the dock OR successfully dock, the mission will let the operator know with a user question. If the operator does not answer, the robot will safely power off. This parameter controls how long the operator has to answer. This parameter also controls how long robot will wait to retry to undock on a failed undock.

• bool disable_recharge = 9

  Whether the robot can use this dock for recharging or executing a return to dock and try again later failure behavior.

• bool disable_end = 10

  Whether the robot can end a mission on this dock.

An Element is the basic building block of the autowalk.

Used in: Walk

• string name = 1

  The name of an element may be anything, but it is good practice to choose something that describes the physical location and action that is occurring (e.g., boiler room laser scan).

• optional Target target = 2

  Location the robot should navigate to.

• optional FailureBehavior target_failure_behavior = 3

  Describes what to do if the robot fails to navigate to target.

• optional Action action = 4

  Action performed at target destination

• optional ActionWrapper action_wrapper = 5

  Actions performed by the robot and/or payloads prior to and during an action.

• optional FailureBehavior action_failure_behavior = 6

  Describes what to do if the robot fails to execute the action.

• bool is_skipped = 7

  Set to true to skip element.

• optional BatteryMonitor battery_monitor = 8

  If the mission requires more than one battery, the robot needs to return to the dock and charge before it can complete the mission. This field defines the battery percentage thresholds that at which the robot should pause and resume mission execution. Considering using various thresholds depending on the target's distance from the dock

• optional google.protobuf.Duration action_duration = 9

  Maximum duration of action execution time, including all wrappers. If they take longer than this duration, the action will be considered a failure. Not including, or including a zero duration will set the action to NOT have a timeout.

• string id = 10

  Unique identifier for this element. This will be embedded in various Data Acquisition captures and various logging bundles. This should be globally unique across all elements.

Used in: CompileAutowalkResponse, LoadAutowalkResponse

• optional NodeIdentifier root_id = 1

  Identifiable data for the root node of the element. Deprecated as of 4.0. Please use navigation_id instead.

• optional NodeIdentifier action_id = 2

  Identifiable data for action node of the element.

• optional NodeIdentifier navigation_id = 3

  Identifiable data for the navigation node of the element.

Used in: CompileAutowalkResponse, LoadAutowalkResponse

• repeated string errors = 1

  The reasons why this element failed. May not be provided by all elements.

• repeated string warnings = 2

  Compile time modification that resolved error(s).

Used in: Element

• int32 retry_count = 1

  The mission can automatically retry navigating to a waypoint or performing an action. Automatic retries can increase the probability of successfully navigating to a waypoint, but may cause the robot to take an unexpected path. Similarly, they can increase the probability of successfully collecting data for an action, but also increase the amount of time a mission takes. If the client does not want the robot to automatically retry navigating to a waypoint or performing an action, set this to 0. If the client wants the robot to automatically retry navigating to a waypoint or performing an action, set this to the desired number of retries. For example, if the client would like the action to be retried once, set this equal to 1. If this is unset or set to 0, no retry will occur.

• optional google.protobuf.Duration prompt_duration = 2

  At mission playback, if something fails (e.g., the robot gets stuck, an action fails), the user will get all possible actions as options in a question to choose from. If the user does not answer, the mission will fall back to the default behavior after this timeout. The default behaviors are defined by the default_behavior one_of. A minimum duration of 10 seconds is enforced.

• oneof default_behavior

  Sometimes, the robot may not be able to get to an action (for example, its path may be blocked). Similarly, while at a waypoint where an action is performed, that action may fail (for example, the sensor is not powered on). In case of such failures, the user should choose the desired behavior using this enum.

  • FailureBehavior.SafePowerOff safe_power_off = 3

  • FailureBehavior.ProceedIfAble proceed_if_able = 4

  • FailureBehavior.ReturnToStartAndTryAgainLater return_to_start_and_try_again_later = 5

  • FailureBehavior.ReturnToStartAndTerminate return_to_start_and_terminate = 6

If a failure occurs and the prompt has not been answered, the robot will proceed to the next action if able to do so. This may lead to different behavior at mission playback than at mission recording (e.g., the robot may take a different route, the robot may fail to collect the data for an action).

Used in: FailureBehavior

(message has no fields)

Only available in missions with a dock! If robot can get back to the dock, it will, and if it does, the mission will end.

Used in: FailureBehavior, WalkInterrupt.ConditionAndBehavior

(message has no fields)

Only available in missions with a dock! If a failure occurs and the prompt has not been answered, the robot will return to the start of the mission. Once at the start of the mission, the robot will attempt to dock. If successfully, robot will try again later after the specified delay.

Used in: FailureBehavior

• optional google.protobuf.Duration try_again_delay = 1

  How long to wait at start of mission (or on dock) before trying again. A minimum duration of 60 seconds is enforced.

If a failure occurs and the prompt has not been answered, the robot will sit down and power off. This is the safest option.

Used in: FailureBehavior, WalkInterrupt.ConditionAndBehavior

• optional SafePowerOffCommand.Request request = 1

These parameters apply to the entire autowalk.

Used in: Walk

• string group_name = 1

  If the mission contains data acquisitions, this will be their group name. The actual group name used will include the specified group name, and additional qualifiers to ensure its unique for each start of this mission.

• bool should_autofocus_ptz = 2

  If the mission contains SpotCAM PTZ actions, set this to true. At the start of the mission (or if the robot falls), the SpotCAM PTZ autofocus will be reset, thereby improving the quality of the subsequent PTZ captures.

• int32 self_right_attempts = 3

  The mission can automatically self-right the robot. Autonomous self-rights can damage the robot, its payloads, and its surroundings. If the user does not want the robot to self-right on its own, set this number to 0. If the user does want the robot to self-right itself, the user may set a maximum number of attempts so that the robot does not destroy itself by repeatedly falling and getting up and falling again.

• repeated Action.RemoteGrpc post_mission_callbacks = 4

  The callbacks that will be executed at the end of the mission. Functionality that is often found in post-mission callbacks includes uploading data to the cloud or sending an email. The callbacks will be executed serially (first in, first executed).

• bool skip_actions = 5

  It can be useful to have the robot run a walk without collecting data. If this boolean is set to true, the compiled mission will still navigate to the target of each element, however it will not actually perform the associated action & action wrappers.

• optional HriBehaviors hri_behaviors = 6

  Configurable options for Spot to perform extra behaviors in missions to communicate with nearby observers.

Options for Spot to perform additional human-robot interaction behaviors in missions to help communicate with observers.

Used in: GlobalParameters

• bool play_alert_behaviors = 1

  If true, Spot will tap its front-left foot twice if anomalies are discovered during an inspection. Alerts can be viewed in Orbit.

• bool play_undock_behaviors = 2

  If true, Spot will lift its legs twice before undocking.

• optional RequestHeader header = 1

  Common request header.

• optional Walk walk = 2

  Walk to compile

• repeated Lease leases = 3

  Leases that will be needed to validate the mission. Usually, no leases are necessary for validation, and this can be left empty.

• bool treat_warnings_as_errors = 5

  If this is set to true, mission compilation will fail if the Walk contains parameters that are set incorrectly. This can be useful during development to help the developer find issues with their client (e.g., suppose the client UI allows a user to set a parameter incorrectly). If this is set to false, mission compilation is more likely to succeed for the same Walk because any parameters that are both incorrect and modifiable are modified during mission compilation.

• optional ResponseHeader header = 1

  Common response header.

• LoadAutowalkResponse.Status status = 2

  Result of loading the mission.

• repeated LeaseUseResult lease_use_results = 3

  Results from any leases that may have been used. As part of mission validation, some of the non-mission leases may have been used.

• repeated mission.FailedNode failed_nodes = 5

  If certain nodes failed compilation or validation, they will be reported back in this field.

• repeated ElementIdentifiers element_identifiers = 7

  There will be one ElementIdentifier for each Element in the input Walk. The index of each ElementIdentifier corresponds to the index of the Element in the input Walk. Skipped elements will have default values for id's. (0 and empty string) Deprecated as of 5.0. The active_mission_text field in the mission service's State proto will indicate when the robot is undocking, navigating, performing an action, or docking at mission runtime.

• map<int32, FailedElement> failed_elements = 8

  If certain elements failed compilation, they will be reported back in this field. The map correlates the index of the Element in the input Walk to the FailedElement.

• int64 mission_id = 9

  Mission ID assigned by the mission service.

• optional NodeIdentifier docking_node = 10

  Final docking node.

• optional NodeIdentifier loop_node = 11

  Node that contains the main sequence of actions performed in the walk. In continuous playback mode, the walk repeats when this node completes.

Possible results of loading a mission.

Used in: LoadAutowalkResponse

• STATUS_UNKNOWN = 0

  Invalid status, do not use.

• STATUS_OK = 1

  The mission was loaded successfully.

• STATUS_COMPILE_ERROR = 2

  Compilation failed. The walk was malformed.

• STATUS_VALIDATE_ERROR = 3

  Load-time validation failed. Some part of the mission was unable to initialize.

Used in: CompileAutowalkResponse, ElementIdentifiers, LoadAutowalkResponse

• int64 node_id = 1

  Unique integer set by the mission service when loading a mission.

• string user_data_id = 2

  Unique string set by the autowalk service when compiling a walk.

The playback mode governs how many times the mission is played back (once or more), at what interval the playbacks should occur (e.g., every 2 hours), and if docking is involved, the battery level thresholds at which the robot should either (1) stop and charge or (2) start the playback process again.

Used in: Walk

• oneof mode

  • PlaybackMode.Once once = 2

  • PlaybackMode.Periodic periodic = 3

  • PlaybackMode.Continuous continuous = 4

The mission should be played continuously only stopping if a battery monitor stop threshold is crossed.

Used in: PlaybackMode

(message has no fields)

The mission should be played back once.

Used in: PlaybackMode

• bool skip_docking_after_completion = 1

  Deprecated as of 4.1. To skip docking after completion, set disable_end to true for all docks in the walk proto. Boolean to allow the robot to not dock after completing a mission.

The mission should be played back periodically.

Used in: PlaybackMode

• optional google.protobuf.Duration interval = 1

  The interval is the time that will elapse between the mission finishing and starting again. It is applied relative to the time at which the mission finishes. For example, if the user sets the interval to 2 hours, starts the mission at 12:00, and the mission takes one hour (finishes at 13:00), the next mission would start at 15:00, NOT 14:00. Next mission start time = current mission end time + interval

• int32 repetitions = 2

  The number of times the mission should be played back. If set to 1, the interval no longer applies and the mission will be played back once. If set to two or more, the mission will run that number of times, with the amount of time between playbacks equal to the interval. If set to zero, the mission will run "forever".

A Target is the location the robot should navigate to.

Used in: Dock, Element

• oneof target

  • Target.NavigateTo navigate_to = 1

  • Target.NavigateRoute navigate_route = 2

• optional Target.Relocalize relocalize = 3

  If set, upon reaching the target the robot will perform an explicit relocalization. This should increase the accuracy of the robots belief of it's position on the map. After relocalizing, the robot will re-navigate to the target.

• Target.TargetStowBehavior target_stow_behavior = 5

• bool success_when_goal_area_reached = 6

  If true, the robot is allowed to continue to perform the action Before it comes to a complete stop.

Tell the robot to follow a route to a waypoint. If the robot is off the route (i.e., "far" from the route) when NavigateRoute is sent, the robot may navigate in unexpected ways.

Used in: Target

• optional graph_nav.Route route = 1

  A route for the robot to follow.

• optional graph_nav.TravelParams travel_params = 2

  Parameters that define how to traverse and end the route. For example, the user may decide how close to the destination waypoint the robot needs to be in order to declare success.

• optional SE2Pose destination_waypoint_tform_body_goal = 3

  Passed through to graph_nav. See comment in graph_nav.proto.

Tell the robot to navigate to a waypoint. It will choose its route.

Used in: Target

• string destination_waypoint_id = 1

  A unique string corresponding to the waypoint ID that the robot should go to.

• optional graph_nav.TravelParams travel_params = 3

  Parameters that define how to traverse and end the route. For example, the user may decide how close to the destination waypoint the robot needs to be in order to declare success.

• optional SE2Pose destination_waypoint_tform_body_goal = 4

  Passed through to graph_nav. See comment in graph_nav.proto.

Used in: Target

• optional graph_nav.SetLocalizationRequest set_localization_request = 1

  Some SetLocalizationRequests require that waypoint snapshots contain full images. Make sure your client is downloading / storing / uploading full snapshots if you plan on using this feature in your client.

Used in: Target

• TARGET_STOW_BEHAVIOR_UNKNOWN = 0

  Will default to TARGET_STOW_BEHAVIOR_AUTO

• TARGET_STOW_BEHAVIOR_AUTO = 1

  Compiler will do some heuristics to figure out if we should stow. Headed back to dock = stow Headed to another action that doesn't use arm sensor pointing = stow Headed to another action that uses arm sensor pointing and is far away = stow Headed to another action that uses arm sensor pointing and is close = don't stow

• TARGET_STOW_BEHAVIOR_NEVER = 2

  Never ever stow the arm on the way to this action.

• TARGET_STOW_BEHAVIOR_ALWAYS = 3

  Always stow the arm on the way to this action.

Used in: CompileAutowalkRequest, LoadAutowalkRequest

• optional GlobalParameters global_parameters = 1

  Parameters that apply to the entire mission.

• optional PlaybackMode playback_mode = 2

  Governs the mode and frequency at which playbacks occur.

• string map_name = 7

  The name of the map this mission corresponds to.

• string mission_name = 4

  The name of the mission.

• repeated Element elements = 5

  The list of actions and their associated locations.

• repeated Dock docks = 6

  The docks the mission can dock at.

• string id = 8

  Unique identifier for this walk. This will be embedded in various Data Acquisition captures and various logging bundles. This should be globally unique across all walks.

• optional ChoreographyItems choreography_items = 9

  Choreography related dependencies (any sequences and animations a robot needs to play this walk).

• optional WalkInterrupt interrupts = 10

  Interrupts can be used to interrupt the normal flow of an autowalk. This could be useful for: - Getting the robot to power off when an onboard sensor determines an unsafe condition. - Having an external system that's internet connected inform the robot it's going to rain, so that the robot can return to the dock early. - Temporarily pausing the mission to get a closer look at a detected anomaly.

How are multiple interruptions handled? - SafePowerOff can never be overridden, and can override everything. - ReturnToStartAndTerminate can only be overridden by SafePowerOff, and can override everything else. - Node can't override anything except an actively running element. If multiple interrupts with "Node" as the condition_behavior are triggered, the first one triggered will run. When that behavior completes, all signals will be revaluated, and if the other interrupt is still high then that behavior will be triggered.

Used in: Walk

• repeated WalkInterrupt.DaqPluginSignal signals = 1

• repeated WalkInterrupt.ConditionAndBehavior conditions_and_behaviors = 2

Used in: WalkInterrupt

• string name = 1

  Only used for things like the autowalk report.

• oneof condition

  Should evaluate to true when this interrupt should occur.

  • mission.Condition condition_node = 2

• oneof behavior

  • FailureBehavior.SafePowerOff safe_power_off = 3

  • FailureBehavior.ReturnToStartAndTerminate return_to_start_and_terminate = 4

  • mission.Node behavior_node = 5

Used in: WalkInterrupt

• optional DataAcquisitionCapability capability = 4

• optional DataCapture data_capture = 2

• string blackboard_name = 3

  The DataCapture will be sent as part of a LiveDataRequest to the data acquisition plugin service. The service will return a CapabilityLiveData for that data_capture, which will be embedded in the mission blackboard at the following name, for use in the condition node.