-
Notifications
You must be signed in to change notification settings - Fork 190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Image/PointCloud Snapshot as a service #105
base: jade-devel
Are you sure you want to change the base?
Changes from all commits
62b378a
72fcbee
f2f302b
aacfcfc
9236c56
f115ce8
d2021ad
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
# dense_cloud = true, if the cloud has to be dense (ordered) | ||
bool dense_cloud | ||
|
||
# exposure in milliseconds (0 indicates autoexposure) | ||
uint32 exposure | ||
|
||
uint8 raw_data | ||
uint8 NO_RAW_DATA = 0 | ||
uint8 GRAYSCALE = 1 | ||
uint8 RGB = 2 | ||
|
||
--- | ||
|
||
# cloud is the returning point cloud | ||
sensor_msgs/PointCloud2 cloud | ||
|
||
# image is the 2d data form the camera | ||
sensor_msgs/Image image | ||
|
||
--- | ||
|
||
uint32 percentage_completed |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
# Point Cloud as a service | ||
|
||
# REQUEST: | ||
|
||
# dense_cloud = true, if the cloud has to be dense (ordered) | ||
bool dense_cloud | ||
|
||
# exposure in milliseconds (0 indicates autoexposure) | ||
uint32 exposure | ||
|
||
--- | ||
|
||
# RESPONSE: | ||
|
||
# cloud is the returning point cloud | ||
sensor_msgs/PointCloud2 cloud | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
# Image as a service | ||
|
||
# REQUEST | ||
|
||
# exposure in milliseconds (0 indicates autoexposure) | ||
uint32 exposure | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There's the same issue here. Unless you're going to provide all the settings providing just one doesn't make much sense. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, I agree. Providing one parameter is quite arbitrary and not general. I can modify both srv with an std_msgs/Empty in the request side. |
||
|
||
--- | ||
|
||
# RESPONSE: | ||
|
||
# image is the returning raw image | ||
sensor_msgs/Image image | ||
|
||
# camera info, which includes intrinsics calibration | ||
sensor_msgs/CameraInfo camera_info | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you really expect to be setting the exposure time for a cloud? This seems to be breaking several abstractions that you must know about the sensor's parameters and lighting situation to request a snapshot?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you mean to let the exposure config through another mechanism like, for instance, dynamic reconfigure, so keep the request even more simple ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. This standalone argument means nothing unless you know a lot more about the system. It has implications for side effects too, such as will this modify the system if it's already running with the exposure setting? What does the exposure setting mean if this snapshot is implemented with a data source such as a laser?