profile
viewpoint

locusrobotics/fuse 264

The fuse stack provides a general architecture for performing sensor fusion live on a robot. Some possible applications include state estimation, localization, mapping, and calibration.

locusrobotics/robot_navigation 209

Spiritual successor to ros-planning/navigation.

locusrobotics/catkin_virtualenv 45

Bundle python requirements in a catkin package via virtualenv

locusrobotics/qgis_ros 28

ROS QGIS Plugin prototype

locusrobotics/aiorospy 11

asyncio wrapper for rospy

locusrobotics/fuse_rl 8

robot_localization models for the fuse package

locusrobotics/json_transport 6

A simple way to transport dynamic data over ROS comms

locusrobotics/copyrightify 4

Apply copyright and license templates to source files.

locusrobotics/imu_tools 2

ROS tools for IMU devices

issue commentlocusrobotics/qgis_ros

Unavailable layer on QGIS

I will try that and get back to you whatever the outcome is. Thank you so much for your help!

antoinepiedfert

comment created time in 2 days

issue commentlocusrobotics/qgis_ros

Unavailable layer on QGIS

Try to record some of your topic data into a bagfile and replay it that way. If it fails, and the bagged data is not sensitive, maybe you can send it to me and I can try doing some debugging.

Apologies, it's difficult to provide help without being able to reproduce the problem on my end.

antoinepiedfert

comment created time in 2 days

issue commentlocusrobotics/qgis_ros

Unavailable layer on QGIS

Thank you for your answer. I am not sure I understand correctly all of your questions so apologies if my answers are a bit confusing.

I tried with several topic types : sensor_msgs/NavSatFix or nav_msgs/Odometry and many others but all get the same error. QGIS works fine with .shp layers without using the plugin. I can see all the messages in those topics from rostopic echo so I know they exist. But if you mean can I see the json-like data generated by your plugin with rostopic echo - which I am not sure I'm supposed to be able to do - then no I can't. It looks like a uri is generated but no file or message is written there. What confuses me is that there is no crash or error related to a failure of QgsVectorLayer - which is why I added that layer .isValid() test in the first place. I haven't tried working with bags yet, so I don't know if the problem would be the same.

antoinepiedfert

comment created time in 2 days

issue commentlocusrobotics/qgis_ros

Unavailable layer on QGIS

Hello,

I haven't run into that before and am not immediately sure what to suggest. I would probably try to bifurcate the problem a little and see where you get. Can you load any other layer? What is the topic type for the layer(s) you're trying to load? Live or from a bag? Can you see the data from rostopic echo?

If you're comfortable, maybe try to remove the layer.isValid() test and see if it crashes and if the crash gives you a better error. Admittedly that's a pretty bad error message I provide.

antoinepiedfert

comment created time in 2 days

issue openedlocusrobotics/qgis_ros

Unavailable layer on QGIS

Hi @ablakey,

I've been trying to make your plugin work with my project. It looks like everything works fine until the QgsVectorLayer command is called in translator.py: layer = QgsVectorLayer(uri, topicName, 'rosvectorprovider'). The following lines: if not layer.isValid(): print("Layer failed to load!") I implemented immediately after said command does return an error.

To be more specific, all of my topics are detected and appear correctly in the available topics table from your plugin GUI. But whenever I select any of them and ask to create a layer, an empty layer is created with the expected name and source uri, but an error appears that says "Unavailable layer! Layer data source could not be found".

It seems like the problem comes from the provider. Have you encountered this issue before?

created time in 2 days

push eventlocusrobotics/wireless

locus-services

commit sha daf2645f67982d8b8e4c7aacebf552a646b4d8c6

Tailor: Updating Jenkinsfile

view details

push time in 3 days

push eventlocusrobotics/urg_node

locus-services

commit sha a71529760345c38de9363cb905897ed0c8624b65

Tailor: Updating Jenkinsfile

view details

push time in 3 days

push eventlocusrobotics/tf2_2d

locus-services

commit sha 2dc3fd72b13c60a8bd80759f49592c43964a4bb3

Tailor: Updating Jenkinsfile

