eric-wieser's profile - activity

The problem is, then I have to pass it all the way down to foo - I don't want to make a huge mess of my API just to get

Can I detect the currently active nodelet? I have a helper function that I want to calls NODELET_INFO within: void foo(

Not so much the caller of foo, but the nodelet / callback queue which the current callback is being run by

Can I detect the currently active nodelet? I have a helper function that I want to calls NODELET_INFO within: void foo(

@rnunziata: I'm using a VM and having this problem. Any recommendations?

A solution that worked for me was to just clear all interactive markers and reinsert them all with the new colors. Surprisingly, this works even while a marker is being dragged in rviz

This package is now published!

Duplicate of http://answers.ros.org/question/17170...

I submitted the package here

It's passed some jenkins builds here

However, it doesn't show up as a package on the wiki, or in the software list.

Is there a step that I've missed? Or does the process take longer than a few days?

link for the lazy

setattr(x, y) should always be preferred over x.__setattr__(y)

"an array of cells in a 2D grid" isn't a particularly clear description.

1. What defines the spacing of the grid?
2. Is the array one or two dimensional? So many ros types use a 1D array to represent a 2D grid, so the type alone is not sufficient documentation
3. What does cells[i] represent?
4. Do all cells have to be XY-planar?
5. Do all cells have to be planar at all?
6. Do the cells even have to align to a grid?
7. is cell_width measured from the center or the corner?

Why is this question closed? @tfoote. I have this problem, and would like a solution

Where is the official source for the nxt packages? The source link on the wiki page is dead

for c in config iterates over the keys of the config, not the values. I think you want:

host = rospy.get_param("~host", None)
sock = nxt.locator.find_one_brick(host)
b = sock.connect()

config = rospy.get_param("~"+ns)
components = []
for k, c in config.items():
    # do something with k - it might be useful
    rospy.loginfo("Creating %s with name %s on %s",c['type'],c['name'],c['port'])
    if c['type'] == 'motor':
        components.append(Motor(c, b))
    elif c['type'] == 'touch':
        components.append(TouchSensor(c, b))
    elif c['type'] == 'ultrasonic':
        components.append(UltraSonicSensor(c, b))
    elif c['type'] == 'color':
        components.append(ColorSensor(c, b))
    elif c['type'] == 'intensity':
        components.append(IntensitySensor(c, b))
    elif c['type'] == 'gyro':
        components.append(GyroSensor(c, b))
    elif c['type'] == 'accelerometer':
        components.append(AccelerometerSensor(c, b))
    else:
        rospy.logerr('Invalid sensor/actuator type %s'%c['type'])

What does print(config) give you?

I've submitted an issue

@ahendrix: The package name above is a link to the github repo, containing both of those things

Here's the contents of Int32MultiArray.msg:

# Please look at the MultiArrayLayout message definition for
# documentation on all multiarrays.

MultiArrayLayout  layout        # specification of data layout
int32[]           data          # array of data

And here's the contents of MultiArrayLayout

# The multiarray declares a generic multi-dimensional array of a
# particular data type.  Dimensions are ordered from outer most
# to inner most.

MultiArrayDimension[] dim # Array of dimension properties
uint32 data_offset        # padding bytes at front of data                         (A)

# Accessors should ALWAYS be written in terms of dimension stride
# and specified outer-most dimension first.
# 
# multiarray(i,j,k) = data[data_offset + dim_stride[1]*i + dim_stride[2]*j + k]    (B)
<snip>

Uh oh - contradiction! Is .layout.data_offset the offset in bytes (A) or the offset in words (B)? If the former, how are we supposed to adjust for something unaligned like data_offset = 3?

But data.data will still be a 1d array of bytes, not a 3d image array of the right type

I've thrown together a package that tries to solve the "How can I convert ROS's <X> into a numpy array" class of problems: ros_numpy. Using this, the solution becomes:

arr = ros_numpy.numpify(img_msg)