Apollo: I can not start module monitor in apollo 2.0. Help~

[jinpingfan]

By the end of the 1.5 version, it can all run perfectly......
I update the update in order 1.5.1；1.5.2..........2.0.0 but I can not start DEMO module monitor in apollo 2.0
（I don't understand why the kernel version still stays in 1.5.......

）
and I can not download 2.0 Demo bag on line......

Please help me.......I don't know where the problem is.

[startcode]

Can you try to download the 2.0 bag by this command?

wget https://github.com/ApolloAuto/apollo/releases/download/v2.0.0/demo_2.0.bag

[jinpingfan]

yap......But what is more important is command “bash scripts/bootstrap.sh”
Cannot be executed

[startcode]

The bootstrap.sh is in the latest repo. Somehow it is not in your local file system.

https://github.com/ApolloAuto/apollo/blob/master/scripts/bootstrap.sh

My guess is that you are still using apollo 1.5 code.
Can you double check the git branch and git log output?

[jinpingfan]

Thank you, sir. You're right, I'm still running the 1.5 version of the program, but I've updated the Platform to 2.0.0 according to the instructions.......

[startcode]

@jinpingfan can you let me know which instruction has confused you? I think we should correct them. Thanks

[jinpingfan]

[jinpingfan]

@startcode startcodeOn the basis of 1.5：
Download：ros-indigo-apollo-2.0.0-x86_64.tar.gz：
https://github.com/ApolloAuto/apollo-platform/releases

tar zxvf ros-indigo-apollo-2.0.0-x86_64.tar.gz
rsync -av ros/ ~/apollo/third_party/ros_x86_64
source ~/apollo/third_party/ros_x86_64/setup.bash

2.bash docker/scripts/dev_start.sh

3.bash docker/scripts/dev_into.sh

4.bash apollo.sh build

5.bash scripts/bootstrap.sh

[richtong]

Is the build step now required for Apollo 2.0?

[lianglia-apollo]

Yes, it is required to run bash apollo.sh build before calling bootstrap.sh

[richtong]

You might want to update the Readme which is unclear. I can fix this and issue a PR if you like. Also have outstanding work to allow logo and skinning changes to dreamview which we need for integration into our systems. Thanks for the great work!

Thanks,
Rich

Sent from my iPhone X
http://tongfamily.com | @richtong | https://fb.me/richtong1

On Jan 16, 2018, at 11:23, Liangliang Zhang [e-mail] wrote:

Yes, it is required to run bash apollo.sh build before calling bootstrap.sh

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[richtong]

I think part of the problem is the README.md is a little unclear for new people like me. We have fixed the instructions in our fork, would the main project be interested in a PR on this, might help as I see lots of folks struggling with how to make this work. See https://github.com/XevoInc/apollo/tree/rich-readme-2.0

[xiaoxq]

That is great!

Please send the PR. Thanks!

On Tue, Jan 16, 2018 at 1:08 PM, Rich Tong [e-mail] wrote:

I think part of the problem is the README.md is a little unclear for new
people like me. We have fixed the instructions in our fork, would the main
project be interested in a PR on this, might help as I see lots of folks
struggling with how to make this work.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ApolloAuto/apollo/issues/2471#issuecomment-358106018,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF6AkgDZ1gG-T3PGpz-7qpkID80PYkkZks5tLQ-7gaJpZM4RfWB2
.

[richtong]

Just sent

[jinpingfan]

@richtong @xiaoxq Thank you for your stronly support~ Looking forward to a detailed description of the document for the update~ THX~

[richtong]

Thank you very much for working on such a terrific product.

Thanks,
Rich

Sent from my iPhone X
http://tongfamily.com | @richtong | https://fb.me/richtong1

On Jan 16, 2018, at 21:20, jinpingfan [e-mail] wrote:

@richtong @xiaoxq Thank you for your stronly support~ Looking forward to a detailed description of the document for the update~ THX~

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

[Zhenni17]

Bug resolved and PR was accepted. Closed the issue.