Skip to content
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

Enable samplebot sample on melodic #250

Merged

Conversation

Naoki-Hiraoka
Copy link
Contributor

@Naoki-Hiraoka Naoki-Hiraoka commented Apr 12, 2020

This PR includes #246, #249.
Samplerobot walked in melodic

The video is 10x fast because my PC (ThinkPad T440s) is not so fast and simulation is slow.
video

@Naoki-Hiraoka Naoki-Hiraoka changed the title [WIP][on #246 #249]Enable samplebot sample melodic [WIP][on #246 #249]Enable samplebot sample on melodic Apr 12, 2020
@Naoki-Hiraoka
Copy link
Contributor Author

TRAVIS PASSED!!!

@Naoki-Hiraoka Naoki-Hiraoka changed the title [on #246 #249]Enable samplebot sample on melodic [on #249]Enable samplebot sample on melodic Apr 13, 2020
.rosinstall Outdated
@@ -0,0 +1,30 @@
- git:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is this .rosinstall for?
Could you write usage of this on README?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file is same as .travis.rosinstall of master.
I think we don't need this file, and I don't know the usage of some packages like https://svn.code.sf.net/p/jsk-ros-pkg/code/trunk/openrave_planning/collada_robots.
But I could not erase this file because these URL may be needed in the future.

Copy link
Collaborator

@pazeshun pazeshun Apr 14, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see. How about just commenting out unnecessary lines of .travis.rosinstall and adding comments like (@Naoki-Hiraoka) I don't know what is for
I think jsk_model_tools, jsk_roseus, and collada_robots are added at #36 .
And nowadays, we can use jsk_model_tools and jsk_roseus from apt, so they are no more required and can be removed even from comments.
@k-okada Do you remember why you added collada_robots?
I searched source code at c5ea4a4, but I couldn't find about collada_robots.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you. I fixed it.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@k-okada

@k-okada Do you remember why you added collada_robots?
I searched source code at c5ea4a4, but I couldn't find about collada_robots.

Sorry, but do you have any comment about this?

Copy link
Collaborator

@pazeshun pazeshun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you also test this on kinetic?

@Naoki-Hiraoka Naoki-Hiraoka changed the title [on #249]Enable samplebot sample on melodic Enable samplebot sample on melodic Apr 13, 2020
@Naoki-Hiraoka
Copy link
Contributor Author

Could you also test this on kinetic?

I have tested this PR on my kinetic PC now. SampleRobot sample successfully worked.

@Naoki-Hiraoka
Copy link
Contributor Author

@pazeshun @k-okada
It was reported that this PR worked without problems in a b4 environment.
I would like to merge this PR and #251.
Is there something I need to fix?

(After this PR is merged, we will be able to test start-jsk/rtmros_tutorials and then test start-jsk/rtmros_hrp2 start-jsk/rtmros_choreonoid for melodic)

@pazeshun
Copy link
Collaborator

@Naoki-Hiraoka @k-okada
We stopped at #250 (comment)

@knorth55
Copy link
Member

I checked with my melodic robot, and it successfully walked!

@Naoki-Hiraoka
Copy link
Contributor Author

On melodic, /opt/ros/melodic/share/hrpsys/srcis not installed with ros-melodic-hrpsys, so hrpsys_gazebo_general/iob needs to be built with hrpsys source.

@Naoki-Hiraoka Naoki-Hiraoka force-pushed the enable-samplebot-sample-melodic branch from 8b01130 to 45ff056 Compare April 23, 2020 06:25
@k-okada k-okada merged commit c8421d8 into start-jsk:master May 4, 2020
@k-okada
Copy link
Member

k-okada commented May 4, 2020

On melodic, /opt/ros/melodic/share/hrpsys/srcis not installed with ros-melodic-hrpsys, so hrpsys_gazebo_general/iob needs to be built with hrpsys source.

if we release hrpsys on meloidc, can we remove them from .rosinstall? if so we can remove

- git:
uri: https://github.com/fkanehiro/hrpsys-base
local-name: hrpsys
Or, do we need latest version of hrpsys to let SampleRobot walk?

@Naoki-Hiraoka
Copy link
Contributor Author

On melodic, /opt/ros/melodic/share/hrpsys/srcis not installed with ros-melodic-hrpsys, so hrpsys_gazebo_general/iob needs to be built with hrpsys source.

if we release hrpsys on meloidc, can we remove them from .rosinstall? if so we can remove

- git:
uri: https://github.com/fkanehiro/hrpsys-base
local-name: hrpsys

Or, do we need latest version of hrpsys to let SampleRobot walk?

We do not need latest version of hrpsys to let SampleRobot walk.

I'm wondering what .rosinstall should be.
As you said, we can remove .rosinstall and small .rosinstall is better.
On the other hand, it is better to test both with and without latest version of hrpsys because many researchers use latest version of hrpsys. We can test both situation by setting USE_DEB=true(without latest version of hrpsys) or USE_DEB=false(with latest version of hrpsys) respectively.

Could you tell me what kind of policy we should take?
This decision will affect .rosinstall of rtmros_gazebo, rtmros_tutorials, rtmros_hrp2, rtmros_choreonoid, ....

@pazeshun
Copy link
Collaborator

@k-okada @Naoki-Hiraoka

We can test both situation by setting USE_DEB=true(without latest version of hrpsys) or USE_DEB=false(with latest version of hrpsys) respectively.

I think we sometimes have three situations about travis testing of a package as follows:

  • Test the package on travis with released deb of the other packages (USE_DEB=true)
  • Test the package on travis with source of some other packages because they are not released
  • Test the package on travis with source of some other packages in order to check if the target package works with the latest version of other packages

Can we separate the second and the third situations?
I know USE_DEB=false and USE_DEB=source exist, but I don't know which to use for each situation.

In @Naoki-Hiraoka 's case, hrpsys exists for the third situation.

@Naoki-Hiraoka
Copy link
Contributor Author

I opened new PR #255 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants