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
For the purposes of the competition we need to be able to specify the wave conditions (seastate) in the environment - specifically we need to be able to give a range of seastate values to specify the range of operating conditions that the tasks solutions will be tested against.
where the properties of the individual wave components are determined as described here.
After we integrate the physics/visual synchronization (see issue #23 (#23)) we need to determine a reasonable way to describe the range of seastates that will be use for task evaluation.
The text was updated successfully, but these errors were encountered:
Original report (archived issue) by Brian Bingham (Bitbucket: brian_bingham).
For the purposes of the competition we need to be able to specify the wave conditions (seastate) in the environment - specifically we need to be able to give a range of seastate values to specify the range of operating conditions that the tasks solutions will be tested against.
In the current default branch the wave field is specified as a summation of N regular waves where the amplitude, period and direction of each wave component are specified directly - see https://github.com/osrf/vrx/blob/master/wamv_gazebo/urdf/dynamics/wamv_gazebo_dynamics_plugin.xacro
In the proposed synchronized physics visualization (see PR #78 ) the wave field is specified like so…
where the properties of the individual wave components are determined as described here.
After we integrate the physics/visual synchronization (see issue #23 (#23)) we need to determine a reasonable way to describe the range of seastates that will be use for task evaluation.
The text was updated successfully, but these errors were encountered: