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.

Sign up for GitHub

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

Jump to bottom

add new arena model #6

Merged
merged 1 commit into from
Jan 6, 2016
Merged

add new arena model #6

merged 1 commit into from
Jan 6, 2016

Conversation

tongtybj
Copy link
Member

@tongtybj tongtybj commented Jan 5, 2016

@cretaceous-creature
Please chk

  1. I add new arena model. which contains the texture material.
    just have a try with: $ gazebo mbzirc_arena.world
    I also confirm that new arena is ok for husky:
    $ROBOT_INITIAL_POSE="-x 65 -y -25 -z 1" roslaunch jsk_mbzirc_ugv_sim husky_mbzirc.launch
  2. I suppose that the mbzirc_arena.world for each task should be specialized, such as mbzirc_arena_task1.world, mbzirc_arena_task2.world, mbzirc_arena_task3.world, mbzirc_arena_task4.world. Because the environment of each task is slightly different.
  3. I also suppose that the it is better to move the directory "gazebo_model" into package "jsk_mbzirc_common" or change the "gazebo_model" to ros package.

@cretaceous-creature
Copy link
Collaborator

And for the husky, the deb package is buggy and without gripper,
we need to build from the recent source code if we want to perform the
simulation.

Are we going to use husky?

2016-01-05 16:53 GMT+09:00 趙 漠居 notifications@github.com:

I add new arena model. which contains the texture material.
just have a try with: $ gazebo mbzirc_arena.world
I also confirm that new arena is ok for husky:
$ROBOT_INITIAL_POSE="-x 65 -y -25 -z 1" roslaunch jsk_mbzirc_ugv_sim
husky_mbzirc.launch
2.

I suppose that the mbzirc_arena.world for each task should be
specialized, such as mbzirc_arena_task1.world, mbzirc_arena_task2.world,
mbzirc_arena_task3.world, mbzirc_arena_task4.world. Because the environment
of each task is slightly different.
3.

I also suppose that the it is better to move the directory
"gazebo_model" into package "jsk_mbzirc_common" or change the
"gazebo_model" to ros package.

You can view, comment on, or merge this pull request online at:

#6
Commit Summary

  • add new arena model

File Changes

Patch Links:

—
Reply to this email directly or view it on GitHub
#6.

@tongtybj
Copy link
Member Author

tongtybj commented Jan 5, 2016

uh, it seems like building from source is a boring task, but still not
difficult.
We can use husky+ur5 just for simuliation, like the
percepition/munipulation process.

But the best choice I believe is the car you showed in taobao + the staro
arm.
The only thing I am concern about the staro arm is that there is no
professional person in our team to deal with urata-board series product.

2016-01-05 17:58 GMT+09:00 Chen notifications@github.com:

And for the husky, the deb package is buggy and without gripper,
we need to build from the recent source code if we want to perform the
simulation.

Are we going to use husky?

2016-01-05 16:53 GMT+09:00 趙 漠居 notifications@github.com:

I add new arena model. which contains the texture material.
just have a try with: $ gazebo mbzirc_arena.world
I also confirm that new arena is ok for husky:
$ROBOT_INITIAL_POSE="-x 65 -y -25 -z 1" roslaunch jsk_mbzirc_ugv_sim
husky_mbzirc.launch
2.

I suppose that the mbzirc_arena.world for each task should be
specialized, such as mbzirc_arena_task1.world, mbzirc_arena_task2.world,
mbzirc_arena_task3.world, mbzirc_arena_task4.world. Because the
environment
of each task is slightly different.
3.

I also suppose that the it is better to move the directory
"gazebo_model" into package "jsk_mbzirc_common" or change the
"gazebo_model" to ros package.

You can view, comment on, or merge this pull request online at:

#6
Commit Summary

  • add new arena model

File Changes

Patch Links:

—
Reply to this email directly or view it on GitHub
#6.

—
Reply to this email directly or view it on GitHub
#6 (comment).

@cretaceous-creature
Copy link
Collaborator

The car from taobao is only 10+kg, it is unable to carry more than 20kg...
And as it become heavier, it become slower....
we need a 4m/s UGV....

2016-01-05 18:07 GMT+09:00 趙 漠居 notifications@github.com:

uh, it seems like building from source is a boring task, but still not
difficult.
We can use husky+ur5 just for simuliation, like the
percepition/munipulation process.

But the best choice I believe is the car you showed in taobao + the staro
arm.
The only thing I am concern about the staro arm is that there is no
professional person in our team to deal with urata-board series product.

2016-01-05 17:58 GMT+09:00 Chen notifications@github.com:

And for the husky, the deb package is buggy and without gripper,
we need to build from the recent source code if we want to perform the
simulation.

Are we going to use husky?

2016-01-05 16:53 GMT+09:00 趙 漠居 notifications@github.com:

I add new arena model. which contains the texture material.
just have a try with: $ gazebo mbzirc_arena.world
I also confirm that new arena is ok for husky:
$ROBOT_INITIAL_POSE="-x 65 -y -25 -z 1" roslaunch jsk_mbzirc_ugv_sim
husky_mbzirc.launch
2.

I suppose that the mbzirc_arena.world for each task should be
specialized, such as mbzirc_arena_task1.world,
mbzirc_arena_task2.world,
mbzirc_arena_task3.world, mbzirc_arena_task4.world. Because the
environment
of each task is slightly different.
3.

I also suppose that the it is better to move the directory
"gazebo_model" into package "jsk_mbzirc_common" or change the
"gazebo_model" to ros package.

You can view, comment on, or merge this pull request online at:

#6
Commit Summary

  • add new arena model

File Changes

Patch Links:

—
Reply to this email directly or view it on GitHub
#6.

—
Reply to this email directly or view it on GitHub
#6 (comment).

—
Reply to this email directly or view it on GitHub
#6 (comment).

@tongtybj
Copy link
Member Author

tongtybj commented Jan 5, 2016

One solution you said is to change the motor_driver to urata-board?
Is it still feasible?
What is your best option?

2016-01-05 18:12 GMT+09:00 Chen notifications@github.com:

The car from taobao is only 10+kg, it is unable to carry more than 20kg...
And as it become heavier, it become slower....
we need a 4m/s UGV....

2016-01-05 18:07 GMT+09:00 趙 漠居 notifications@github.com:

uh, it seems like building from source is a boring task, but still not
difficult.
We can use husky+ur5 just for simuliation, like the
percepition/munipulation process.

But the best choice I believe is the car you showed in taobao + the staro
arm.
The only thing I am concern about the staro arm is that there is no
professional person in our team to deal with urata-board series product.

2016-01-05 17:58 GMT+09:00 Chen notifications@github.com:

And for the husky, the deb package is buggy and without gripper,
we need to build from the recent source code if we want to perform the
simulation.

Are we going to use husky?

2016-01-05 16:53 GMT+09:00 趙 漠居 notifications@github.com:

I add new arena model. which contains the texture material.
just have a try with: $ gazebo mbzirc_arena.world
I also confirm that new arena is ok for husky:
$ROBOT_INITIAL_POSE="-x 65 -y -25 -z 1" roslaunch jsk_mbzirc_ugv_sim
husky_mbzirc.launch
2.

I suppose that the mbzirc_arena.world for each task should be
specialized, such as mbzirc_arena_task1.world,
mbzirc_arena_task2.world,
mbzirc_arena_task3.world, mbzirc_arena_task4.world. Because the
environment
of each task is slightly different.
3.

I also suppose that the it is better to move the directory
"gazebo_model" into package "jsk_mbzirc_common" or change the
"gazebo_model" to ros package.

You can view, comment on, or merge this pull request online at:

#6
Commit Summary

  • add new arena model

File Changes

Patch Links:

—
Reply to this email directly or view it on GitHub
#6.

—
Reply to this email directly or view it on GitHub
#6 (comment).

—
Reply to this email directly or view it on GitHub
#6 (comment).

—
Reply to this email directly or view it on GitHub
#6 (comment).

@cretaceous-creature
Copy link
Collaborator

it depends how much we can get.....
how much is husky?
I know UR5 is about 3 million yen.....

Change the motor is not very hard, but then I need to
change the software then.....
I hope Japan have such kind of moving base...

2016-01-05 18:14 GMT+09:00 趙 漠居 notifications@github.com:

One solution you said is to change the motor_driver to urata-board?
Is it still feasible?
What is your best option?

2016-01-05 18:12 GMT+09:00 Chen notifications@github.com:

The car from taobao is only 10+kg, it is unable to carry more than
20kg...
And as it become heavier, it become slower....
we need a 4m/s UGV....

2016-01-05 18:07 GMT+09:00 趙 漠居 notifications@github.com:

uh, it seems like building from source is a boring task, but still not
difficult.
We can use husky+ur5 just for simuliation, like the
percepition/munipulation process.

But the best choice I believe is the car you showed in taobao + the
staro
arm.
The only thing I am concern about the staro arm is that there is no
professional person in our team to deal with urata-board series
product.

2016-01-05 17:58 GMT+09:00 Chen notifications@github.com:

And for the husky, the deb package is buggy and without gripper,
we need to build from the recent source code if we want to perform
the
simulation.

Are we going to use husky?

2016-01-05 16:53 GMT+09:00 趙 漠居 notifications@github.com:

I add new arena model. which contains the texture material.
just have a try with: $ gazebo mbzirc_arena.world
I also confirm that new arena is ok for husky:
$ROBOT_INITIAL_POSE="-x 65 -y -25 -z 1" roslaunch
jsk_mbzirc_ugv_sim
husky_mbzirc.launch
2.

I suppose that the mbzirc_arena.world for each task should be
specialized, such as mbzirc_arena_task1.world,
mbzirc_arena_task2.world,
mbzirc_arena_task3.world, mbzirc_arena_task4.world. Because the
environment
of each task is slightly different.
3.

I also suppose that the it is better to move the directory
"gazebo_model" into package "jsk_mbzirc_common" or change the
"gazebo_model" to ros package.

You can view, comment on, or merge this pull request online at:

#6
Commit Summary

  • add new arena model

File Changes

Patch Links:

—
Reply to this email directly or view it on GitHub
#6.

—
Reply to this email directly or view it on GitHub
#6 (comment).

—
Reply to this email directly or view it on GitHub
#6 (comment).

—
Reply to this email directly or view it on GitHub
#6 (comment).

—
Reply to this email directly or view it on GitHub
#6 (comment).

cretaceous-creature added a commit that referenced this pull request Jan 6, 2016
@cretaceous-creature
Merge pull request #6 from RCTemp/indigo-devel
975a883 
add new arena model
@cretaceous-creature cretaceous-creature merged commit 975a883 into start-jsk:indigo-devel Jan 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@tongtybj @cretaceous-creature