view details

push time in 3 days

push eventlocusrobotics/json_transport

locus-services

commit sha 37f256bb5c420af973c0f7f14571a538e1283e19

Tailor: Updating Jenkinsfile

view details

push time in 3 days

push eventlocusrobotics/catkin_virtualenv

locus-services

commit sha 25c6c745a11a4311a4bc1be1fcfefb5609adee30

Tailor: Updating Jenkinsfile

view details

push time in 3 days

push eventlocusrobotics/aiorospy

locus-services

commit sha de8354e5c95a82f0fab9cda9cb6cddb06d98d2a3

Tailor: Updating Jenkinsfile

view details

push time in 3 days

created taglocusrobotics/tailor-meta

tag0.1.15

created time in 3 days

delete branch locusrobotics/tailor-meta

delete branch : use-build-label

delete time in 3 days

push eventlocusrobotics/tailor-meta

Gary Servin

commit sha ad15fd8e78288b68ac0023d65fe9675972871b39

Use build_label as the top level dir (#18)

view details

push time in 3 days

PR merged locusrobotics/tailor-meta

Use build_label as the top level dir

The build process is still uploading the artifacts to the release_track dir, this fixes it to use the release_label instead

+1 -1

0 comment

1 changed file

garyservin

pr closed time in 3 days

PullRequestReviewEvent

create barnchlocusrobotics/robot_navigation

branch : devel

created branch time in 3 days

PR opened locusrobotics/tailor-meta

Reviewers
Use build_label as the top level dir

The build process is still uploading the artifacts to the release_track dir, this fixes it to use the release_label instead

+1 -1

0 comment

1 changed file

pr created time in 3 days

create barnchlocusrobotics/tailor-meta

branch : use-build-label

created branch time in 3 days

created taglocusrobotics/tailor-image

tag0.1.47

created time in 3 days

delete branch locusrobotics/tailor-image

delete branch : RST-3869_Single-index-entry-bare-metal

delete time in 3 days

push eventlocusrobotics/tailor-image

Gary Servin

commit sha 2bc6295c87d214ef4b80293a5c3af74e31a7003a

Use same timestamp for multiple images (#55) * Use same timestamp for multiple images * Fix wrong name * Use idiomatic way

view details

push time in 3 days

push eventlocusrobotics/tailor-image

Gary Servin

commit sha 65ec5602f2bba22b80a28af90e90d2358fbecca5

Use idiomatic way

view details

push time in 3 days

Pull request review commentlocusrobotics/tailor-image

Use same timestamp for multiple images

 def update_image_index(release_label, apt_repo, common_config, image_name):         if error.response['Error']['Code'] == 'NoSuchKey':             click.echo('Index file doesn\'t exist, creating a new one') -    data[date_time] = image_data+    if timestamp in data:

the idiomatic python way here is

try:
  ...
except KeyError:
  ...
``

to avoid the redundant 'in' check
garyservin

comment created time in 3 days

PullRequestReviewEvent

push eventlocusrobotics/tailor-image

Gary Servin

commit sha 300981b763b1410c9eddcb8cf844fd094ec46008

Fix wrong name

view details

push time in 3 days

PullRequestReviewEvent

Pull request review commentlocusrobotics/tailor-image

Use same timestamp for multiple images

 def update_image_index(release_label, apt_repo, common_config, image_name):         if error.response['Error']['Code'] == 'NoSuchKey':             click.echo('Index file doesn\'t exist, creating a new one') -    data[date_time] = image_data+    if timestamp in data:+        data[timestamp] = merge(data[timestamp], image_data)

yeah, thanks!

garyservin

comment created time in 3 days

Pull request review commentlocusrobotics/tailor-image

Use same timestamp for multiple images

 def update_image_index(release_label, apt_repo, common_config, image_name):         if error.response['Error']['Code'] == 'NoSuchKey':             click.echo('Index file doesn\'t exist, creating a new one') -    data[date_time] = image_data+    if timestamp in data:+        data[timestamp] = merge(data[timestamp], image_data)

should this be merge_dicts?

garyservin

comment created time in 3 days

more