[tyamazaki]

Hi, everyone.

Yesterday, I started the calculation about the wind turbine blade using SU2( ver7.3.1 blackbird ).
I want to know how to output the aero force distribution on the rotor blade.
I plan to use the force distribution for our in-house FEM structure calculation codes.

I am looking into the information, but I can not find it. ( I only found how to output the sum of aerodynamic force and moment on a solid surface... )

If anyone knows about the aerodynamic force distribution output,
would you mind telling me any information?

I really appreciate any help you can provide.

Tomoki

[pcg]

Hi,

This is an example that extracts forces for all points on a surface:
https://github.com/su2code/SU2/tree/...ating_NACA0012

[tyamazaki]

Originally Posted by pcg

Hi,

This is an example that extracts forces for all points on a surface:
https://github.com/su2code/SU2/tree/...ating_NACA0012

I appreciate your kindness.
Reading your sources, I understand how to get the distribution of aerodynamic forces.

By the way, I copied your sources to my local environment to confirm the execution behavior and rebuilt SU2 with python wrappers and mpi options to run it.
I succeeded in building SU2 with only python wrappers but failed building
SU2 with python wrappers and mpi options.
My local environment is set to python3.7.9 on virtualenv( installed mpi4py) and swig3.0.12 in CentOS7.

If you have any ideas, would you mind telling me to solve this situation?
This additional question is out of scope for the first question, so should I ask the same question in SU2 git issues...?

The output errors in meson-log.txt are bellow:

Message: Boost sources found.
Program swig found: YES (/usr/bin/swig)
Running command: /***/***/***/work/SU2/venv/bin/python3 -c import mpi4py; print(mpi4py.get_include())
--- stdout ---
/***/***/***/work/SU2/venv/lib/python3.7/site-packages/mpi4py/include

--- stderr ---


Message: Using mpi4py from /***/***/***/work/SU2/venv/lib/python3.7/site-packages/mpi4py/include
Pkg-config binary for 1 is cached.
Determining dependency 'python-3.7m' with pkg-config executable '/usr/bin/pkg-config'
env[PKG_CONFIG_LIBDIR]: /***/***/***/soft/Python-3.7.9/build/lib/pkgconfig
env[PKG_CONFIG_PATH]: /opt/intel/compilers_and_libraries_2019.1.144/linux/mkl/bin/pkgconfig
Called `/usr/bin/pkg-config --modversion python-3.7m` -> 0
3.7
env[PKG_CONFIG_LIBDIR]: /***/***/***/soft/Python-3.7.9/build/lib/pkgconfig
env[PKG_CONFIG_PATH]: /opt/intel/compilers_and_libraries_2019.1.144/linux/mkl/bin/pkgconfig
Called `/usr/bin/pkg-config --cflags python-3.7m` -> 0
-I/data/home/yamazaki/soft/Python-3.7.9/build/include/python3.7m
env[PKG_CONFIG_LIBDIR]: /***/***/***/soft/Python-3.7.9/build/lib/pkgconfig
env[PKG_CONFIG_ALLOW_SYSTEM_LIBS]: 1
env[PKG_CONFIG_PATH]: /opt/intel/compilers_and_libraries_2019.1.144/linux/mkl/bin/pkgconfig
Called `/usr/bin/pkg-config --libs python-3.7m` -> 0
-L/***/***/***/soft/Python-3.7.9/build/lib -lpython3.7m
env[PKG_CONFIG_LIBDIR]: /***/***/***/soft/Python-3.7.9/build/lib/pkgconfig
env[PKG_CONFIG_PATH]: /opt/intel/compilers_and_libraries_2019.1.144/linux/mkl/bin/pkgconfig
Called `/usr/bin/pkg-config --libs python-3.7m` -> 0
-L/***/***/***/soft/Python-3.7.9/build/lib -lpython3.7m
WARNING: extract_all_objects called without setting recursive
keyword argument. Meson currently defaults to
non-recursive to maintain backward compatibility but
the default will be changed in the future.


SU2_PY/pySU2/meson.build:27:2: ERROR: Tried to form an absolute path to a source dir.
You should not do that but use relative paths instead.

To get include path to any directory relative to the current dir do

incdir = include_directories(dirname)

After this incdir will contain both the current source dir as well as the
corresponding build dir. It can then be used in any subdirectory and
Meson will take care of all the busywork to make paths work.

Dirname can even be '.' to mark the current directory. Though you should
remember that the current source and build directories are always
put in the include directories by default so you only need to do
include_directories('.') if you intend to use the result in a
different subdirectory.

[pcg]

You can open a discussion on GitHub, maybe someone with a similar setup will know what to do.

[tyamazaki]

I got it. I appreciate your kind response!!!