Skip to content
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

How to change wave parameters? #507

Closed
bsb808 opened this issue Sep 1, 2022 · 3 comments
Closed

How to change wave parameters? #507

bsb808 opened this issue Sep 1, 2022 · 3 comments

Comments

@bsb808
Copy link
Collaborator

bsb808 commented Sep 1, 2022

Scenario

Working on PR#500 and would like to test under wave conditions other then the default.

Consider the simple Sydney Regatta example: https://github.com/osrf/vrx/wiki/2023-running_vrx#the-sydney-regatta-environment

  • How would one change the wave parameters for a higher seastate?

What I tried

In the past we would change the period and gain parameters in the ocean_waves macro to change seastate - see https://github.com/osrf/vrx/wiki/changing_plugin_params_tutorial

Grepping for those SDF parameters I find that the gain parameter is set in many different places.

./vrx_ign/worlds/sydney_regatta.sdf:            <gain>0.3</gain>
./vrx_ign/worlds/sydney_regatta.sdf:            <gain>0.3</gain>
./vrx_ign/worlds/sydney_regatta.sdf:            <gain>0.3</gain>
./vrx_ign/worlds/sydney_regatta.sdf:            <gain>0.3</gain>
./vrx_ign/worlds/sydney_regatta.sdf:            <gain>0.3</gain>
./vrx_ign/worlds/sydney_regatta.sdf:            <gain>0.3</gain>
./vrx_ign/models/wam-v/model.sdf.erb:        <gain>0.3</gain>
./vrx_ign/models/wam-v_2/model.sdf.erb:        <gain>0.3</gain>
./vrx_ign/models/wam-v_2/model.sdf.erb:        <gain>0.3</gain>
./vrx_ign/models/coast_waves/model.sdf:              <gain>0.3</gain>

I changed all of the gain and period SDF tags to 1.0 and 10.0 respectively. No change in the visual behavior of the wave field or the vessel motion.

@caguero
Copy link
Contributor

caguero commented Sep 8, 2022

What you did is the right way to do it right now. You need to change it in all of those places. This will change when we register the parameters from a single place into a component. Then, all the other plugins will be able to read it using the component and the ECM.

@bsb808
Copy link
Collaborator Author

bsb808 commented Sep 8, 2022

Roger - I'll leave the issue open for now so that we have a reminder to address when the time is right.
Thank you.

@M1chaelM
Copy link
Collaborator

M1chaelM commented Aug 2, 2023

This is now resolved. Here's a summary of what we did to fix it:

@M1chaelM M1chaelM closed this as completed Aug 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants