udgcirs / marine_ros_conventions_discussion Goto Github PK
View Code? Open in Web Editor NEWA repossitory to discuss about new standard marine messages
A repossitory to discuss about new standard marine messages
Can't hurt to put a license on from the start. Since we want wide use and adoption, I'd suggest BSD or MIT.
This repository has no existing draft.
From the workshop notes:
Other attached sensors (DO, Fluorometer) don't go in this msg.
@ivaughn brought this up in #5, which I think is more of a general issue, worth clarifying and adding to the general message standards (#4):
More generally, are we at all concerned about the performance requirements necessary to hit up TF for each beam? The PR2 had to compact its TF tree for performance reasons, just curious where that limiti is.
Currently, over 60 message ideas are waiting to become ROS messages. Before we start 60 separate discussions, maybe some ground rules should be defined. What do we aim for with the messages? What are general rules for ROS messages we should comply with?
Several message suggestions/abbreviations from the work shop are not clear (enough) to me:
This looks like copypasta from the line above (float32 range_max # maximum range value [m]
). If I interpret the use of the variable correctly, this may better be described with
float32 range_increment # resolution of the discrete beam range measurements [m]
range_resolution might also be a more descriptive name:
float32 range_resolution # [m]
or
float32 range_resolution # minimum difference between two discrete beam range measurements [m]
Hi everyone,
have you already added marine_ros_conventions_discussion/sensor_msgs/DVL.msg to ROS sensor_msgs, i.e., is there a <sensor_msgs/DVL.h> available to use already?
Thanks,
Bojan.
Often, Doppler Velocity Log and Acoustic Doppler Current Profiler come as a single device. If I understand the current DVL msg correctly, it can be enriched with current profile data for each of the beams.
From the workshop notes:
#
good beams#
binsI don't think all of the notes are represented in the current msg proposal, but I am also not sure I understand all of the suggestions from the workshop.
I struggle to identify the difference between the two sonar messages. Both seem to be based on the laser scan messages from sensor_msgs.
Extra fields in ProfilingSonar:
Extra fields in Imaging Sonar:
It appears two are slightly different implementations of the same concept:
range_resolution <-> range_increment
intensities <-> beams
With my current knowledge of sonar sensing I can not assign a sonar device clearly to either of these messages, and know of no argument why both are needed. As a merge of the two I would suggest https://github.com/smaria/marine_ros_conventions_discussion/blob/master/sensor_msgs/SonarScan.msg
It has become apparent in #2 that multibeam data cannot be dealt with by a single message format that fits all. We need to better understand which processing&use exist, where existing formats are best used, and which additional message types are needed.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.