jason-ros

Description

This repository is being used to develop a possible integration between Jason and ROS.

This is being done by customizing the agent architecture, AgArch class, to include ROS functionalities, using rosjava. Also, an intermediary ros node, called HwBridge, is being used to serve as bridge between Jason and Hardware nodes.

Basically, the Jason agent publishes the action it wants to perform into the topic ‘/jason/actions’ and it subscribes to the topic ‘/jason/actions_status’ to receive the status of the action sent and to the topic ‘/jason/percepts’/ to receive new perceptions.

In other hand, HwBridge node subscribes to ‘/jason/actions’ and using the information contained in the action_manifest it translates the action received and sends it to the right topic/service, when the action is completed it publishes its status into ‘/jason/actions_status’ topic. Also, it publishes perceptions into ‘/jason/percepts’ topic according to what is defined in perception_manifest.

Docker images containing this repo and needed environment can be found at dockerhub.

armv7 version at branch armv7 (out of date)

Usage

mas2j

Use jasonros.RosArch

MAS rosbridge_agents {

    infrastructure: Centralised

    agents: sample_agent agentArchClass jasonros.RosArch;
}

Gradle

Include jason, jasonros and jasonros_msgs to gradle:

repositories {
   mavenCentral()
   jcenter()

   maven { url "https://raw.github.com/rosjava/rosjava_mvn_repo/master" }
   maven { url "https://raw.github.com/jason-lang/mvn-repo/master" }
   maven { url "http://jacamo.sourceforge.net/maven2" }
}

dependencies {
   compile group: 'org.jason-lang',     name: 'jason' ,   version: '2.4-SNAPSHOT'
   compile group: 'org.jason-lang',     name: 'jasonros' ,   version: '1.8'
   compile group: 'org.jason-lang',     name: 'jasonros_msgs' ,   version: '1.8'
}

Edit Manifests

In order to use this project, one must modify the action_manifest and perception_manifest to include the information about the actions being performed and the perceptions of interest.

action_manifest:

[teste]
method = topic
name = /hw/teste
msg_type = String
dependencies = std_msgs.msg
params_name = data
params_type = str
latch = True

method - topic or service

name - name of the topic or service

msg_type - type of the message e.g. String, Bool, Int32

dependencies - python module which contains the message type e.g. std_msgs.msg, mavros_msgs.msg

params_name - name of the parameter being sent

params_type - type of the parameter e.g. bool, str, int. If not inclued the default type is str

latch - if the action should be latched e.g. true, True, yes, 1, False, false. If not included the default is true

For more examples of actions you can take a look at this action_manifest

perception_manifest:

[state]
name = /hw/teste2
msg_type = String
dependencies = std_msgs.msg
args = data
buf = add

name - name of the topic or service

msg_type - type of the message e.g. String, Bool, Int32

dependencies - python module which contains the message type e.g. std_msgs.msg, mavros_msgs.msg

args - fields that you want to perceive

buf (belief update function) - if the perception should be added or updated in the belief base. If not inclued the default option is update

This perception would be added into the agent belief base as state(data)

File truncated at 100 lines see the full file