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

Inflow velocity point not found in mesh #11

Open
ZhouYmi opened this issue Oct 14, 2024 · 7 comments
Open

Inflow velocity point not found in mesh #11

ZhouYmi opened this issue Oct 14, 2024 · 7 comments

Comments

@ZhouYmi
Copy link

ZhouYmi commented Oct 14, 2024

Dear Pere @fronterapp ,
Thank you for maintaining the code and patiently answering questions.
Based on your paper CFD Simulation of a Floating Wind Turbine with OpenFOAM, I encrypted the mesh near the rotor. Even if it meets the requirements, errors similar to the following still occur:
Inflow velocity point for turbine.blade2.element2 not found in mesh
This kind of problem can often be solved when I change the number of parallel computations. I want to know what caused this error and whether there are other solutions to avoid it from happening
Best,
Zhou

@fronterapp
Copy link
Owner

Dear Zhou,

There's an open issue about this error in #5 (comment). Hope it can help.

Best,
Pere

@ZhouYmi
Copy link
Author

ZhouYmi commented Oct 19, 2024

Dear Zhou,

There's an open issue about this error in #5 (comment). Hope it can help.

Best, Pere

Dear Pere @fronterapp ,
Thank you very much for answering my question. This is of great help to me : ) !! by changing the number of parallelizations can effectively solve this problem. In order to simulate another floating wind turbine, I made modifications to the coupled case in Chapter_7 provided by you. I replacing the blades and platform model, and changing it to uniform wind, shortening the overall length: in_len=200, out_len=400, sim_len=400 (because I do not want to analyze the change about the wake field). But I encountered a floating point exception during the running process. Here is my entire log file. I would like to ask what is usually related to the occurrence of such problems? How should I modify it?
Best, Zhou
log.txt

@fronterapp
Copy link
Owner

Dear Zhou,

Looking at the log file (line 57649), it seems like there's an issue when calculating the end effects. You can take a look at #9 (comment). Hope that helps!

Regards,
Pere

@ZhouYmi
Copy link
Author

ZhouYmi commented Oct 22, 2024

Dear Zhou,

Looking at the log file (line 57649), it seems like there's an issue when calculating the end effects. You can take a look at #9 (comment). Hope that helps!

Regards, Pere

Dear Pere,
It is very helpful!!!! Thank you very much! :)
Regards,
Zhou

@ZhouYmi
Copy link
Author

ZhouYmi commented Oct 23, 2024

Dear Pere@fronterapp ,
I have some questions about some settings you made in the dynamicMeshDict file. I would like to know if the refAttachmentPt in CatenaryLine should be a point on the surface of a floating platform object? Or does it need to be located inside the floating platform? Also, I noticed that you omitted the code for turbineWeight in restraints. I would like to know what impact this has on the overall movement of the floating platform and why it is not necessary?
Regards,
Zhou
1729662623788

@fronterapp
Copy link
Owner

Dear Zhou,

The refAttachmentPt is, at the same time, the starting point of the mooring line (which will connect to the anchor) and the point where the restraint loads are applied to the rigid body. It does not need to be on the floater's surface. For example, it can be set some distance outwards depending on the fairlead geometry.

The turbine weight is explained on page 88 of the thesis, in "Morphing mesh and rigid-body". Since the floater and turbine are rigidly connected, you can assign the coupled system a total mass and center of gravity (see the myVars script). The rotational inertia of the turbine was omitted, though you can include it easily through the parallel axes theorem.

Best,
Pere

@byChen47
Copy link

Dear Zhou,
There's an open issue about this error in #5 (comment). Hope it can help.
Best, Pere

Dear Pere @fronterapp , Thank you very much for answering my question. This is of great help to me : ) !! by changing the number of parallelizations can effectively solve this problem. In order to simulate another floating wind turbine, I made modifications to the coupled case in Chapter_7 provided by you. I replacing the blades and platform model, and changing it to uniform wind, shortening the overall length: in_len=200, out_len=400, sim_len=400 (because I do not want to analyze the change about the wake field). But I encountered a floating point exception during the running process. Here is my entire log file. I would like to ask what is usually related to the occurrence of such problems? How should I modify it? Best, Zhou log.txt

Dear @ZhouYmi ,
I want to ask you used how number of parallelization to solver the question: Inflow velocity point not found in mesh,and How much cells in you case
Best
chen

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