-
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
Remove dependency on jsk_perception for separated build #1820
Conversation
humm, by this change, ros-indigo-jsk-perception will not donwloaded if you apt-get install ros-indigo-jsk-pcl-ros, and you failed to run sample program. |
Yeah, I think that is problem. |
humm, I thought adding jsk_perception to test_depends, but it seems that
◉ Kei Okada On Fri, Aug 5, 2016 at 5:22 PM, Kentaro Wada [email protected]
|
Why you are referring to opencv_apps? |
just to confirm that
but that is not included in deb depends
|
It is described as below here:
|
If the jsk_perception is added as test_depends, the build of jsk_perception will be skipped when building jsk_pcl_ros? |
i thought adding jsk_perception to test_depends is ok for you
but it does not bring jsk_preception when you apt-get jsk_pcl_ros ◉ Kei Okada On Thu, Aug 11, 2016 at 4:43 PM, Kentaro Wada [email protected]
|
72e10a0
to
9138d0d
Compare
There are no tests in jsk_pcl_ros that depend on jsk_perception but launch files. |
9138d0d
to
dc9912c
Compare
Actually, it fails because of timeout even if we separate these packages, so moving to Travis seems impossible at this time.
I see, I agree that separating completely 2D/3D processing seems impossible, but I think that does not indicate jsk_pcl_ros and jsk_perception are not separable. I just prefer dependency graph like below, because both jsk_pcl_ros and jsk_perception are very large package. In the figure, I use purple that depends on both 2D/3D packages, so I agree that it is too difficult to separate `jsk_recognition_utils` to 2D and 3D completely, but I think separating `jsk_pcl_ros` and `jsk_perception` is not so difficult. |
ok, merged this PR, but please do not hesitate to write code depend on jsk_perception, as we discussed these days, 2D image processing has been long history on research and if we can write 3D perception code based on 2D depth image, we can make use of algorithm developed in 2D image processing, i.e. deep learning image segmentation, so at this moment , what we should do is how to find the 2D image processing algorithm that used in Depth or 2.5D image processing or find completely new 3D algorithm |
I see. Thank you for the advice. But is that ok to merge this before releasing 0.3.22? |
Some node in jsk_perception is used in the sample launch files in jsk_pcl_ros,
and this is why jsk_perception is added as run_depend.
However, dependency on jsk_perception by jsk_pcl_ros always requires build of
jsk_perception even when the user want to use jsk_pcl_ros only.
I think this is problem, because jsk_perception is also a large package,
and recognition packages for 2D and 3D should be separated.