-
Notifications
You must be signed in to change notification settings - Fork 20
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
Urom and Umag at a final time step looks different #18
Comments
@tpgrunloh @tjwilso @akashaero, Hello,Developers: |
Let me take a look at this. Will get back to you soon! |
Hello @skyabc355 Many thanks for acknowledging my issues. But I figured this out correctly using Ubuntu 20.04.4 LTS and OpenFOAM v1906. The issue could be that the inconsistency in using the |
Hello@chandukec@akashaero,Thanks for your replies.I have successfully used this POD utility with Ubuntu 20.04 and OpenFOAM 7.Everything is working as expected. |
Hello,

Many thanks for this utility. I tried to use this utility for the sample case that you have provided, when I tried to run
podROM 0
it gave me some display output but at the final line it sayssegmentation fault
. I ignored that went with thempirun -np 4 podFlowReconstruct -time 0.5:15 -parallel
. But when I compared theurom
andumag
velocity fields at the final time step, they looks different-- the screenshot is attached herewith. Is that fine, or I am doing something terribly wrong? Any comment/suggestion will be a great help, thanks in advance.The text was updated successfully, but these errors were encountered: