-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add env variables in .world files #75
Comments
After being tired of always needing to change the code to my folder structure in the .world, I searched about this and didn't really find how to use env variables in .world files but I was reading how the world folder structure should be organized and found this link: https://gazebosim.org/api/gazebo/5.1/migrationsdf.html. After some reading I manage to make it work without having to specify my specific folder structure in the code.
To this:
And in the .world file I changed from this:
To this:
One thing I noticed is that we don't have the same folder structure as they talk about in the link is that for any reason in particular? In that website they also talk about Ignition Gazebo that from what I can read we could put the world in the cloud and then just use the link in the code, instead of having it in our computer, if I'm not mistaken. |
Hi @andrefdre, if it works, commit.
Usually, we remove from the git folder all files that are too large to be pushed to github. But if you have a better way, feel free to change.
From what I read, Ignition Gazebo is the newer version of Gazebo, so I don't think we should even think about switching... |
Yes, better use the point cloud locally stored for now. |
I didn't know it was the newer version I just read about it and sounded it could be interesting.
Okay, that's what I thought, but then why have the .world files in the GitHub folder? Why not have it together with the rest of the world files? Then you just have to add to the the bashrc file where it is and would remove the need to have the global directory in the .world and just have the relative path and the global one would be in the bashrc. Kind of what it suggested in the gazebo reference. |
…s with the collection part where I tried to also use the same variable, so if for example I want to save the dataset and the models in an external drive I just need to change the line in the bashrc. I didn't place it in the main branch to get other opinion. #75
One thing I noticed was that using Gazebo environment variable to everything presents a problem if you have another paths, since we are selecting manually which one we want in the array.
But this doesn't have the issue in the .world files, since it searches in every path. |
Since .world files are in XML format, it is not straightforward to use env variables. I'll leave this for later since it is not critical for now.
The text was updated successfully, but these errors were encountered: