Solve_for points_function Using heterogeneous_inflow_config functions in FLORIS

[fbelli997]

Hi everyone,

I was triyng to use the solve_for_points function setting the fmodel with heterogeneous_inflow_confige active in the model. unfortunatelly I received this message:

" File "C:\Users\fbell\AppData\Local\Programs\Python\Python311\Lib\site-packages\floris\floris_model.py", line 1383, in sample_flow_at_points
return self.core.solve_for_points(x, y, z)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\fbell\AppData\Local\Programs\Python\Python311\Lib\site-packages\floris\core\core.py", line 251, in solve_for_points
self.flow_field.initialize_velocity_field(field_grid)
File "C:\Users\fbell\AppData\Local\Programs\Python\Python311\Lib\site-packages\floris\core\flow_field.py", line 178, in initialize_velocity_field
grid.x_sorted_inertial_frame.flatten(),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'PointsGrid' object has no attribute 'x_sorted_inertial_frame'. Did you mean: 'y_sorted_inertial_frame'?"

does this means that i can use this function implementing particular heterogeneous inflow conditions?

Thank you in andvance for your help.

regards
Federico

[misi9170]

Hi Federico,

Thank you for bringing this up! Could you share a short script showing what you're running to generate this error?

Misha

[fbelli997]

Hi @misi9170:

here below I send you what I initialized in my fmodel:

heterogeneous_inflow_config = {
    "speed_multipliers": speed_multipliers,
    "x": x_locs,
    "y": y_locs,
    "z": z_locs,
}
fmodel.set(
        layout_x=np.array([0.0, 1*5.0*WTM12A_D, 2*5.0*WTM12A_D]),
        layout_y=np.array([0.0, 0.0, 0.0]),
        turbine_library_path=os.path.dirname(os.path.dirname(__file__)) + "\\turbine_files",
        air_density = air_density,
        heterogeneous_inflow_config=heterogeneous_inflow_config,
        reference_wind_height=0.86,
        wind_directions=np.array([270.0]),
        wind_speeds=np.array([wind_speed]),
        turbulence_intensities=np.array([turbulence_intesity]),
        wind_shear=0.0,
    )

yM_5D, yM_10D = mat_data_5D['yM'].flatten(), mat_data_10D['yM'].flatten()  # y coordinates
zM_5D, zM_10D = mat_data_5D['zM'].flatten(), mat_data_10D['zM'].flatten()  # z coordinates
uM_5D, uM_10D = mat_data_5D['uM'], mat_data_10D['uM']  # average wind speed
xM_5D, xM_10D = 5*WTM12A_D*np.ones_like(yM_5D), 10*WTM12A_D*np.ones_like(yM_10D) # x coordinates

predicted_values_5D = np.array([fmodel.sample_flow_at_points(xM_5D, yM_5D, z*np.ones_like(yM_5D)) for z in zM_5D])
predicted_values_10D = np.array([fmodel.sample_flow_at_points(xM_10D, yM_10D, z*np.ones_like(yM_10D)) for z in zM_10D])
predicted_values_5D, predicted_values_10D = predicted_values_5D.reshape(uM_5D.shape), predicted_values_10D.reshape(uM_10D.shape)

predicted_values_5D = np.array([fmodel.sample_flow_at_points(xM_5D, yM_5D, z*np.ones_like(yM_5D)) for z in zM_5D])
predicted_values_10D = np.array([fmodel.sample_flow_at_points(xM_10D, yM_10D, z*np.ones_like(yM_10D)) for z in zM_10D])

This is the code I'm using which generated that error.

Let me know if you need something else.

Federico.

[misi9170]

Thanks Federico! That helps a lot. Based on your example and also examples/examples_heterogeneous_inflow/001_heterogeneous_inflow_single.py, I made the following minimal example:

from floris import FlorisModel


# Initialize FlorisModel
fmodel = FlorisModel("../inputs/gch.yaml")

# Change the layout to a 4 turbine layout in a box
fmodel.set(layout_x=[0, 0, 500.0, 500.0], layout_y=[0, 500.0, 0, 500.0])

# Set FLORIS to run for a single condition
fmodel.set(wind_speeds=[8.0], wind_directions=[270.0], turbulence_intensities=[0.06])

# Define the speed-ups of the heterogeneous inflow, and their locations.
# Note that heterogeneity is only applied within the bounds of the points defined in the
# heterogeneous_inflow_config dictionary.  In this case, set the inflow to be 1.25x the ambient
# wind speed for the upper turbines at y = 500m.
speed_ups = [[1.0, 1.25, 1.0, 1.25]]  # Note speed-ups has dimensions of n_findex X n_points
x_locs = [-500.0, -500.0, 1000.0, 1000.0]
y_locs = [-500.0, 1000.0, -500.0, 1000.0]

# Create the configuration dictionary to be used for the heterogeneous inflow.
heterogeneous_inflow_config = {
    "speed_multipliers": speed_ups,
    "x": x_locs,
    "y": y_locs,
}

# Set the heterogeneous inflow configuration (No error raised if this line is commented out)
fmodel.set(heterogeneous_inflow_config=heterogeneous_inflow_config)

# Run the FLORIS simulation
fmodel.run() # Works

fmodel.sample_flow_at_points([100], [100], [100]) # Does not work

This produces the error you reported:

AttributeError: 'floris.core.grid.PointsGrid' object has no attribute 'x_sorted_inertial_frame'. Did you mean: 'y_sorted_inertial_frame'?

I will look into why this is happening and hope to get back to you early next week.

[misi9170]

Hi @fbelli997 , I've started to implement a fix for this in #1110 . I haven't yet fully tested the new code, but you can likely start using the branch that I'm working on in the meantime if you'd like.

[fbelli997]

Hi @misi9170, thank you very much for the support, I will use it.
just an other question. I implemented the vertical deflection in all the models with the aim to have the dependency also of the turbulence intensity. I'm actually using the same parameters of the empirical gauss, do you think I should calibrate the parameters for the other wake models?

  horizontal_deflection_gain_D: 3.0
  vertical_deflection_gain_D: 3.0
  deflection_rate: 22

Thank you for your support.

[misi9170]

Hi @fbelli997 ,

I'm not totally sure I understand your question: are you asking whether, for the Gauss and Jimenez deflection models, you should use the same vertical deflection parameters as their default horizontal deflection parameters? Unless you have any other datapoints, I think that is a reasonable starting point. I think there are some reasons to believe that vertical deflections will be "smaller" than horizontal deflections (e.g. presence of the ground below and atmospheric boundary layer above), but since we don't have a good handle on what vertical deflections look like, I think using the same parameters as horizontal deflections is reasonable.

Misha