-
Notifications
You must be signed in to change notification settings - Fork 65
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
Invalid cells and stencils using Version 4.1 #47
Comments
From Version 4.0 to 4.1 the own math functions to calculate the reference space have changed. Before the function to calculate the eigenvalues of a matrix was not generally valid for all 3x3 matrices. This has been fixed in Version 4.1 and now mirrors more the behavior of the LAPACK library. Therefore maybe something small changed with the reference frame, which then changes the transformation matrices. When I run the test with OpenFOAM v2012 I have no invalid cells for the cavity tutorial. For the wedge case I get the same message of 100% invalid. This is however due to the wedge mesh and I have encountered this error also for previous versions. To circumvent this the checkCondition option can be set to false, then the condition of the central stencil is not checked. If the simulations still run stable it is also no problem to set this option. If you want you can also check if the result changes when you use the LAPACK library. Hope this helps understanding it better. |
Hello Jan, Thank you for reply and suggestion 😄 . Based on your recommendation, I am running some tests and glad to share my progress with you here. I tested OpenFOAM v2012/v2106 and WENOEXT 4.0(b6f4978)/4.1(f45593a) a. You are right. Using the LAPACK library, the cavity case run by both v2012 and v2106 with 4.0/4.1 show no invalid cells. It seems that this problem does relate to the math function. To further determine the cause and effect of invalid cells, I may need some of your help. The relevant files under WENOBase seem to be stored in binary format. I used some tools to convert them to ASCIl, but none of them work. Is there any way to make these files human-readable? In addition, I found that when the number of invalid cells exceeded a certain number, the log stopped printing the cell ID. Is there a way to output complete information about these cells so I can locate them, for example in ParaView? Best, Fracturist |
Hello Fracturist, the binary format should be able to be converted back into OpenFOAM ASCII lists. However, even in ASCII format the files are very difficult to read, especially the matrices, due to the List of Lists format OpenFOAM uses. But you can do the following:
|
Thank you very much, Jan. This information is very helpful 👍 Once I have any progress I will post here. |
Hello, Jan. I have also encountered this problem. |
Hi, Lin. If your case is the linear advection equation with sine wave as the initial value, I suggest you make a comparison between upwind scheme and a series of WENOUpwindFit schemes after some periods. If the results are basically the same at different time, this is a fast way to check whether WENOEXT performed well or not. |
Hello, have you switched off the condition check in the control settings as stated in the README? If it is switched on then you will have an Upwind Scheme.
|
Hello, I previously tried to turn |
Discussed in #46
Originally posted by Fracturist June 29, 2022
Hello,
I have recently noticed appearance of extra invalid cells and stencils in my own test case when using Version 4.1.
Then I checked the log file stored previously for same case using Version 4.0. It seems that everything is fine.
So I did a rerun for tutorial case using Version 4.1. Serial Cavity case is OK but parallel Cavity case showed an extra invalid cell. Moreover, all cells in Wedge case seem invalid. I am pretty sure that these case was fine with Version 4.0.
The log fie for tutorial cases is here
log.txt
Can someone give me a hint as to how these happened? Is it due to my compilation or some feature related to new version?
The text was updated successfully, but these errors were encountered: