-
Notifications
You must be signed in to change notification settings - Fork 772
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
how to run simulator along with apollo #15
Comments
@ImCabbage we are in process of open-sourcing the instructions, stay tuned.
|
Hi, What time are you guys planning release the Apollo's instructions? Thanks! |
should be done by the end of next week |
@ImCabbage @yangydavid see Apollo instructions here: https://github.com/lgsvl/apollo |
@andytolst |
@ImCabbage can you attach a screenshot of incorrect position ? do you see the map of SF in the dreamview ? make sure localization is in RTK mode:
make sure you have localization module running in Apollo.
|
@andytolst I follow the tutorial in your official Youtube channel along with the README file in the forked Apollo repo. According to my experience with the Apollo platform, I think I do it right and successfully get the topic "/apollo/sensor/gnss/best_pose", just like what you post above (RTK mode in localization for sure). But the map seems not loaded when I start the localization module (sim_control closed). What I saw is all black background. I got two feedback from the Dreamview panel.
I am not sure whether the second info will affect. As I know, the default_end_way_point.txt file is generated through the lane.csv. But it seems that this file is indeed missing. When I open the sim_control option, I am able to see the map in the dreamview. I have a screenshot of what I met when this option is on, sadly, uploading pictures in issues is unavailable. If you could give a mail address or something, I think I can email you the pics. But still, the car is not in the right position. In dreamview, the vehicle always starts at the bottom right corner wherever it is in the simulator. I think it's the default start point for the map in Apollo. BTW, sometimes I got error info when I start the rosbridge launch file, recorded as below: the rosdep view is empty: call 'sudo rosdep init' and 'rosdep update' |
@ImCabbage, the two feedback messages you are seeing in dreamview are ok. The GPS message will appear because Apollo is not able to communicate with the GPS driver (which is not used with the simulator). The default POI is related to routing but should not affect localization. The sim_control mode should not be used with the simulator. That mode allows apollo to simulate driving at a high level on the HD map without any sensor data. Since it seems like you are having issues with rosbridge, I suspect that the GPS messages are not going through which would cause localization issues. To confirm, please try echoing the GNSS topic inside docker: This should print the GNSS messages on the screen. I suspect that this will not happen. Did you have any errors when building ros_pkgs? To rebuild, first delete the |
@ImCabbage please make sure you are using the latest code of the simulator (we changed GPS origin a week ago and it has to be in sync with Apollo) |
@andytolst Hi, thanks so much for the released instruction, it is very helpful and i am able to run the simulator with Apollo now. However, when I try to start the dreamview with |
@andytolst Thanks! I solve the issue following the suggestions there. |
@andytolst one more question I have is that the simulator runs very slow, and I use |
@yangydavid it depends on your HW config, good CPU and graphics card usually help
|
@andytolst |
@andytolst @hadiTab |
I'm closing this issue since it seems to be resolved for everyone. Feel free to reopen it if needed. |
* when rebuilding CubeTown many times in the same workspace I always get segfault like: 19:06:26 Launched and connected shader compiler UnityShaderCompiler after 0.03 seconds 19:06:44 Caught fatal signal - signo:11 code:1 errno:0 addr:0xd0000000e 19:06:44 Obtained 25 stack frames. 19:06:44 #0 0x007f72a328a3c0 in funlockfile 19:06:44 #1 0x007f72a3141c5b in memcpy 19:06:44 #2 0x007f71edcabf64 in vk_optimusGetDeviceProcAddr 19:06:44 #3 0x0056107c6dad75 in vk::TaskExecutor::HandleCommandStream(GrowableBuffer*, VkCommandBuffer_T*) 19:06:44 #4 0x0056107c6d9fe6 in vk::TaskExecutor::ExecuteCommandbuffers(vk::CommandBuffer**, int) 19:06:44 #5 0x0056107c6d6c33 in vk::TaskExecutor::DoFlush(VkFence_T*, VkSemaphore_T*, unsigned long) 19:06:44 #6 0x0056107c6a3e07 in GfxDeviceVK::SubmitCurrentCommandBuffers(VkSemaphore_T*) 19:06:44 #7 0x0056107c6a5721 in GfxDeviceVK::FinishRendering() 19:06:44 #8 0x0056107c61f4dd in GfxDeviceClient::FinishRendering() 19:06:44 #9 0x0056107bf9b506 in AssetHotreload() 19:06:44 #10 0x0056107f0fb8ff in AssetHotreload(core::hash_set<UnityGUID, core::hash<UnityGUID>, std::equal_to<UnityGUID> > const&) 19:06:44 #11 0x0056107f1964e7 in RefreshInternalV2(AssetDatabase::UpdateAssetOptions, ScanFilter const&, InternalRefreshFlagsV2) 19:06:44 #12 0x0056107f180712 in StopAssetImportingV2(AssetDatabase::UpdateAssetOptions, InternalRefreshFlagsV2, ScanFilter const*) 19:06:44 #13 0x0056107f180cb1 in RefreshV2(AssetDatabase::UpdateAssetOptions) 19:06:44 #14 0x0056107f0e5181 in AssetDatabase::Refresh(AssetDatabase::UpdateAssetOptions) 19:06:44 #15 0x0056107e4fdeb3 in Application::InitializeProject() 19:06:44 #16 0x0056107f03e606 in InitializeUnity(void*) 19:06:44 #17 0x007f72a39c3be8 in g_source_get_time 19:06:44 #18 0x007f72a39c304e in g_main_context_dispatch 19:06:44 #19 0x007f72a39c3400 in g_main_context_dispatch 19:06:44 #20 0x007f72a39c36f3 in g_main_loop_run 19:06:44 #21 0x007f72a405837d in gtk_main 19:06:44 #22 0x0056107f03dfce in main 19:06:44 #23 0x007f72a30aa0b3 in __libc_start_main 19:06:44 #24 0x0056107bd72029 in _start 19:06:44 /usr/bin/unity-editor: line 11: 11 Segmentation fault (core dumped) /opt/unity/Editor/Unity "$@" when building in workspace with empty "Library" directory and re-running it in the same workspace 2nd time (keeping "Library") finishes OK Rerun each bundle build upto 3 times before giving up and showing an error. Show summary at the end to easily find if some bundles still need to be re-triggered or fixed. * re-try the initial "fetch license" as well as it was sometimes failing there already (before starting any bundle build) * we do something similar in build-simulator.sh already, for "check" function
I am a developer working with Apollo recently. I would like to know is there any tutorial on how to run the Apollo and this simulator together.
I think it would be better if there is a tutorial on that.
Thanks for your work. This project is interesting. :)
The text was updated successfully, but these errors were encountered: