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

Reconstruction issue #7

Open
starflame-Qot opened this issue Dec 22, 2023 · 2 comments
Open

Reconstruction issue #7

starflame-Qot opened this issue Dec 22, 2023 · 2 comments
Assignees

Comments

@starflame-Qot
Copy link

starflame-Qot commented Dec 22, 2023

hello,I tested two tutorial cases, freeProFlame2D and damBreak2D, and both worked fine in reconstructParMesh.

However, once I use reconstructPar, I will get the following error, as shown in the figure.

Screenshot from 2023-12-22 08-43-27

It doesn't go wrong from the beginning, it happens sometime in the middle.(actually, freeProFlame2D case was reported error at the first moment)

When I use reconstructPar -latestTime, I can synthesize the data for the last time.

Thanks for your potential help.

@JanGaertner
Copy link

I had the same issue, never could figure out why it happens as it appears kinda random.

However, I think this is an OpenFOAM issue. I also experienced reconstruct problems with a static mesh for large scale computations on a super computer.

If you have an idea how to solve this, it would be greatly appreciated.

@FoamScience FoamScience self-assigned this Dec 22, 2023
@FoamScience
Copy link
Collaborator

FoamScience commented Dec 22, 2023

I see.

The problem seems to be originating from a bug in reconstructPar. It is somehow trying to read mesh data of the previous time steps instead of the current one!!!

There is a simple workaround. Reconstruction seems to work if you specify the time as a CLI argument:

reconstructParMesh
for t in $(foamListTimes); do reconstructPar -time $t; done

Or, even better, always reconstruct using distributePar:

runParallel redistributePar -reconstruct

I personally like the second way better. Thanks for reporting this behavior.

I'll keep this issue open; and track progress on fully resolving this bug. If I find time, I'll investigate this further during the weekend.

  • add a wiki note about using redistributePar
  • switch all tutorials to use redistributePar for decomposition/reconstruction
  • fix reconstructPar bug: trying to read some processor meshes from the wrong time folders

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