LGSVL Simulator has been a powerful simulator that made many research projects possible. Unfortunately, LG has made the difficult decision to suspend active development of SVL Simulator, as of January 1, 2022. The official statement says the cloud will be up and running through at least Thursday, June 30, 2022.
The current version of SVL Simulator cannot be used without a cloud which provides necessary information (e.g. assetGuid) and download endpoints for SVL client. As an effort to keep the tool available for future researches, a draft for a local cloud has been started here.
If you want to contribute to the project, please consider joining our Slack workspace.
- Viewing maps, vehicles, plugins (previews)
- Allow SVL Client to connect to a local cloud
- Start an API Only Simulation
-
Install Docker
-
Clone the project
-
Download assets needed from Google Drive and unzip them in
server/assets
. (preview, maps, plugins, vehicles, hdmaps)Since the compressed file for entire maps directory is too large, you will have to manually download map asset individually from the Google Drive folder. Also, when downloading individual asset file, make sure there is no file extension. Google sometimes automatically adds ".zip" to the end, make sure to remove this from the filename. See YuqiHuai#33 (comment)
UPDATE 2022-06-30: WISE provides geojson for some of the maps. To access those geojson, download
geojson.json
from Google Drive, and then import them into MongoDB. -
Run
docker compose up --build -d
-
Local SVL Cloud will be available at "http://localhost"
-
Add
config.yml
to the root directory of SVL client with the following content:headless: false read_only: false api_hostname: "localhost" api_port: 8181 cloud_url: "http://localhost"
Note the cloud url starts with
http
(nothttps
).See documentation from SVL archive.
-
Now, SVL Client can be used without WISE.
- Gradually incorporate original LGSVL documentation
- Allow uploading sensor configuration
- Allow creating new simulation templates
- Allow creating new vehicle sensor configurations
- Add cluster feature to the cloud
- Allow website to reflect client connection status.
- Host assets at a different location
- It is possible that permission settings related to Docker can cause project to fail (unable to load preview, unable to download assets). See YuqiHuai#11 (comment)
- I recommend installing docker following instructions in https://docs.docker.com/engine/install/ubuntu/
Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/AmazingFeature
) - Commit your Changes (
git commit -m 'Add some AmazingFeature'
) - Push to the Branch (
git push origin feature/AmazingFeature
) - Open a Pull Request