public class BackendUtils
extends java.lang.Object
Constructor and Description |
---|
BackendUtils() |
Modifier and Type | Method and Description |
---|---|
static int |
countNengoDimension(int[] dimensionSizes)
This converts (Jython) description of dimension sizes into length of
single vector for Nengo.
|
static Backend |
select(java.lang.String topic,
java.lang.String messageType,
org.ros.node.ConnectedNode myRosNode,
boolean publish)
Here are message types which have predefined number of dimensions (e.g.
|
static Backend |
select(java.lang.String topic,
java.lang.String messageType,
int[] dimensionSizes,
org.ros.node.ConnectedNode myRosNode,
boolean publish)
Here are Backends which operate over the message types with
user-definable data dimensionality.
|
static java.util.List<std_msgs.MultiArrayDimension> |
setRosDimensions()
This is experimental and it should set the layout of ROS message
according to dimensionSizes parsed from Jython script.
|
public static Backend select(java.lang.String topic, java.lang.String messageType, int[] dimensionSizes, org.ros.node.ConnectedNode myRosNode, boolean publish) throws MessageFormatException, UnsupportedMessageFormatExc
topic
- messageType
- dimensionSizes
- myRosNode
- publish
- MessageFormatException
UnsupportedMessageFormatExc
public static Backend select(java.lang.String topic, java.lang.String messageType, org.ros.node.ConnectedNode myRosNode, boolean publish) throws MessageFormatException, UnsupportedMessageFormatExc
topic
- messageType
- myRosNode
- publish
- MessageFormatException
UnsupportedMessageFormatExc
public static int countNengoDimension(int[] dimensionSizes) throws MessageFormatException
dimensionSizes
- each number represents size of a dimension (e.g. 640x480)MessageFormatException
public static java.util.List<std_msgs.MultiArrayDimension> setRosDimensions()
d
- list of dimensionSizes obtained bt rosMessage.getLayout(), it is empty..dimensionSizes
- information parsed from Jython