Skip to content

[Theory or Implementation] How to create h5 file with mean drift forces? #1020

@Dadidal

Description

@Dadidal

Is your question request related to a problem? Please describe.
I do not understand how to create a hydrodynamic data file (*.h5) with mean drift forces.

Describe the theory or implementation approach that you have a question
Firstly I calculated BEM data in ANSYS Aqwa. This BEM data includes mean drift forces. I know that according to documentation, WEC-Sim can read the mean drift forces only from WAMIT. Therefore I used BEMRosetta to change the BEM output format: I imported results from AQWA and then exported them to WAMIT format. Then I used BEMIO to read "WAMIT" *.out file and tried to simulate my model with "body(1).meanDrift = 1" option but obtained an error:

Error using h5readc
The HDF5 library encountered an error and produced the following stack trace information:

    H5G__traverse_real    component not found

Error in h5read (line 93)
[data,var_class] = h5readc(Filename,Dataset,start,count,stride);

Error in readBEMIOH5 (line 98)
    hydroData.hydro_coeffs.mean_drift =  reverseDimensionOrder(h5read(filename, [h5BodyName '/hydro_coeffs/mean_drift/control_surface/val']));

It seemed that my h5 file does not contain mean drift forces even though they exist in BEM data. I checked h5 file and observed that all matrixes of mean drift forces have 0 values.
Could you give some advice on how to fix it?
I have attached the following files (BEM data.zip):

  1. BEM output from ANSYS Aqwa
  2. Converted BEM data to WAMIT format
  3. Generated .h5 file

Personal project context
I am trying to include 2nd order wave forces in my simulation

Describe the type of conclusion or resolution you are looking for
I want to clarify and understand what I should do in order to include mean drift forces in WEC-Sim simulation

Additional context
image
BEM data.zip

Metadata

Metadata

Assignees

Labels

BEM/BEMIOrelated to BEMIO or BEM hydro dataNEMOH

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions