You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 6, 2023. It is now read-only.
Hi,
I have been running into a weird issue with the plumes where after a couple minutes, a large portion of the plume is suddenly vertically displaced upwards. Sometimes this displacement happens multiple times in short succession, other times it happens once. And it happens on every run.
The particles are continuously generated at the source with the correct current velocity (which I am setting via the set_current_velocity service call).
The text was updated successfully, but these errors were encountered:
I managed to make this issue not happen (I hesitate to say fixed). What I suspect is that the 'current_velocity_server' instance that I created in addition to launching the gazebo world 'ocean_waves.launch' created conflicting current velocities with that produced by the gazebo current velocity controller. I took another look at the existing launch files in plume simulator and realized that the current_velocity_server was only being created if use_gazebo was false.
Long story short I think the issue was coming from my unnecessary use of the current_velocity_server.
In case you're still interested, here is the service call that I used for setting current velocity when I still had issues: rosservice call /current_velocity_server/set_current_velocity "{velocity: 1.0, horizontal_angle: 0.0}"
Thanks for the reply, the simulator's been great!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
I have been running into a weird issue with the plumes where after a couple minutes, a large portion of the plume is suddenly vertically displaced upwards. Sometimes this displacement happens multiple times in short succession, other times it happens once. And it happens on every run.
The particles are continuously generated at the source with the correct current velocity (which I am setting via the set_current_velocity service call).
The text was updated successfully, but these errors were encountered: