Is the WISDEM n_refine parameter settable for the monopile?

Wind & Water Computer-Aided Engineering Software Tools
1

Hello everybody.
I would like to set the n_refine parameter to a non-default value for both tower and monopile, but the setting for the monopile
rises an error and makes the optimization abort. The setting for the tower, instead, causes no problem.
In fact, when I go thorough the code in monopile.py I can see that there is a hardcoded value NREFINE that is used instead of n_refine:

./fixed_bottomse/monopile.py:11:NREFINE = 3
…
./fixed_bottomse/monopile.py-790- self.add_subsystem(
./fixed_bottomse/monopile.py-791- “member”,
./fixed_bottomse/monopile.py:792: mem.MemberStandard(column_options=temp_opt, idx=0, n_mat=n_mat, n_refine=NREFINE),
./fixed_bottomse/monopile.py-793- promotes=promlist,
./fixed_bottomse/monopile.py-794- )

Is it thus forbidden, for some reasons, to set n_refine for the monopile in the modeling_options.yaml input file?
Can I directly set NREFINE to a value !=3 in the monopile.py file?
Thank you for your time and attention

2

Yes, that seems like a bug. There is an n_refine allowed in the modeling options for the monopile but it is not used in the monopile code. Another item for the to-do list.

3

Thank you Garret for your fast reply.
Just for information, I modified the value of NREFINE directly in monopile.py and tried an optimization run, but it soon aborted showing the following error for many variables:

The source and target shapes do not match or are ambiguous for the connection...
4

Thanks for the heads up, I’ll have to sort that out too.

5

This is being address in this PR.