Hi,
Well is a way way way much slower, probably 5 times. In any case, all my previous cases are not working fine. At the moment I am playing with the length scales to see if I find the right values. Regards, Joel |
Dear Sandeep:
I have run different cases on 4 processors. I have the same problem. First: dynamicTopoFvMesh run well but after various time steps > 200, I have this error Code:
~~~ Mesh Quality Statistics ~~~ Regards Olivier |
Dear Sandeep
I tested your latest version (01/15) in debug mode: fatal error: cells already calculated. When I run on one processor I have not this error. Code:
[0] Mapping Faces: 267 Olivier |
Olivier,
I've posted a fix for the floating-point exception issue. I'm not sure what's going on with the cellCells error - does it occur only in Debug? [EDIT:] Also - are you running this multi-threaded (i.e., threads > 1)? Thanks |
Sandeep,
I tested your latest version. The error is still there. does it occur only in Debug? ==> no are you running this multi-threaded (i.e., threads > 1)? ==> yes Regards |
Okay.. I'll look into the multi-threaded issue. Can you try with single-threaded for now, and see if the rest works?
Thanks |
I've fixed the multi-threading issue as well. Hopefully, it should work now.
|
Sandeep:
Yes it works very fine, congratulation. However, now after various time steps, I have a problem at the boundaries, sorry Quote:
Regards, Olivier |
Sandeep:
I carried out a run in debub mode: Quote:
Olivier |
Could you give me a test case that I can work with?
|
Hi Sandeep,
A good day to you! I have modified the solver (it can work now in parallel and take in account viscous forces). Now, I am working with foam3.0 and I use parMetis method. The solver works fine during various time steps, about 30000, up to an error: < Code:
ExecutionTime = 179843 s ClockTime = 183110 s When I run another test case, I have the same error but on another patch. Have you an idea? Regards, Olivier |
Olivier,
If you are able to reproduce this consistently, then it would be helpful if you could write out the mesh at the time-step just prior to the crash, and then restart the simulation with a higher debug level (valid up to level 5) to produce more output. This should write out a few VTK files (related to the swaps) that you can visualize, and would also help me figure out what might be wrong. Glad to know that you're finding this useful. |
Hi Sandeep,
I have the same error than the one at post #91 from this page when running the GDI engine case. Bruno (wyldckat) have been helping me to resolve the issues with relation to the case, from the problem with the load balancing process and the loading of the parMetis libraries to the one with debbuging the dynamic mesh. Here are the results: http://www.cfd-online.com/Forums/ope...balancing.html I have sent to you through a private message the link to the debug package "turbDyMEngineFoam4subdomains.debug_at_358.3_3 58.4 .tar.gz" as well as the original case. Thank you very much, Alvaro. |
Tutorial for openFoam 2.3.0
I am using openFoam 2.3.0 and I managed to compile both the mesquite and the dynamicTopoFvMesh. I could run the text example circCylinder3d by Mooney (7th openFoam workshop) after initial hitch.
However I do not understand the other tutorials.
Here is link to Kyle Mooney's files from the workshop. Of course the tutorials were for old openFoam versions but can someone can please suggest modifications for openFoam2.3.0. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% In addition I have a case where a cube with in another cube is rotating with some speed. I want the mesh to update while the cube is rotating. Of course with current setup it does not. It would be nice if someone can help me fix this case. Here is link to the case. http://www.mediafire.com/download/mb...bject_mod3.zip |
Points between two slip boundaries do not move correctly with mesquiteMotionSolver
3 Attachment(s)
Hello ,
I would like to use Mesquite Motion Solver coupled with dynamicTopoFvMesh to simulate a case with a deforming boundary (which is deformed based on calculated data) . I created a simple case based on the circCylinder3dHex tutorial but I got a problem. The points on the line between two slip boundaries do not move correctly as showed in pictures. I uploaded my case and please help me find out where did I make a mistake...(I am using Foam-extend 3.1) By the way, I would like to use Mesquite Motion solver with interDyMFoam. However, the alpha1 value is not correct when the mesh is deformed. Could someone give me some suggestions about how to solve this problem ? Thanks in advance ! Best regards ! Lu ZHOU |
All times are GMT -4. The time now is 19:19. |