Help changing map file in f1tenth simulator

[Malik Ali]

I am trying to change the map from levine to levine_obs to test my gap following algorithm for lab 4. I have placed the levine_obs.yaml and levine_obs.png files in the f1tenth_gym_ros/maps folder and modified the sim.yaml:

# map parameters
    map_path: '/sim_ws/src/f1tenth_gym_ros/maps/levine_obs'
    map_img_ext: '.png'

Unfortunately, after building and relaunching, I am still arriving at the same levine map. I found the build file in log and it showed that it was successfully copying the sim.yaml file and when looking at what was in the sim.yaml file using cat, it shows the correct filepath. Additionally, I can modify the origin for the levine.yaml file and it will work as intended. Does this have something to do with docker? Any help would be greatly appreciated. Thanks,

Malik.

[Rahul Mangharam]

Malik,

I encourage you to ask these questions on the f1tenth-teams slack. It is a responsive and helpful community

https://join.slack.com/t/f1tenth-teams/shared_invite/zt-2bs9qs2bb-oIQioGYrmd5s~IuGRFsufw

Prof. Rahul Mangharam
Dept. of Electrical and Systems Engineering
School of Engineering and Applied Science
University of Pennsylvania

https://www.seas.upenn.edu/~rahulm

https://f1tenth.org | http://av4ev.org | https://medcps.org | https://autoware.org

--
You received this message because you are subscribed to the Google Groups "F1_10" group.
To unsubscribe from this group and stop receiving emails from it, send an email to f1_10+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/f1_10/8354437c-2e72-496e-85b6-d49e5e212015n%40googlegroups.com.

[Shivam Jindal]

I am encountering a similar issue, is someone able to share the slack join link again as it has expired? Thank you!

[Malik Ali]

Shivam,

Go to f1tenth.org and click on forum in the top right and it will redirect you to the slack channel.

As for your question, when you change the map name in the sim.yaml file, make sure to bring down the docker image with 'sudo docker-compose down' , then colcon build your workspace, and when you bring it back up run 'sudo docker-compose up -- build'

Hopefully this helps,

Malik.